[Buildbot-commits] [Buildbot] #2383: Configuration of the ports for slaves

Buildbot nobody at buildbot.net
Tue Oct 30 03:25:20 UTC 2012


#2383: Configuration of the ports for slaves
----------------------------+------------------------
Reporter:  metronomy        |       Owner:
    Type:  support-request  |      Status:  closed
Priority:  critical         |   Milestone:  undecided
 Version:  0.8.7            |  Resolution:  fixed
Keywords:                   |
----------------------------+------------------------
Changes (by tom.prince):

 * status:  new => closed
 * resolution:   => fixed


Old description:

> Hello,
>
> I am still a beginner concerning configuration of buildbot.
>
> I created a new slave in another PC. When I start the slave, it tries to
> connect to the master but without success.
>
> Here is an overview of the content of the twistd.log file:
>
> {{{
> 2012-10-15 14:37:16+0200 [-] Log opened.
> 2012-10-15 14:37:16+0200 [-] twistd 11.0.0 (C:\Python27\python.exe 2.7.2)
> starting up.
> 2012-10-15 14:37:16+0200 [-] reactor class:
> twisted.internet.selectreactor.SelectReactor.
> 2012-10-15 14:37:16+0200 [-] Starting BuildSlave -- version: 0.8.4
> 2012-10-15 14:37:16+0200 [-] recording hostname in twistd.hostname
> 2012-10-15 14:37:21+0200 [-] Starting factory <buildslave.bot.BotFactory
> instance at 0x0131DD28>
> 2012-10-15 14:37:21+0200 [-] Connecting to trinity.muc.lantiq.com:20400
> 2012-10-15 14:37:21+0200 [-] Connection to trinity.muc.lantiq.com:20400
> failed: [Failure instance: Traceback (failure with no frames): <class
> 'twisted.internet.error.DNSLookupError'>: DNS lookup failed: address
> 'trinity.muc.lantiq.com' not found: [Errno 11001] getaddrinfo failed.
> }}}
>
> Do you have information about this issue?
>
> By the way, the port number for the new slave should be the same as the
> first slave?
>
> For the moment, I configured the master.cfg file like this:
>
> {{{
> c = BuildmasterConfig = {}
>
> s1 = BuildSlave("Nightly_PC", "root")
> s2 = BuildSlave("Uli8", "root")
>
> c['slaves'] = [s1,s2]
>
> c['slavePortnum'] = 20400
>

> Thanks in advance!
>
> Metronomy
> }}}

New description:

 Hello,

 I am still a beginner concerning configuration of buildbot.

 I created a new slave in another PC. When I start the slave, it tries to
 connect to the master but without success.

 Here is an overview of the content of the twistd.log file:

 {{{
 2012-10-15 14:37:16+0200 [-] Log opened.
 2012-10-15 14:37:16+0200 [-] twistd 11.0.0 (C:\Python27\python.exe 2.7.2)
 starting up.
 2012-10-15 14:37:16+0200 [-] reactor class:
 twisted.internet.selectreactor.SelectReactor.
 2012-10-15 14:37:16+0200 [-] Starting BuildSlave -- version: 0.8.4
 2012-10-15 14:37:16+0200 [-] recording hostname in twistd.hostname
 2012-10-15 14:37:21+0200 [-] Starting factory <buildslave.bot.BotFactory
 instance at 0x0131DD28>
 2012-10-15 14:37:21+0200 [-] Connecting to trinity.muc.lantiq.com:20400
 2012-10-15 14:37:21+0200 [-] Connection to trinity.muc.lantiq.com:20400
 failed: [Failure instance: Traceback (failure with no frames): <class
 'twisted.internet.error.DNSLookupError'>: DNS lookup failed: address
 'trinity.muc.lantiq.com' not found: [Errno 11001] getaddrinfo failed.
 }}}

 Do you have information about this issue?

 By the way, the port number for the new slave should be the same as the
 first slave?

 For the moment, I configured the master.cfg file like this:

 {{{
 c = BuildmasterConfig = {}

 s1 = BuildSlave("Nightly_PC", "root")
 s2 = BuildSlave("Uli8", "root")

 c['slaves'] = [s1,s2]

 c['slavePortnum'] = 20400
 }}}

 Thanks in advance!

 Metronomy

--

Comment:

 The problem is that the slave isn't resolving the name
 `trinity.muc.lantiq.com`. Also, all the slaves use the same port to talk
 to the master (the port is a listening port on the master that the slaves
 connect to).

-- 
Ticket URL: <http://trac.buildbot.net/ticket/2383#comment:2>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation


More information about the Commits mailing list