Edgewall Software
Modify

Opened 16 years ago

Closed 15 years ago

#395 closed defect (duplicate)

Slave quits when it can't connect to the master

Reported by: kauschovar@… Owned by: cmlenz
Priority: major Milestone:
Component: Build slave Version: dev
Keywords: Cc:
Operating System: Linux

Description

Every few days, I notice my build slave is not running anymore. When I check the log, I see the following:

2009-04-27 00:11:47,436 [bitten.slave] INFO: No pending builds
2009-04-27 00:12:47,954 [bitten.slave] INFO: No pending builds
2009-04-27 00:13:59,961 [bitten.slave] ERROR: <urlopen error (113, 'No route to host')>

That's always the last line in the log file, which tells me bitten quits as soon as it can't connect to the master. The behavior I would expect is that the slave would log the error and keep trying, because sometimes hosts or routers are rebooted.

bitten-slave --version reports:

bitten-slave 0.6dev-r567

Attachments (0)

Change History (1)

comment:1 Changed 15 years ago by osimons

  • Milestone 0.6 deleted
  • Resolution set to duplicate
  • Status changed from new to closed

This is the same issue requested later by #403, but as that ticket also contains patches I'm closing this one as a duplicate. Please add any opinions about how best to solve this on that ticket.

Add Comment

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain cmlenz.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.