[Buildbot-devel] Slaves behind Dynamic IPs

[Michael Parker]

Howdy,

I have a couple of slaves behind dynamic IP addresses.  When the IP
address changes they are no longer able to talk to the master, getting
this traceback:

2004/11/27 14:14 CST [Broker,client] Traceback from remote host --
Traceback (most recent call last):
          File
          "/usr/lib/python2.2/site-packages/twisted/spread/pb.py",
          line 1734, in remote_respond
            d = self.portalWrapper.portal.login(self, mind,
            IPerspective)
          File
          "/usr/lib/python2.2/site-packages/twisted/cred/portal.py",
          line 94, in login
            return maybeDeferred(c.requestAvatarId, credentials
          File
          "/usr/lib/python2.2/site-packages/twisted/internet/defer.py", line 214, in addCallback
            callbackKeywords=kw)
          File
          "/usr/lib/python2.2/site-packages/twisted/internet/defer.py", line 205, in addCallbacks
            self._runCallbacks()
        --- <exception caught here> ---
          File
          "/usr/lib/python2.2/site-packages/twisted/internet/defer.py", line 338, in _runCallbacks
            self.result = callback(self.result, *args, **kw)
          File "/usr/lib/python2.2/site-packages/buildbot/master.py",
          line 474, in requestAvatar
            p = self.botmaster.getPerspective(avatarID)
          File "/usr/lib/python2.2/site-packages/buildbot/master.py",
          line 322, in getPerspective
            raise ValueError("duplicate slave, old one connected from
            %s" \
        exceptions.ValueError: duplicate slave, old one connected from
        IPv4Address(TCP, 'NNN.NNN.NNN.NNN', 33447)
        

Is there something that can be set on the master side, or run on the
slave side to clear up the old IP and allow a connection from the new?

Thanks
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://buildbot.net/pipermail/devel/attachments/20041128/7a4d084f/attachment.bin>