jabber-at/ejabberd

ejabberd don't start automatic after upgrade to 16.08

Closed this issue · 3 comments

beherit commented

What version of ejabberd are you using?

16.08

What operating system (version) are you using?

Debian Jessie 8.5

How did you install ejabberd (source, package, distribution)?

jabber.at repo

What did not work as expected? Are there error messages in the log? What
was the unexpected behavior? What was the expected result?

After upgrade from 16.04 to 16.08 ejabberd won't start automatic, I must run it manually:

root@virtualbox:/etc/ejabberd# systemctl start ejabberd
Job for ejabberd.service failed. See 'systemctl status ejabberd.service' and 'journalctl -xn' for details.
root@virtualbox:/etc/ejabberd# systemctl status ejabberd.service
● ejabberd.service - A distributed, fault-tolerant Jabber/XMPP server
   Loaded: loaded (/lib/systemd/system/ejabberd.service; enabled)
   Active: activating (auto-restart) (Result: resources) since Tue 2016-09-06 09:53:44 CEST; 3s ago
  Process: 16931 ExecStart=/usr/sbin/ejabberdctl start (code=exited, status=0/SUCCESS)
 Main PID: 569 (code=exited, status=1/FAILURE)

Sep 06 09:53:44 virtualbox systemd[1]: ejabberd.service never wrote its PID file. Failing.
Sep 06 09:53:44 virtualbox systemd[1]: Failed to start A distributed, fault-tolerant Jabber/XMPP server.
Sep 06 09:53:44 virtualbox systemd[1]: Unit ejabberd.service entered failed state.
beherit commented

Same in ejabberd 16.09, I even reinstalled it but with no luck:

root@virtualbox:~# systemctl status ejabberd
● ejabberd.service - A distributed, fault-tolerant Jabber/XMPP server
   Loaded: loaded (/lib/systemd/system/ejabberd.service; enabled)
   Active: activating (auto-restart) (Result: resources) since Wed 2016-09-28 19:42:26 CEST; 1s ago
  Process: 896 ExecStart=/usr/sbin/ejabberdctl start (code=exited, status=0/SUCCESS)

Sep 28 19:42:26 virtualbox systemd[1]: Failed to start A distributed, fault-tolerant Jabber/XMPP server.
Sep 28 19:42:26 virtualbox systemd[1]: Unit ejabberd.service entered failed state.
root@virtualbox:~# systemctl start ejabberd
Job for ejabberd.service failed. See 'systemctl status ejabberd.service' and 'journalctl -xn' for details.
root@virtualbox:~# systemctl status ejabberd
● ejabberd.service - A distributed, fault-tolerant Jabber/XMPP server
   Loaded: loaded (/lib/systemd/system/ejabberd.service; enabled)
   Active: activating (auto-restart) (Result: resources) since Wed 2016-09-28 19:43:18 CEST; 3s ago
  Process: 1169 ExecStart=/usr/sbin/ejabberdctl start (code=exited, status=0/SUCCESS)

Sep 28 19:43:18 virtualbox systemd[1]: ejabberd.service never wrote its PID file. Failing.
Sep 28 19:43:18 virtualbox systemd[1]: Failed to start A distributed, fault-tolerant Jabber/XMPP server.
Sep 28 19:43:18 virtualbox systemd[1]: Unit ejabberd.service entered failed state.

When I hit ejabberdctl start I see PID file in /var/run/ejabberd but only for 1 second, ejabberd still run but there is no such file.

beherit commented

@mathiasertl could You take a look at this issue? I bought new VPS with fresh Debian 8.6 installation, I install there ejabberd and problem exists too!

beherit commented

It's funny because setcap causes this problem...

setcap 'cap_net_bind_service=+ep' /usr/lib/erlang/erts*/bin/beam
setcap 'cap_net_bind_service=+ep' /usr/lib/erlang/erts*/bin/beam.smp

Uhm.