[Buildbot-devel] buildmaster almost starts, but doesn't really

[Axel Hecht]

2007/9/5, Hacksaw <dtodd at irobot.com>:
> I'm trying to get 0.7.5 going, and I have what I think is a reasonable
> master.cfg. But something must be wrong, because it never finishes starting:
>
> [root at asimov Buildbot]# buildbot restart ~/Buildbot/
> buildbot process 21680 is dead
> now restarting buildbot process..
> Following twistd.log until startup finished..
> 2007/09/05 15:05 -0400 [-] Log opened.
> 2007/09/05 15:05 -0400 [-] twistd 2.5.0 (/usr/bin/python 2.4.2) starting up
> 2007/09/05 15:05 -0400 [-] reactor class: <class
> 'twisted.internet.selectreactor.SelectReactor'>
> 2007/09/05 15:05 -0400 [-] Loading buildbot.tac...
> 2007/09/05 15:05 -0400 [-] Loaded.
> 2007/09/05 15:05 -0400 [-] loading configuration from
> /home/dtodd/Buildbot/master.cfg
> 2007/09/05 15:05 -0400 [-] twisted.conch.manhole_ssh.ConchFactory
> starting on 9999
> 2007/09/05 15:05 -0400 [-] Starting factory
> <twisted.conch.manhole_ssh.ConchFactory instance at 0xb79f10cc>
> 2007/09/05 15:05 -0400 [-] Manhole listening via SSH on port
> tcp:9999:interface=127.0.0.1
> 2007/09/05 15:05 -0400 [-] adding new builder componentFramework for
> category None
> 2007/09/05 15:05 -0400 [-] trying to load status pickle from
> /home/dtodd/Buildbot/full/builder
> 2007/09/05 15:05 -0400 [-] added builder componentFramework in category None
> 2007/09/05 15:05 -0400 [-] adding IStatusReceiver <Waterfall on port
> tcp:8010>
> 2007/09/05 15:05 -0400 [-] twisted.web.server.Site starting on 8010
> 2007/09/05 15:05 -0400 [-] Starting factory <twisted.web.server.Site
> instance at 0xb790b66c>
> 2007/09/05 15:05 -0400 [-] BuildMaster listening on port tcp:9989
> 2007/09/05 15:05 -0400 [-] configuration update started
> 2007/09/05 15:05 -0400 [-] Unhandled error in Deferred:

... and this is where the interesting part of the log would start.
Take a look at what is in twistd.log, be sure to look at the latest
occurence. If that doesn't ring a bell, paste it to your mail.

The 5 seconds message really doesn't mean a whole lot more than that
it took long for buildbot to start up, which may or may not be a sign
for trouble. In your case, it seems less informative than what would
be in your actual log.

Axel