-
assigned issue to
Does not Exist status for Stopped service
i see the status as Does not Exist status for Stopped service. is it possible to make the status as "stopped". So that we have a clear status like "running" and "stopped".
Comments (7)
-
Account Deactivated reporter -
repo owner Please can you provide more details about where you see the "Does not Exist" status (screenshot?) and under what circumstances and which Monit version it is?
When you stop or unmonitor the service gracefully via Monit (using for example "monit stop myservice"), the state becomes "Not monitored", even if it was "Does not exist" before.
If you stop the process outside of Monit control and won't disable its monitoring, Monit will try to restart it and before the process is recovered, the status will be "Does not exist".
-
Account Deactivated reporter when we stop any service which is monitored by Monit, we get a status as Does not exist on monit UI.
snippet:
root@cibu-blr14 ~]# service crond stop Stopping crond: [ OK ] [root@cibu-blr14 ~]# monit summary The Monit daemon 5.1.1 uptime: 21h 22m
Process 'cron' Does not exist Process 'keepAliveProg' running System 'cibu-blr14' running
the same satus is replicated in monit UI.
-
repo owner Thanks for data.
The "service crond stop" doesn't stop the service via monit nor disables the monitoring => monit will detect that the service is not running and will display "Does not exist" status (monit "doesn't know" that the process stop was intentional).
If the service is monitored with monit, you should either stop it via "monit stop crond" or at least disable monitoring and then you can stop it manually ("monit unmonitor crond").
-
repo owner - changed component to Monit
-
repo owner - changed status to closed
-
repo owner - removed version
Removing version: 5.8.1 (automated comment)
- Log in to comment