You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the server was rebooted uncleanly, the existing ~/.eye directory causes eye to think processes are running when they are not, or to kill the wrong processes (based on PID?), or just not to start at all.
A quick fix is to rm -$ ~/.eye followed by eye load recorder.eye after a server reboot, but would be nice if eye could detect if it was rebooted?
I'm not sure how eye internals work, but maybe it can check for PID as well as process name or something before assuming a process is up when it is not?
The text was updated successfully, but these errors were encountered:
~/.eye not related to the process pids, you specify pid_file for every process.
Yes, i meet sometimes this problem too, when reboot and not call eye stop all && eye quit before, after reboot eye read pids from pid_files, and it can happen that there is already alive process with that pid (rare situation, but possible), so eye can kill that wrong process (or sometimes itself)
I also think about saving pid + name, for that situation, (god, bluepill, monit seems not doing this)
If the server was rebooted uncleanly, the existing ~/.eye directory causes eye to think processes are running when they are not, or to kill the wrong processes (based on PID?), or just not to start at all.
A quick fix is to rm -$ ~/.eye followed by eye load recorder.eye after a server reboot, but would be nice if eye could detect if it was rebooted?
I'm not sure how eye internals work, but maybe it can check for PID as well as process name or something before assuming a process is up when it is not?
The text was updated successfully, but these errors were encountered: