Thank you for your answer. At

Jimini — Mon, 18 Jul 2011 17:00:48 +0000

Thank you for your answer.

At the moment, no accounts are listed. Yesterday, I emptied /var/spool/jabber/ for testing purposes, so I would have to search a backup of that folder first. But It is also impossible to create ne accounts, I always get the error "403: forbidden" in Pidgin. Using "ejabberdctl", I can register users without any problems.

The other things I was asking for were simply stupid mistakes by myself.
Thanks for your help so long!

Best regards,
Jimini

Jimini wrote: I use ejabberd

mfoss — Mon, 18 Jul 2011 10:55:17 +0000

Jimini wrote:

I use ejabberd on Gentoo Linux. On june 20th I upgraded from 2.1.7 to 2.1.8, but did not restart the daemon. This morning, I had to reboot the machine the daemon runs on, and since that, I can not connect to ejabberd anymore.
Pidgin and PSI tell me, that I would not be authorized, here is an excerpt from the log:
=INFO REPORT==== 2011-07-17 10:34:27 ===
I(<0.314.0>:ejabberd_c2s:784) : ({socket_state,tls,{tlssock,#Port<0.3549>,#Port<0.3561>},<0.313.0>}) Failed authentication for jimini@bla.host.org

It seems as if the old database isn't used, or you provide wrong password

Are the old accounts available?
$ ejabberdctl registered_users localhost
badlop
badlop2
user1
user2

Jimini wrote:

I am also unable to register new users, either with Pidgin / PSI or directly on the machine by using "ejabberdctl register test3 test3@bla.host.org secretpw":
Can't register user test3@test3@bla.host.org at node ejabberd@localhost: not_allowed

Why are there so many @ in the user JID?

Jimini wrote:

Then I noticed the following:
Atlas jabber # ejabberdctl status
The node ejabberd@localhost is started with status: started
ejabberd 2.1.7 is running in that node

1) why is the daemon started as version 2.1.7?

Don't worry, this is because 2.1.8 still advertices as 2.1.7. You can see the mistake in the file ejabberd.app

Jimini wrote:

2) why does the daemon seem not to use my config-file?

Why do you think the daemon doesn't use your config? Check with
netstat -nlp | grep beam
if it listens in 5222. Then change that number in the config to 5666, restart, and see if ejabberd now listens 5666.

ejabberd - Comments for "ejabberd 2.1.8 keeps starting 2.1.7 and ignores config file"

Thank you for your answer. At

Jimini wrote: I use ejabberd