I am experiencing the following strange circumstances:
- I visit the monit service manager and it reports that all my services are running
- The service is clearly not running. When I try to use it, it fails in a manner that indicates that it is not running (i.e. it is unavailable), and when I run "ps -aef | grep <service name>" nothing shows up. Also, if I scan through the ps -aef list myself, I see nothing resembling the service.
- I also searched for the process ID stored in the pid file using "ps -aef | grep <pid>" and I got nothing. In the past I have seen monit think that the service is running if that pid file, having been left there by the previous instance of the service, contains the pid of another unrelated service that is currently running. In other words, monit *seems* to dumbly check to see if the pid indicated in the pid file matches any currently running process in deciding that its monitored service is running. But that is not happening in this case. What *is* happening here? How is it that monit decides whether or not the monitored service is actually running?
- The strangest thing is that the monit service manager is reporting that the service has been up for 1 day 10 hours and 18 minutes, whereas the other monitored service has been up for 10 hours and 18 minutes. The server is itself reporting an uptime of 10 hours and 18 minutes, so the amount of time that the service manager is reporting is completely wrong.
Any thoughts?