xmpp.chapril.org-ejabberd/ejabberd.service.template

[Unit]
Description=XMPP Server
After=network.target

[Service]
User=ejabberd
Group=ejabberd
LimitNOFILE=65536
Restart=on-failure
RestartSec=5
ExecStart=@ctlscriptpath@/ejabberdctl foreground
ExecStop=/bin/sh -c '@ctlscriptpath@/ejabberdctl stop && @ctlscriptpath@/ejabberdctl stopped'
ExecReload=@ctlscriptpath@/ejabberdctl reload_config
PrivateDevices=true
TimeoutSec=300

[Install]
WantedBy=multi-user.target
Add script for systemd (Guthub #434) 2015-02-23 15:52:18 +01:00			`[Unit]`
			`Description=XMPP Server`
			`After=network.target`

			`[Service]`
			`User=ejabberd`
			`Group=ejabberd`
Increase file descriptor limit in systemd unit 16,000 file descriptors will only suffice for small setups. 2016-10-20 00:12:02 +02:00			`LimitNOFILE=65536`
Let systemd restart ejabberd on failure The "RestartSec=5" setting has no effect if "Restart" is not also specified. 2016-10-19 23:35:22 +02:00			`Restart=on-failure`
Add script for systemd (Guthub #434) 2015-02-23 15:52:18 +01:00			`RestartSec=5`
Let systemd start ejabberd in foreground Daemons started by systemd shouldn't fork into the background if possible, because if multiple forked processes exist, systemd has a hard time determining the main process ID. In a memory constrained environment, the OOM killer may cause ejabberd to exit without any trace. Because epmd keeps running, systemd wouldn't notice the error condition, and as a result it won't restart the server. With ejabberd running in foreground, systemd is able to obtain the correct exit code (137 in this case, instead of 0) and schedules a restart. The administrator can then see what happend by looking at systemctl status ejabberd. 2020-11-19 20:43:51 +01:00			`ExecStart=@ctlscriptpath@/ejabberdctl foreground`
Let systemd stop ejabberd gracefully Make sure the "ExecStop" command line blocks until ejabberd is actually stopped. This prevents systemd from killing the ejabberd process(es) immediately. Also, let the "ExecStart" command line block until ejabberd's startup is completed. This makes sure that services which depend on ejabberd aren't started up too early. 2016-10-20 00:27:50 +02:00			`ExecStop=/bin/sh -c '@ctlscriptpath@/ejabberdctl stop && @ctlscriptpath@/ejabberdctl stopped'`
Specify "ExecReload" command in systemd unit Now that "ejabberdctl reload_config" works the way most admins would expect, expose the command via systemd. 2017-02-23 18:16:56 +01:00			`ExecReload=@ctlscriptpath@/ejabberdctl reload_config`
Harden the systemd unit Restrict capabilities, have a private tmp directory, private /dev, and don't accessing file system locations that really shouldn't be accessed. 2016-06-28 23:02:41 +02:00			`PrivateDevices=true`
Increase start-up/stop timeout in systemd unit On slow systems, it can take quite a while for "ejabberdctl started" and/or "ejabberdctl stopped" to return. 2018-06-07 17:40:05 +02:00			`TimeoutSec=300`
Add script for systemd (Guthub #434) 2015-02-23 15:52:18 +01:00
			`[Install]`
			`WantedBy=multi-user.target`