Public bug reported:
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.
** Affects: ejabberd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970791
Title:
Starting ejabberd with systemctl "hangs" on Ubuntu 22.04 with
apparmor profile
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1970791/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
