On Mon, Jul 16, 2007 at 07:54:31AM -0400, Steve wrote:
Here is trhe data.
hobbit at balboa [/usr/local/hobbit/server/bin]
$ cat /usr/local/hobbit/server/www/bb.html
OK, this is a complete webpage, it just doesn't have any hosts
on it. Which is consistent with what you'd get when bbgen cannot
query the Hobbit server for the current status.
hobbit at balboa [/usr/local/hobbit/server/bin]
$ ./bbcmd bbgen
2007-07-16 07:51:35 Using default environment file /usr/local/hobbit/server/etc/hobbitserver.cfg
2007-07-16 07:52:22 Whoops ! bb failed to send message - timeout
2007-07-16 07:52:22 hobbitd status-board not available
OK, try running it with the "--debug" option added. It dumps
a lot of output, but you should find something like this:
2007-07-16 16:25:34 load_state()
2007-07-16 16:25:34 Transport setup is:
2007-07-16 16:25:34 bbdportnumber = 1984
2007-07-16 16:25:34 bbdispproxyhost = NONE
2007-07-16 16:25:34 bbdispproxyport = 0
2007-07-16 16:25:34 Recipient listed as '127.0.0.1'
2007-07-16 16:25:34 Standard BB protocol on port 1984
2007-07-16 16:25:34 Will connect to address 127.0.0.1 port 1984
2007-07-16 16:25:34 Connect status is 0
2007-07-16 16:25:34 Sent 135 bytes
2007-07-16 16:25:34 Read 2248 bytes
2007-07-16 16:25:34 Closing connection
The "recipient" setting is taken from the BBDISP setting in
hobbitserver.cfg - this must be the correct IP of your Hobbit server.
Is there any indication that the "hobbitd" process has crashed? It
will restart automatically, but do check for core-files in
~hobbit/data/tmp/, or the process creation timestamp of the "hobbitd"
proces. And the hobbitlaunch.log file will also tell if it has restarted
hobbit.
Regards,
Henrik