[ejabberd] ejabberd does not start, no logs produced except sasl.log

Eugeny N Dzhurinsky bofh at redwerk.com
Thu Oct 4 17:27:59 MSD 2007


On Thu, Oct 04, 2007 at 08:36:44AM -0400, Manuel Mely wrote:
> Eugeny N Dzhurinsky wrote:
> > Hello!
> > Could somebody please explain why can this happen - after installation of
> > ejabberd 1.1.4 on Gentoo, with default configuration ejabberd does not produce
> > any logs, except sasl.log, and does not listen on appropriate ports 5222/5223
> > 
> > sasl.log content goes below:
> > 
> > =CRASH REPORT==== 4-Oct-2007::14:12:50 ===
> >   crasher:
> >     pid: <0.36.0>
> >     registered_name: []
> >     error_info: {bad_return,{{ejabberd_app,start,[normal,[]]},
> >                               {'EXIT',{{badmatch,{aborted,{no_exists,config}}},
> >                                        [{ejabberd_config,set_opts,1},
> >                                         {ejabberd_app,start,2},
> >                                         {application_master,start_it_old,
> 
> Try changing permission to ejabberd.cfg. If doesn't work try to remove 
> your ejabberd database (mnesia one) and restart the service.
> 
> If this doesn't work, try with a good erlang eye your configuration, 
> maybe there's a "}" or something missing.

Okay, I modified permissions and ownership for /etc/jabber/* and removed
everything in /var/spool/jabber - and ejabberd successfully started.

Thanks.

-- 
Eugene Dzhurinsky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.jabber.ru/pipermail/ejabberd/attachments/20071004/0b16791f/attachment.pgp 


More information about the ejabberd mailing list