Starting ejabberd with systemctl "hangs" on Ubuntu 22.04 with apparmor profile
Bug #1970791 reported by
Jason Stephenson
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ejabberd (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
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(165117320
Disabling the apparmor profile for usr.sbin.
To post a comment you must log in.
Same issue with error on ejabberd log: 218448+ 03:00 [error] <0.356. 0>@ejabberd_ systemd: handle_ info/2: 135 Cannot ping watchdog: {badmatch, {error, eacces} }
2022-06-01 09:14:31.
That seems to be erlang notifier access right to notify systemd.