ReleaseEngineering/How To/Handle an Idle Slave

From MozillaWiki
Jump to: navigation, search

We are working toward not having slaves go idle, but progress is slow.

The nagios alert is currently set for four days. The current strategy is just to reboot them, which should buy another 4 hours and flush any oddities in the master/slave communication:

  • check buildbot.tac to ensure the slave is enabled and see which master it's on.
  • tail twistd.log to see if the slave is really idle. In most cases, the slave has been idle since it started up. Note any differences.
  • Reboot. Don't use `buildbot restart`, since it won't work on macs!