Do you get anything after the "close connection"?? I get a bunch of
init_state(host,domain,com.test, -567484, ...)
find_or_create_column(test)
init_state: hostname=host.domain.com, testname=test, color=0......
one for each column for each host. What do yuo get from this command:
server/bin/bb localhost "hobbitdboard
fields=hostname,testname,color,flags,lastchange,logtime,validtime,acktime,disabletime,sender,cookie,line1,acklist"
That's all on one line. It's what bbgen does immediately after logging
"load_state()"
Ralph
On Thu, Jul 10, 2008 at 12:30 PM, Daniel Elswit <user-8d00d2826ff5@xymon.invalid> wrote:
Ah… got it. I see this:
2008-07-10 12:38:49 load_bbhosts: -- got line '10.35.80.51
test.cals.cornell.edu # noping dns ntp'
2008-07-10 12:38:49 init_host(test.cals.cornell.edu)
2008-07-10 12:38:49 load_state()
2008-07-10 12:38:49 Transport setup is:
2008-07-10 12:38:49 bbdportnumber = 1984
2008-07-10 12:38:49 bbdispproxyhost = NONE
2008-07-10 12:38:49 bbdispproxyport = 0
2008-07-10 12:38:49 Recipient listed as '10.253.209.163'
2008-07-10 12:38:49 Standard BB protocol on port 1984
2008-07-10 12:38:49 Will connect to address 10.253.209.163 port 1984
2008-07-10 12:38:49 Connect status is 0
2008-07-10 12:38:49 Sent 126 bytes
2008-07-10 12:38:49 Read 3601 bytes
2008-07-10 12:38:49 Closing connection
--Dan
*From:* Ralph Mitchell [mailto:user-00a5e44c48c0@xymon.invalid]
*Sent:* Thursday, July 10, 2008 11:49 AM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] Configuration question
OK. What I did to get that log was: stop hobbit, change the bbdisplay
entry in server/etc/hobbitlaunch.cfg to read:
CMD bbgen $BBGENOPTS --report --debug
then I renamed the bb-display.log file and restarted hobbit. The log
fragment I posted came from the new bb-display.log during/after it read
through the bb-hosts file.
I guess you wouldn't need to stop/start Hobbit, as it's trying to launch
bbgen every minute...
Ralph
On Thu, Jul 10, 2008 at 10:30 AM, Daniel Elswit <user-8d00d2826ff5@xymon.invalid> wrote:
My bb-display.log has not updated in 2 days (not since I had an initial
problem related to a missing library that was resolved.) I don't see any of
what you have below. The hobbitd.log says "Setup complete". Upon starting
of the service, hobbitlaunch.log says:
2008-07-10 11:20:46 hobbitlaunch starting
2008-07-10 11:20:46 Loading tasklist configuration from
/usr/bin/hobbit/server/etc/hobbitlaunch.cfg
2008-07-10 11:20:46 Loading hostnames
2008-07-10 11:20:46 Loading saved state
2008-07-10 11:20:46 Setting up network listener on 0.0.0.0:1984
2008-07-10 11:20:46 Setting up signal handlers
2008-07-10 11:20:46 Setting up hobbitd channels
2008-07-10 11:20:46 Setting up logfiles
2008-07-10 11:20:52 Task bbdisplay terminated by signal 6
2008-07-10 11:21:52 Task bbdisplay terminated by signal 6
2008-07-10 11:22:52 Task bbdisplay terminated by signal 6
The bbdisplay errors continue to occur every few minutes.
--Dan
*From:* Ralph Mitchell [mailto:user-00a5e44c48c0@xymon.invalid]
*Sent:* Thursday, July 10, 2008 10:55 AM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] Configuration question
On Thu, Jul 10, 2008 at 8:41 AM, Daniel Elswit <user-8d00d2826ff5@xymon.invalid> wrote:
Strangely, bben –debug shows that it cooks right through the bb-hosts
file and then after the last line, aborts with no further information.
bbgen –version runs properly and shows the correct version. I'm beginning
to wonder if the bbgen file itself is corrupted.
This is what I get in my bb-display.log after a restart. The first two
lines below are the last two from bb-hosts - a blank comment line and an
include:
2008-07-10 09:37:51 load_bbhosts: -- got line '#'
2008-07-10 09:37:51 Opening file /home/hobbit/server/etc/ghosts.inc
2008-07-10 09:37:51 load_state()
2008-07-10 09:37:51 Transport setup is:
2008-07-10 09:37:51 bbdportnumber = 1984
2008-07-10 09:37:51 bbdispproxyhost = NONE
2008-07-10 09:37:51 bbdispproxyport = 0
2008-07-10 09:37:51 Recipient listed as '10.134.13.133'
2008-07-10 09:37:51 Standard BB protocol on port 1984
2008-07-10 09:37:51 Will connect to address 10.134.13.133 port 1984
Do you get the "load_state()" ??
Ralph Mitchell