[jdev] Re: Re: [jadmin] Problem building jabber-1.4.4 (Lars Sommer)

[Lars Sommer]

Dunno if this ever got through, so here it is again:

Hi Matthias.

When i looked in the jabber.xml file, i found out that it was pointing
to /jabber//usrblabla.. So i deleted my jabber folders, installed the
jabber server again with --prefix/jabber (instead of --prefix=/jabber/),
and now it doesent come with the long debug info as before,
unfortunately only with:
--------
Starting program: /jabber/bin/jabberd 
20070315T19:17:22: [notice] (-internal): initializing server

Program received signal SIGSEGV, Segmentation fault.
0x00000011 in ?? ()
(gdb) quit
The program is running.  Exit anyway? (y or n) y
[root at localhost bin]# 
-----------

So now the server doesent crash when i try to register a user, it just,
halts or what you call it. I can make other connections, but it doesent
give me an id, neither does it care what i send to it, it just ignores
it. 

Ive made sure that my folders had the rights it should be, by giving all
permissions:
chmod 777 -R /jabber
and
chmod 777 -R /usr/local/jabber

Its the same.

I think i might have been drunk or something when i came up with that
subject, im using jabberd 1.4.4 :)

Well i feel like im doin progress here, thanks to you!

Hope you can help with that tiny bit of debug info..

Regards
/Lars


> > this time it is no problem in libpth ... the backtrace shows what
> the 
> > executable just did when it crashed ... the names (e.g. 
> > "xdb_file_phandler") there refer to the functions that have called
> > each 
> > other. Every function is called by the function below it. Therefore
> > the 
> > last known function call before your server crashed is 
> > xdb_file_phandler() which is defined in xdb_file.c. There at line
> 291 
> > your computer tried to call something else that crashed ...
> > 
> > Which version of jabberd are you exactly using? (It can't be
> jabberd 
> > 1.4.1 as we have in the subject.) So I can check the right version
> of 
> > this file to see where your problem exists. But I'd expect that
> there
> > is 
> > some problem to access the file spool of your server. Check that 
> > directory you have configured in your jabber.xml configuration file 
> > using the <spool/> element does exist and is read- and writeable by
> > the 
> > user that is running the jabber server.
> > 
> > 
> > Matthias
> >