- edited description
Monit thinks service is running, but there is no process
note: im on centos 7, monit is aparently 5.2.5, but I cannot select this from your submission form.
I have problems with services dying, but monit not noticing:
e.g,
[root@live-web ~]# cat /etc/monit.d/codedeploy
check process codedeploy with pidfile /opt/codedeploy-agent/state/.pid/codedeploy-agent.pid
start "/etc/init.d/codedeploy-agent start"
stop "/etc/init.d/codedeploy-agent stop"
[root@live-web ~]# ls -l /opt/codedeploy-agent/state/.pid/codedeploy-agent.pid
-rw-r--r-- 1 root root 5 Feb 16 16:48 /opt/codedeploy-agent/state/.pid/codedeploy-agent.pid
[root@live-web ~]# monit summary
The Monit daemon 5.2.5 uptime: 20h 42m
...
Process 'codedeploy' running
...
Process 'codedeploy'
status running
monitoring status monitored
pid 2621
parent pid 0
uptime 0m
children 0
memory kilobytes 0
memory kilobytes total 0
memory percent 0.0%
memory percent total 0.0%
cpu percent 0.0%
cpu percent total 0.0%
data collected Wed Feb 17 14:27:35 2016
But there is no such process:
[root@live-web ~]# ps -ef | grep 2621
root 7813 6932 0 14:28 pts/0 00:00:00 grep --color=auto 2621
[root@live-web ~]#
As a workaround I guess I can detect its using 0 bytes memory or parent is 0, but surely this is not right.
Cheers,
J.
Comments (5)
-
repo owner -
repo owner - changed version to 5.2.5
-
repo owner Please can you provide output of the following command?:
cat /opt/codedeploy-agent/state/.pid/codedeploy-agent.pid
Please also run monit in debug mode (monit -vI) and send monit logs (can be enabled using "set logfile" statement).
We also suggest to upgrade monit ... the 5.2.5 should work fine with the given configuration, but there were lots of fixes and improvements since 5.2.5.
-
repo owner - changed status to closed
closing ... no response, unable to reproduce, most probably configuration issue
-
repo owner - removed version
Removing version: 5.2.5 (automated comment)
- Log in to comment