Opened 10 years ago

Closed 10 years ago

#745 closed defect (worksforme)

Initial slave connection can be slow

Reported by: catlee Owned by:
Priority: major Milestone: 0.8.0
Version: master Keywords:


Slaves can sometimes take more than 10 seconds to connect to the master.

now restarting buildbot process..
Following twistd.log until startup finished..
2010-03-16 11:44:26-0400 [-] Log opened.
2010-03-16 11:44:26-0400 [-] twistd 10.0.0 (/home/catlee/.virtualenvs/buildbot.git/bin/python2.4 2.4.6) starting up.
2010-03-16 11:44:26-0400 [-] reactor class: twisted.internet.selectreactor.SelectReactor.
2010-03-16 11:44:26-0400 [-] Starting factory < instance at 0x7f75279485a8>

The buildmaster took more than 10 seconds to start, so we were unable to
confirm that it started correctly. Please 'tail twistd.log' and look for a
line that says 'configuration update complete' to verify correct startup.

Change History (5)

comment:1 Changed 10 years ago by dustin

Hmm, my slaves still start in less than 10s, but maybe it takes longer due to database lookups? Is this in the Mozilla staging environment? If so, I wonder if the master is doing a lot of db operations during that time?

To be clear: the slave *does* eventually start up, right?

comment:2 Changed 10 years ago by catlee

Yes, the slave *does* eventually start up. I just discovered something interesting today while testing this. After the slave outputs Starting factory < instance at 0xXXXXXXXXXXXX> and hangs, if I hit Ctrl-C, the slave then immediately connects, according to the master's log.

According to netstat, the slave hasn't even tried to open a socket to the master at this point.

comment:3 Changed 10 years ago by dustin

What Twisted version?

comment:4 Changed 10 years ago by catlee

both 9.0 and 10.0

comment:5 Changed 10 years ago by catlee

  • Resolution set to worksforme
  • Status changed from new to closed

Post reboot, this is working fine now.

Note: See TracTickets for help on using tickets.