Linux ChromiumOS MSAN {Builder,Tests} are offline (slave{150,151}-c1) |
|||
Issue description
Linux ChromiumOS MSAN {Builder,Tests} are offline (slave{150,151}-c1).
This appears to be fallout from my attempts to migrate the builders that were on the chromium.memory.full waterfall to the chromium.memory waterfall.
It looks like the slaves cannot connect to the new master.
From the buildbot log on slave150-c1, for example:
2017-04-12 19:24:05-0700 [-] Starting factory <buildslave.bot.BotFactory instance at 0x7f7632fa1680>
2017-04-12 19:24:05-0700 [-] Connecting to master1.golo.chromium.org:8112
2017-04-12 19:24:05-0700 [Uninitialized] Connection to master1.golo.chromium.org:8112 failed: Connection Refused
2017-04-12 19:24:05-0700 [Uninitialized] <twisted.internet.tcp.Connector instance at 0x7f76335628c0> will retry in 313 seconds
I do not know what is refusing the connection, but I saw no sign of it the master's twistd.log, so maybe there's some sort of firewall rule in effect?
I don't think fixing this is an emergency, as I think these builders were a bit unmonitored prior to the master merger, but hopefully we can get to this in the morning MTV time.
,
Apr 13 2017
,
Apr 13 2017
Had to add respective vserver to the netscalers for master.chromium.memory
,
Apr 13 2017
Thanks! Is there a way in the future I can know whether or not these sort of things might be needed?
,
Apr 13 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome-golo/chrome-golo/+/53d2afaac5640a4bc867960b69c1fe67b623a0ee commit 53d2afaac5640a4bc867960b69c1fe67b623a0ee Author: Peter Schmidt <pschmidt@google.com> Date: Thu Apr 13 17:06:59 2017 |
|||
►
Sign in to add a comment |
|||
Comment 1 by dpranke@chromium.org
, Apr 13 2017