Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#16385 - [ejabberd] server doesn't start.
Attached to Project:
Community Packages
Opened by Adrian Stratulat (Adrians) - Monday, 28 September 2009, 14:36 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 29 September 2009, 08:57 GMT
Opened by Adrian Stratulat (Adrians) - Monday, 28 September 2009, 14:36 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 29 September 2009, 08:57 GMT
|
DetailsDescription:
The ejabberd server doesn't start. Additional info: * ejabberd 2.1.0_rc1-1 Steps to reproduce: 1. Install ejabberd 2. Try to start it. The first part of this bug was quite straightforward - the configuration files used by this program had some incorrect permissions, so that the server couldn't read its own settings: $ ls -l /etc/ejabberd/ total 24 -rw-r----- 1 root root 13235 2009-09-28 15:58 ejabberd.cfg -rw-r----- 1 root root 3835 2009-09-14 00:20 ejabberdctl.cfg -rw-r--r-- 1 root root 111 2009-09-14 00:20 inetrc So I just used: # chown ejabberd /etc/ejabberd/ejabberd.cfg # chown ejabberd /etc/ejabberd/ejabberdctl.cfg It may not be the only bug in this version, as I'm still trying to make it work. I will post if I find any other strange things. |
This task depends upon
After I edited the .cfg to add my DNS name and used "ejabberdctl register <username> <dns-name> <password>", my pidgin says "503: service unavailable".
To be continued.
From my part, the case is closed, as it works for me (with few workarounds), but other users may thnk otherwise.