Description of problem: Any use of ejabberdctl causes a dump file to be placed in /var/log/ejabberd and the command fails. Version-Release number of selected component (if applicable): ejabberd-2.0.0-1.fc9.i386 How reproducible: just enter: ejabberdctl live Steps to Reproduce: 1. enter above command 2. 3. Actual results: Expected results: Additional info:
Created attachment 309405 [details] dump file after entering: ejabberdctl
Confirmed. I'll fix it ASAP.
It seems there are 2 things needed to make ejabberdctl work. The localhost stuff is fine. (No need for cut hostname.) The script must run as ejabberd user. This works, but is ugly: # runuser -s /bin/sh -c "/usr/sbin/ejabberdctl status" - ejabberd Node ejabberd@localhost is started. Status: started ejabberd is running Second, HOME is wrong. Should be: HOME=/var/lib/ejabberd (not /usr/lib/ejabberd)
Oops, sorry, I meant to put this in the bugreport for ejabberd-2.0.1-2.fc9.i386.
ejabberd-2.0.1-3.fc8 has been submitted as an update for Fedora 8
ejabberd-2.0.1-3.fc9 has been submitted as an update for Fedora 9
ejabberd-2.0.1-4.fc8 has been submitted as an update for Fedora 8
ejabberd-2.0.1-4.fc9 has been submitted as an update for Fedora 9
ejabberd-2.0.1-4.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update ejabberd'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-5671
ejabberd-2.0.1-4.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
ejabberd-2.0.1-4.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.