One of the buildbots I monitor had some networking issues over the weekend and now seems to be in a weird state at the master. It is *not* running locally but when I try to start it I get: message from master: master already has a connection named 'sanitizer-ppc64le-linux' - checking its liveness and then it shuts down. The status on the web page shows it is "connected" but of course there is no slave actually connected and so it is not actually doing anything. http://lab.llvm.org:8011/builders/sanitizer-ppc64le-linux Is there something I can do from my end to fix this or must something be done at the master? Full log from buildbot start attempt: 2015-04-13 12:22:16-0400 [-] Starting factory <buildslave.bot.BotFactory instance at 0x3fffa3e236c8> 2015-04-13 12:22:16-0400 [-] Connecting to lab.llvm.org:9990 2015-04-13 12:22:17-0400 [Broker,client] message from master: master already has a connection named 'sanitizer-ppc64le-linux' - checking its liveness 2015-04-13 12:24:39-0400 [-] Received SIGTERM, shutting down. 2015-04-13 12:24:39-0400 [Broker,client] ReconnectingPBClientFactory.failedToGetPerspective 2015-04-13 12:24:39-0400 [Broker,client] we lost the brand-new connection 2015-04-13 12:24:39-0400 [Broker,client] Lost connection to lab.llvm.org:9990 2015-04-13 12:24:39-0400 [Broker,client] Stopping factory <buildslave.bot.BotFactory instance at 0x3fffa3e236c8> 2015-04-13 12:24:39-0400 [-] Main loop terminated. 2015-04-13 12:24:39-0400 [-] Server Shut Down. -- -Bill Seurer