[users at bb.net] FW: Issue connecting slave to master

Tue Jun 20 12:15:16 UTC 2017

Colin,
Its a bit harder to me to efficiently help you as 0.8.8 is quite an old
version. I imagine upgrading is not an option..

it might be an incompatibility of the slave version string. We usually try
to maintain compatibility for new master version to old slave version, but
we might not always take care of supporting running new slaves with older
master.
Did you try downgrading your slave version to 0.8.8?

Pierre

On Tue, Jun 20, 2017 at 11:53 AM Colin Chargy <Colin.Chargy at bentley.com>
wrote:

> Hi Pierre,
>
> Thanks for your reply.
>
> Indeed, I’ve seen in the failedToGetPerspective doc that it could fail
> with a wrong login password. However, the slave name and password seems
> correct (ie the same on the slave .toc file and on the server config). We
> also tested multiple login/password couple to see if that changes anything
> (with no luck). The TCP dump seems to show that the last things which are
>  sent are  the host name and slave info which are the default one (I tried
> modify them with no luck). What happen after/inside failedToGetPerspective
> ? Does the connection changes port/connection/setting or anything else at
> this point ?
>
>
>
> I should probably add about info our set up : the server runs 2 buildbot
> masters and the slave computer also 2 buildbot slave (one for each master).
> We do have other computer that work that way without any problem. Of
> course, we checked that each slave is connecting to the correct master.
> Only one of the slave/master couple fails (and as already said, only on
> this computer).
>
>
>
> Best regards,
>
> Colin Chargy
>
>
>
> *From:* Pierre Tardy [mailto:tardyp at gmail.com]
> *Sent:* Tuesday, June 20, 2017 11:41
> *To:* Colin Chargy <Colin.Chargy at bentley.com>; users at buildbot.net
> *Subject:* Re: [users at bb.net] FW: Issue connecting slave to master
>
>
>
> Hi Colin
>
> Could that be a problem with your slave password?
>
>
>
>
>
>  def failedToGetPerspective(self, why):
>
>         """The login process failed, most likely because of an
> authorization
>
>         failure (bad password), but it is also possible that we lost the
> new
>
>         connection before we managed to send our credentials.
>
>         """
>
>         log.msg("ReconnectingPBClientFactory.failedToGetPerspective")
>
>         if why.check(pb.PBConnectionLost):
>
>             log.msg("we lost the brand-new connection")
>
>             # retrying might help here, let clientConnectionLost decide
>
>             return
>
>         # probably authorization
>
>         self.stopTrying()  # logging in harder won't help
>
>         log.err(why)
>
>
>
>
>
> On Tue, Jun 20, 2017 at 9:18 AM Colin Chargy <Colin.Chargy at bentley.com>
> wrote:
>
> Hi everyone,
> Before I start describing my issue, let me say to we have dozen of slaves
> (Win, Mac and Linux platform perfectly working right now), only one is
> problematic :
> We are facing an issue with slave connection to master. Here is the log on
> the slave side (see enclosed twisted.log for complete log) :
> [Broker,client] message from master: attached [Broker,client]
> ReconnectingPBClientFactory.failedToGetPerspective
> [Broker,client] we lost the brand-new connection [Broker,client] Lost
> connection to 192.168.0.1:9989 [Broker,client]
> <twisted.internet.tcp.Connector instance at 0x03471918> will retry in 3
> seconds
>
> And it starts it again.
> On the server side, the following log is produced :
> 2017-06-19 16:11:27+0200 [Broker,9423,192.168.0.254] slave
> 'lrttestauto-test' attaching from IPv4Address(TCP, '192.168.0.254', 35524)
> 2017-06-19 16:11:27+0200 [Broker,9423,192.168.0.254] Starting buildslave
> keepalive timer for 'lrttestauto-test'
> 2017-06-19 16:11:27+0200 [Broker,9423,192.168.0.254] Peer will receive
> following PB traceback:
> 2017-06-19 16:11:27+0200 [Broker,9423,192.168.0.254] Unhandled Error
>         Traceback (most recent call last):
>         Failure: twisted.spread.pb.PBConnectionLost: [Failure instance:
> Traceback (failure with no frames): <class
> 'twisted.internet.error.ConnectionLost'>: Connection to the other side was
> lost in a non-clean fashion.
>         ]
>
> I've checked that the login and password are correct and Buildbot version
> are the following :
> On the server-side (which is a Debian):
> Buildbot version: 0.8.8
> Twisted version: 12.3.0
>
> On the slave side (which is a Windows 10, buildslave installed via pip):
> Buildslave version: 0.8.14
> Twisted version: 17.5.0
>
> I've enclosed the slave log, the slave tac file and a tcpdump showing data
> transfer between slave and server (I've tried to debug it with Wireshark
> with no luck).
>
> What can I do to debug or to solve this issue ?
>
> Best regards,
> Colin Chargy
> _______________________________________________
> users mailing list
> users at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20170620/c1db5eea/attachment.html>