On Thu, Feb 17, 2005 at 03:18:34PM -0500, kevin grady wrote:
Well that explains the display problem. Kick me for not checking the
logs. So this is what I have in the hobbitlaunch.log:
2005-02-17 16:16:43 Setting up network listener on 0.0.0.0:1984
2005-02-17 16:16:43 Cannot bind to listen socket (Address already in use)
2005-02-17 16:16:43 Task hobbitd terminated, status 1
Could be the same bug that's bitten quite a few people now: The
hostname used in hobbitserver.cfg for the BBSERVERHOSTNAME and
MACHINEDOTS settings is not listed in bb-hosts, causing hobbitd
to crash after 5 minutes.
In that case, you should have a line "hobbitd terminated with signal
6" just before those lines in the logfile.
Make sure the hostname in BBSERVERHOSTNAME is listed in bb-hosts.
I checked the ~/server/etc/hobbitserver.cfg and it has everything
listed properly. This system does not have anything listening on port
1984. Any ideas? Shouldn't the binding IP address be what is specified
in BBSERVERIP?
This error message is bogus, it happens because hobbitd attempts to
restart too quickly after it crashes.
Henrik