[Buildbot-devel] Fwd: Buildbot Slaves Won't Start After Relocation of Machines

[Doug Latornell]

I'm trying to get my buildbot installation up and running again after
all of the master and slave machines were physically moved, and their
IP addresses changed. If it matters, I didn't have much to do with the
move, so the buildbot instances were shutdown by the machine
shutdowns, not by buildbot stop... OTOH, the master and slaves were
all idle at the time of shutdown.

Anyway, the master has come up fine, and the slave that runs on the
same machine is also good. The problem is the slaves running on other
machines. Their log files are showing message like this:

2010-01-29 10:22:14-0800 [-] Starting factory
<buildbot.slave.bot.BotFactory instance at 0xb7aacaec>
2010-01-29 10:22:14-0800 [Uninitialized]
<twisted.internet.tcp.Connector instance at 0xb79ae0cc> will retry in
107 seconds
2010-01-29 10:22:14-0800 [Uninitialized] Stopping factory
<buildbot.slave.bot.BotFactory instance at 0xb7aacaec>

I think that's saying that the slave can't connect to the master, but
I'm not sure.

The slave machines all resolve the master machine's new IP address
just fine. The move happened a few days ago, so I'm sure that DNS
propagation is not the issue. The machines are all on the same subnet.

The only thing I can think of is that the master has stopped listening
on port 9989 for some reason.

Is there something else I'm missing? Any ideas appreciated.

Doug