Closed tokred closed 7 years ago
@tokred Thank you for the report! :smiley: After reading up on the systemd Restart
option, using on-failure
is indeed a better value to use here.
Regarding your question:
Side question: Is there a difference between shutting Graylog down via web interface or directly via CLI shutdown, e.g. by machine reboot or by systemctl stop?
No, that's no difference. Stopping Graylog via systemd or a regular SIGTERM initiates a graceful shutdown.
@tokred I fixed it for the upcoming 2.2 release packages and for the 2.1 packages.
The graylog-server-2.1.1-2.noarch.rpm
package should appear soon!
Expected Behavior
My Graylog nodes are running behind a load balancer. For maintenance, I would like to use the "Graceful shutdown" feature (http://docs.graylog.org/en/2.1/pages/configuration/load_balancers.html#graceful-shutdown) e.g. to perform system upgrades. Expectation is that the Graylog service shuts down and the node is not active anymore.
Side question: Is there a difference between shutting Graylog down via web interface or directly via CLI shutdown, e.g. by machine reboot or by
systemctl stop
?Current Behavior
After Graylog gracefully shuts down, systemd watchdog automatically restarts the service due to the unit files's configuration. This does not make any sense...
Log entries in journalctl confirm:
Possible Solution
Change the unit file's configuration parameter
Restart=always
to something more sane.Steps to Reproduce (for bugs)
systemctl status graylog-server.service
.Context
Your Environment