tags 941075 +moreinfo thanks On Tue, Sep 24, 2019 at 11:38:52AM +0200, Han Boetes wrote: > The current monit package does not include a systemctl file, often resulting > in > monit not running. If I'd check the status with systemctl the result was: > active(exited) see also: https://unix.stackexchange.com/questions/241970/what- > does-status-active-exited-mean-for-a-systemd-service
I don't understand. What conditions lead to the state "monit not running"? Perhaps, you have system with systemd, but manage monit using /etc/init.d/monit script directly. You shouldn't do it, this makes systemd crazy, but this is not a monit's problem. Use systemctl to start/stop/reload monit on systemd-enabled hosts - and everything should work and systemd will be happy. Please let me know if you still have problems after using this suggestion. > Easy fix: add a systemd file and remove the /etc/init.d/monit file Are you volunteered to debug and fix any problems with systemd-enabled setups and this unit file? Please look to the README.Debian: monit can work with systemd, but it would be better, if you avoid this use case.
