ejabberd - Comments for "Strange problems (maybe bad config?)"

Not started correctly; some error message would help

mfoss — Fri, 12 Sep 2008 23:27:27 +0000

clayman wrote:

And what is that meaning:

root@misfortune> ejabberdctl status
Node ejabberd@localhost is started. Status: started
ejabberd is not running

That means the Erlang node called "ejabberd@localhost" is started correctly. Inside that node (it's like a virtual machine), the ejabberd application is NOT running.

This means ejabberd did not crash, but it didn't start correctly. The problem is usually a syntax mistke in ejabberd.cfg, badly corrupted Mnesia database, or unable to load some important ejabberd or erlang library. I think in all those cases some kind of ERROR REPORT or similar is shown in ejabberd.log or sasl.log

If ejabberd is started correctly, you should see in sasl.log a lot of PROGRESS REPORT, and finally something like this:

=PROGRESS REPORT==== 13-Sep-2008::01:25:04 ===
         application: ejabberd
          started_at: ejabberd@atenea

Same

clayman — Thu, 11 Sep 2008 22:09:50 +0000

badlop wrote:

Did you check ejabberd.log and sasl.log immediately after starting ejabberd?

Yes, there is nothing in them, just old crash reports. Nothing about current start.

Quote:

With that ACL only "user@misfortune will have admin privileges.

Fixed, thanks.

Quote:

Once your server works correctly, remember to enter in the Web Admin and delete the stored old ACLs that you don't want.

The problem is I cannot enter in the Web Admin. I cannot create new user from the terminal nor from jabber client. Ahd what is that meaning:

root@misfortune> ejabberdctl status
Node ejabberd@localhost is started. Status: started
ejabberd is not running

Check logs when starting ejabberd

mfoss — Wed, 10 Sep 2008 08:43:48 +0000

Hello. I have a problems getting ejabberd up and running correctly.
...

root@misfortune> ejabberdctl status Node ejabberd@localhost is started. Status: started ejabberd is not running

...
ejabberd is ... inactive on 5222...

Did you check ejabberd.log and sasl.log immediately after starting ejabberd?

Some lines from config:
{acl, admin, {user, "user" }}.

That ACL grants admin privileges to any account named "user@*"!! You should put something like:

{acl, admin, {user, "user", "misfortune"}}.

With that ACL only "user@misfortune will have admin privileges.

Once your server works correctly, remember to enter in the Web Admin and delete the stored old ACLs that you don't want.