Closed Bug 815754 Opened 13 years ago Closed 12 years ago

slave disconnection doesn't work on tegra or panda masters

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: bhearsum, Unassigned)

Details

We get this over and over and over: 2012-11-27 12:25:21-0800 [-] didn't hear back from slave in 30 seconds; killing existing connection 2012-11-27 12:25:21-0800 [-] disconnecting old slave tegra-315 now 2012-11-27 12:25:21-0800 [-] waiting for slave to finish disconnecting Marking as "major" because this regularly hangs reconfigs and wastes human time.
Anythin gwe can do here? Whenever we need to graceful shutdown these masters we end up increasing wait times for tegra jobs. It sucks.
Looks like this is a problem on panda masters too: 2013-01-09 07:30:23-0800 [Broker,280,10.12.136.21] duplicate slave panda-0850; rejecting new slave and pinging old 2013-01-09 07:30:53-0800 [-] disconnecting old slave panda-0850 now 2013-01-09 07:32:47-0800 [Broker,281,10.12.136.21] duplicate slave panda-0850; rejecting new slave and pinging old 2013-01-09 07:33:17-0800 [-] disconnecting old slave panda-0850 now 2013-01-09 07:34:24-0800 [Broker,282,10.12.136.21] duplicate slave panda-0850; rejecting new slave and pinging old 2013-01-09 07:34:54-0800 [-] disconnecting old slave panda-0850 now 2013-01-09 07:36:25-0800 [Broker,283,10.12.136.21] duplicate slave panda-0850; rejecting new slave and pinging old 2013-01-09 07:36:55-0800 [-] disconnecting old slave panda-0850 now 2013-01-09 07:38:25-0800 [Broker,285,10.12.136.21] duplicate slave panda-0850; rejecting new slave and pinging old 2013-01-09 07:38:55-0800 [-] disconnecting old slave panda-0850 now 2013-01-09 07:41:20-0800 [Broker,286,10.12.136.21] duplicate slave panda-0850; rejecting new slave and pinging old 2013-01-09 07:41:50-0800 [-] disconnecting old slave panda-0850 now 2013-01-09 07:43:27-0800 [Broker,287,10.12.136.21] duplicate slave panda-0850; rejecting new slave and pinging old 2013-01-09 07:43:57-0800 [-] disconnecting old slave panda-0850 now 2013-01-09 07:45:27-0800 [Broker,288,10.12.136.21] duplicate slave panda-0850; rejecting new slave and pinging old 2013-01-09 07:45:57-0800 [-] disconnecting old slave panda-0850 now 2013-01-09 07:47:28-0800 [Broker,289,10.12.136.21] duplicate slave panda-0850; rejecting new slave and pinging old 2013-01-09 07:47:58-0800 [-] disconnecting old slave panda-0850 now 2013-01-09 07:48:28-0800 [Broker,290,10.12.136.21] duplicate slave panda-0850; rejecting new slave and pinging old 2013-01-09 07:48:58-0800 [-] disconnecting old slave panda-0850 now 2013-01-09 07:50:29-0800 [Broker,293,10.12.136.21] duplicate slave panda-0850; rejecting new slave and pinging old
Summary: slave disconnection doesn't work on tegra masters → slave disconnection doesn't work on tegra or panda masters
Hasn't been a problem in a while.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.