[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [JDEV] Little problem with jabberbox that I can't track down..



> 	When running jabberbox on a RedHat 5.2 (glibc) based machine, everythings
> fine..  If I compile and run it on my HOME machine, which is Slackware
> (libc5) based machine, it comes up with:
> 
> [Thu Apr 15 22:51:44 1999] main "config=config.x"
> [Thu Apr 15 22:51:44 1999] lib "parsing_file=config.x"
> [Thu Apr 15 22:51:44 1999] lib "Creating new XML Parser pool"
> [Thu Apr 15 22:51:44 1999] main "Unable to open log file!"
> [Thu Apr 15 22:51:44 1999] main "JabberBox starting"
> [Thu Apr 15 22:51:44 1999] lib "IO: collecting data"
> [Thu Apr 15 22:51:44 1999] main "dispatch_data=(NULL)"
> [Thu Apr 15 22:51:44 1999] main "Initialization from IO loop"
> [Thu Apr 15 22:51:44 1999] lib "Created parent net socket"
> net socket: Address already in use
> 
> 	I've quadruple checked, the addresses are NOT in use..  The log file in
> /tmp get's created, but there's nothing in it.  (The above says it can't
> becouse I removed the log line in config.x, to see if not using the Log file
> would fix it in some strange way..) 

I'm still smoothing out the debugging/error stuff, that's why you still
get the "Unable to open log file" when you didn't configure one.

> The net socket: Address already in use
> message is NOT part of jabberbox's code as far as I can grep, nor in the lib
> code.  Any idea's?

As far as the message "net socket: Address already in use" goes, it's
begin generated from this line in /jabberbox/handle.c:
	h_err(s, "net socket");

Why you're getting it though, I'm not sure... At the point where it is
generated, it created a socket on port 5269 with the address listed in
your <listen></listen> configuration directive.  Do a netstat -a and look
for a line like:

tcp        0      0 yourhostname:5269     *:*                     LISTEN

Meaning that there is a process actively listening on that port
somewhere :)

Do you EVER get it to start, or is it always doing this no matter what?

Thanks,

Jer