Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Sun 02:59:09 UTC 8h ago Apache seems to be working until I try and connect to the IP in my browser which just times out or get 100% packet loss if I try to ping it. If set to always, the service will be restarted regardless of whether it exited cleanly or not, got terminated abnormally by a signal, or hit a timeout.I'm setting up NextCloud, but I'm having trouble connecting to my web server. If set to on-watchdog, the service will be restarted only if the watchdog timeout for the service expires. If set to on-abort, the service will be restarted only if the service process exits due to an uncaught signal not specified as a clean exit status. If set to on-abnormal, the service will be restarted when the process is terminated by a signal (including on core dump, excluding the aforementioned four signals), when an operation times out, or when the watchdog timeout is triggered. If set to on-failure, the service will be restarted when the process exits with a non-zero exit code, is terminated by a signal (including on core dump, but excluding the aforementioned four signals), when an operation (such as service reload) times out, and when the configured watchdog timeout is triggered. In this context, a clean exit means an exit code of 0, or one of the signals SIGHUP, SIGINT, SIGTERM or SIGPIPE, and additionally, exit statuses and signals specified in SuccessExitStatus=. If set to on-success, it will be restarted only when the service process exits cleanly. If set to no (the default), the service will not be restarted. Takes one of no, on-success, on-failure, on-abnormal, on-watchdog, on-abort, or always. Timeouts include missing the watchdog "keep-alive ping" deadline and a service start, reload, and stop operation timeouts. service stop or restart), the service will not be restarted. When the death of the process is a result of systemd operation (e.g. The service process may be the main service process, but it may also be one of the processes specified with ExecStartPre=, ExecStartPost=, ExecStop=, ExecStopPost=, or ExecReload=. On-watchdog: will be restarted only if the watchdog timeout for the service expiresĪlways: will be restarted regardless of whether it exited cleanly or not, got terminated abnormally by a signal, or hit a timeoutĬonfigures whether the service shall be restarted when the service process exits, is killed, or a timeout is reached. On-abort: will be restarted only if the service process exits due to an uncaught signal not specified as a clean exit status On-failure: will be restarted when the process exits with a non-zero exit code On-success: will be restarted only when the service process exits cleanly No: the default, the service will not be restarted I believe the addition of the Restart option to your systemd service file would ensure it gets start when not stopped by the systemctl stop command: Restart= Sep 06 18:19:17 localhost systemd: Started LSB: service and resource monitoring daemon.Ĭould you help me to set up systemd so it will restart monit after it has been killed? Sep 06 18:19:17 localhost systemd: rvice: PID file /run/monit.pid not readable (yet?) after start: No such file or directory Sep 06 18:19:17 localhost monit: * Starting daemon monitor monit Sep 06 18:19:17 localhost systemd: Starting LSB: service and resource monitoring daemon. Sep 06 18:19:17 localhost systemd: Stopped LSB: service and resource monitoring daemon. Main PID: 6843 (code=exited, status=0/SUCCESS) Process: 6835 ExecStart=/etc/init.d/monit start (code=exited, status=0/SUCCESS) Process: 6830 ExecStop=/etc/init.d/monit stop (code=exited, status=0/SUCCESS) Loaded: loaded (/etc/init.d/monit generated vendor preset: enabled)ĭrop-In: /etc/systemd/system/Īctive: active (exited) since Wed 18:19:17 UTC 4min 29s ago rvice - LSB: service and resource monitoring daemon.Systemctl shows that monit is active but exited sudo systemctl status rvice Lookpla+ 6857 0.0 0.0 14212 1008 pts/0 S+ 18:21 0:00 grep -color=auto monitīut when I kill monit it doesn't start again: sudo kill 6843 I enabled systemd to load monit at startup sudo systemctl enable monit
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |