ejabberd - Comments for "[newy] first start problems"

web admin

wangyatong — Thu, 19 May 2005 13:23:25 +0000

i run into problem when access http://localhost:5280/admin with result "not allow".

Can you access this url? if can, how to conf it?

Thanks

Great!!!

Seb — Thu, 21 Apr 2005 08:12:06 +0000

Ok, Really thank you for being so helpfull with such an awful newby ;o)
Now, every things seem to work properly. So, I am going to try XMPP and test what I can make with this platform...
See you next time I get a challenge in my XMPP quest ;o)

webadmin: use the full JID

mfoss — Tue, 19 Apr 2005 14:12:45 +0000

there is always a "but" in my posts

Yes, I noticed that :)

I still get a "401 unauthorised"

Possible errors when authenticating on the web admin:

401 unauthorised: you did not specify an existing user, or a valid password. On ejabberd 0.9, the webadmin login user is the full JID: admin@localhost or admin@cpuname...
Not Allowed: you entered an existing user, but he has no privileges to view the page.

I am wondering why my XMPP server on localhost only works with user@localhost JIDs and not with user@cpuName JIDs

Set the host name in ejabberd.cfg to the Jabber server name: 'cpuname', or 'cpuname.org' or jabber.cpuname.org'..., not to 'localhost'. JIDs will be user@servername.

nearly working...

Seb — Tue, 19 Apr 2005 12:33:25 +0000

Ok, ejabberd server and ejabberdctl work properly now.

But (there is always a "but" in my posts...), I cannot log in the admin console. I set {acl, admin, {user, "admin"}} and created a account for admin but I still get a "401 unauthorised". I restarted several times the server to make it take into account the admin settings but it does not work better... Any idea?

Moreover, I am wondering why my XMPP server on localhost only works with user@localhost JIDs and not with user@cpuName JIDs (cpuName is the name of my computer on the network) whereas all the application are able to make the translation and use both server name (i.e. localhost or cpuName). PDUs are routed on the same machine/interface, that is to say it should make no differences...

Regards,
Seb

copy the script to the beam directory

mfoss — Tue, 19 Apr 2005 11:00:54 +0000

ejabberdctl script does not work: undef, [{ejabberd_ctl,start

The error reported by Erlang when running that script means it can't find the ejabberd *.beam files. Check these solutions:

Copy that script to the directory where ejabberd *.beam files are, and execute it from there.
Tell Erlang the directory where the ejabberd *.beam files are; add something like this to the script: -pa /var/lib/ejabberd/ebin

{acl, admin, {user, "Admin"}}

It's not relevant now, but better put it lowercase.

Psi (it does not know the server...)

Maybe the server name can't be resolved. Does 'ping servername' work?. Try setting the servername as 'localhost', it should work

It works ;o)

Seb — Tue, 19 Apr 2005 09:23:14 +0000

Ok, I downloaded las ejabberd version 0.9 and I made a new installation that seems to work... but I still have a problem (I am a horrible newby, don't you think?): I cannot create a user account.
Indeed, I have not an access to the admin console since I have not created my admin account yet and ejabberdctl script does not work (see the error message below). I specified a username for admin in the ejabberd.cfg with {acl, admin, {user, "Admin"}}. but I am not able to create this account even if I use Psi (it does not know the server...).
So, how to make a first XMPP admin account on the ejabberd server?

Regards,
Seb

ejabberdctl's error message:
{"init terminating in do_boot",{undef,[{ejabberd_ctl,start,[]},{init,start_it,1},{init,start_em,1}]}}

Crash dump was written to: erl_crash.dump
init terminating in do_boot ()

I have a ejabberd.cfg file in

mfoss — Tue, 19 Apr 2005 08:52:38 +0000

I have a ejabberd.cfg file in /etc/ejabberd/ and directly in /var/lib/ejabberd/

If you do not specify the exact file with '-ejabberd config "/etc/ejabberd/ejabberd.cfg" ', ejabberd will look for ejabberd.cfg on the current directory, where the *.beam files are.

Still does not work...

Seb — Tue, 19 Apr 2005 08:41:19 +0000

Thanks for your help but I still cannot make it work...
I have a ejabberd.cfg file in /etc/ejabberd/ and directly in /var/lib/ejabberd/ but I always get the same ERROR report, even if I am logged as root with full rights on the files. So, is there another mistake I could have done?

thanks,
Seb

Solution...

adaughterson — Mon, 18 Apr 2005 20:26:56 +0000

If you pass the locale of the cfg file to the erl command as an argument it seems to work:
erl -pa /var/lib/ejabberd/ebin -sname ejabberd -s ejabberd -ejabberd config \"/etc/ejabberd/ejabberd.cfg\" log_path "/var/log/ejabberd/ejabberd.log\" -sasl sasl_error_logger \{file,\"/var/log/ejabberd/sasl.log\"\} -mnesia dir "/var/lib/ejabberd/spool\"

Or just copy the ejabberd.cfg from /etc/ejabberd to /var/lib/ejabberd

ejabberd.cfg does not exist

mfoss — Mon, 18 Apr 2005 14:59:31 +0000

I tried to start it without any success

Only ERROR and CRASH REPORT are significant now. The key is here:

=ERROR REPORT==== 18-Apr-2005::12:05:56 ===
E(<0.39.0>:ejabberd_config:58): Can't load config file "ejabberd.cfg": enoent

The error is that ejabberd can't load the config file 'ejabberd.cfg'. And 'enoent' means that the file does not even exist.

You can use 'ejabberd.cfg.example' to create your config file. Don't forget to specify its full path to erlang, and make it readable by the user that will run ejabberd.

I would like to install transport components on ejabberd

I hope those tutorials are good enought :)