Description of problem: Wrong path to ejabberdctl: /usr/lib/systemd/system/ejabberd.service ExecStop=/usr/sbin/ejabberdctl Version-Release number of selected component (if applicable): ejabberd-2.1.13-7.fc20.x86_64 How reproducible: Always. Steps to Reproduce: 1. systemctl restart ejabberd.service 2. journalctl -lu ejabberd.service Actual results: Errors while stopping/restarting service. Expected results: Correct path: /usr/bin/ejabberdctl
Additional info: ExecStop option without /usr/bin/bash returns non-zero exit status: # systemctl status ejabberd.service ... Process: 10253 ExecStop=/usr/bin/ejabberdctl stop (code=exited, status=127) # journalctl -lu ejabberd.service ... systemd[1]: Stopping A distributed, fault-tolerant Jabber/XMPP server... ejabberdctl[10253]: Refusing to render service to dead parents. systemd[1]: ejabberd.service: control process exited, code=exited status=127 systemd[1]: Stopped A distributed, fault-tolerant Jabber/XMPP server. systemd[1]: Unit ejabberd.service entered failed state. Workaround is the same as in ExecStart option: ExecStop=/usr/bin/bash /usr/bin/ejabberdctl stop
This bug should be closed in Rawhide now and will be closed in Fedora 21.
The problem persists on Fedora 21 + ejabberd-14.07-6.fc21.x86_64: > Dec 17 20:41:18 srv systemd[1]: Stopping A distributed, fault-tolerant Jabber/XMPP server... > Dec 17 20:41:18 srv ejabberdctl[5105]: Refusing to render service to dead parents. > Dec 17 20:41:18 srv systemd[1]: ejabberd.service: control process exited, code=exited status=127 > Dec 17 20:41:18 srv systemd[1]: Unit ejabberd.service entered failed state. > Dec 17 20:41:18 srv systemd[1]: ejabberd.service failed.