Starting ejabberd with systemctl "hangs" on Ubuntu 22.04 with apparmor profile

[Jason Stephenson]

When starting or restarting ejabberd with systemctl on Ubuntu 22.04, the systemctl command hangs until there is a tiemout.

Ejabberd seems to start just fine but fails to notify systemd that it has started. While ejabberd is running man log messages such as the folloing go to /var/log/syslog:

pr 28 15:13:23 devjam kernel: [23209.114137] audit: type=1400 audit(1651173203.101:2332): apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ejabberdctl" name="run/systemd/notify" pid=29578 comm="5_scheduler" requested_mask="w" denied_mask="w" fsuid=115 ouid=0

Disabling the apparmor profile for usr.sbin.ejabberdctl seems to resolve this.

[Sami hulkko (sahulkko)]

Same issue with error on ejabberd log:
2022-06-01 09:14:31.218448+03:00 [error] <0.356.0>@ejabberd_systemd:handle_info/2:135 Cannot ping watchdog: {badmatch,{error,eacces}}

That seems to be erlang notifier access right to notify systemd.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.