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

Doug Latornell djl at douglatornell.ca
Tue Feb 2 04:26:40 UTC 2010

Gold star to Mark!

There were indeed local firewalls on the machines with hard-coded IP
addresses in the rules that open port 9989.

Thanks for pointing me in the right direction.


On Fri, Jan 29, 2010 at 11:41 AM, Doug Latornell <djl at douglatornell.ca> wrote:
> Good thought.  There was no firewalling on the machines before the
> move (university environment :-) but I will check with the sysadmin to
> see if something has changed on that front. I think it would have to
> be a port thing though, because the machines are referred to by name
> in the buildbot.tac files.
> Unless there's a name to IP address cache somewhere in buildbot that
> I'm not seeing...
> Doug
> On Fri, Jan 29, 2010 at 11:20 AM, Mark Roddy <markroddy at gmail.com> wrote:
>> Did you check how the firewall on the server is configured?  If you
>> have exceptions for the remote slaves with hard coded IPs that would
>> explain it (I get bit by this w/buildbot after a move myself).
>> -Mark
>> On Fri, Jan 29, 2010 at 2:03 PM, Doug Latornell <djl at douglatornell.ca> wrote:
>>> 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
>>> ------------------------------------------------------------------------------
>>> The Planet: dedicated and managed hosting, cloud storage, colocation
>>> Stay online with enterprise data centers and the best network in the business
>>> Choose flexible plans and management services without long-term contracts
>>> Personal 24x7 support from experience hosting pros just a phone call away.
>>> http://p.sf.net/sfu/theplanet-com
>>> _______________________________________________
>>> Buildbot-devel mailing list
>>> Buildbot-devel at lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel

More information about the devel mailing list