You're right, systemd is

terminus — Mon, 30 Jan 2017 20:39:54 +0000

You're right, systemd is terminating it because it thinks (wrongly) that it has failed to start:

Jan 30 12:30:15 hostname systemd[1]: Unit ejabberd.service entered failed state.
Jan 30 12:31:51 hostname systemd[1]: ejabberd.service start operation timed out. Terminating.

Thanks, looks like I just need to get systemd into line.

You should investigate if the

badlop — Fri, 27 Jan 2017 12:26:00 +0000

You should investigate if the server starts for some internal reason, or influenced externally (for example some ejabberdctl or system call to restart). I mean, maybe your system has a script that checks if ejabberd works "correctly", it detects that ejabberd doesn't reply, and then restarts it.

Does it happen at certain time of day? Or when clients do something particular?

Disable the client port 5222, so your users don't connect, does it happen? Or disable port 5269 for s2s connections, does it happen? Or check if there is some cron task for checking ejabberd is running...

And if you didn't yet, set loglevel 5 so you get debug log lines

ejabberd - Comments for "How to debug regular restarts"

You're right, systemd is

You should investigate if the