From 64355744131986420e9492bd84e7f04e46e09765 Mon Sep 17 00:00:00 2001 From: Max Rosin Date: Wed, 15 Nov 2017 01:03:15 +0100 Subject: [PATCH] Add documentation about automatic service restarts with systemd refs #5721 refs #5757 --- doc/02-getting-started.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/doc/02-getting-started.md b/doc/02-getting-started.md index f8664cbc5..f39dac122 100644 --- a/doc/02-getting-started.md +++ b/doc/02-getting-started.md @@ -347,6 +347,24 @@ Examples: If you're stuck with configuration errors, you can manually invoke the [configuration validation](11-cli-commands.md#config-validation). +Usually Icinga 2 is a mission critical part of infrastructure and should be +online at all times. In case of a recoverable crash (e.g. OOM) you may want to +restart Icinga 2 automatically. With Systemd it is as easy as overriding some +settings of the Icinga 2 Systemd service by creating +`/etc/systemd/system/icinga2.service.d/override.conf` with the following +content: + + [Service] + Restart=always + RestartSec=1 + StartLimitInterval=10 + StartLimitBurst=3 + +Run `systemctl daemon-reload && systemctl restart icinga2` to apply the changes. +Now Systemd will always try to restart Icinga 2 (except if you run +`systemctl stop icinga2`). After three failures in ten seconds it will stop +trying because you probably have a problem that requires manual intervention. + > **Tip** > > If you are running into fork errors with Systemd enabled distributions, -- 2.40.0