[Buildbot] #3051: master refuses to schedule new builds, doesn't really stop nor start

[Buildbot trac]

#3051: master refuses to schedule new builds, doesn't really stop nor start
-------------------+-----------------------
Reporter:  Ben     |      Owner:
    Type:  defect  |     Status:  new
Priority:  major   |  Milestone:  undecided
 Version:  master  |   Keywords:
-------------------+-----------------------
 It's a quite tough one ... As I didn't realized immediatly the state in
 which my master was, I can't really provide reproduction instruction ...

 I guess the first weird stuff is that the DockerSlave started (the
 container was running), but was never acknowledged by the master. the
 Docker stuff did the right stuff, upon Timeout, it killed the container as
 intended.

 When stopping the master I got the following message:

 {{{
 2014-11-18 15:15:50+0100 [-] Received SIGTERM, shutting down.
 2014-11-18 15:15:50+0100 [-] Weird: Got request to stop before started.
 Allowing slave to start cleanly to avoid inconsistent state
 2014-11-18 15:15:50+0100 [-] (TCP Port 8020 Closed)
 2014-11-18 15:15:50+0100 [-] Stopping factory
 <buildbot.www.service.RotateLogSite instance at 0x3687248>
 2014-11-18 15:15:50+0100 [-] (TCP Port 9989 Closed)
 2014-11-18 15:15:50+0100 [-] Stopping factory
 <twisted.spread.pb.PBServerFactory instance at 0x3efc4d0>
 }}}

 And it does not starts again (nothing in the logs).

 During that time, no new build was started (although requests being
 there).

--
Ticket URL: <http://trac.buildbot.net/ticket/3051>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation