buildd-manager occasionally stops dispatching builds until it's restarted

Reported by Julian Edwards on 2010-10-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Julian Edwards

Bug Description

The symptoms are that the queue is not processed at all, and the log is full of errors like this:

2010-10-28 15:16:17+0000 [-] Dispatching: <ross:http://ross.buildd:8221/>
2010-10-28 15:16:17+0000 [-] Dispatching: <fermium:http://fermium.ppa:8221/>
2010-10-28 15:16:17+0000 [-] Dispatching: <berkelium:http://berkelium.ppa:8221/>
2010-10-28 15:16:17+0000 [-] Dispatching: <kaylaberry:http://kaylaberry.buildd:8221/>
2010-10-28 15:16:17+0000 [-] Dispatching: <gold:http://gold.ppa:8221/>
2010-10-28 15:16:17+0000 [-] Dispatching: <lakoocha:http://lakoocha.ppa:8221/>
2010-10-28 15:16:17+0000 [-] Dispatching: <promethium:http://promethium.ppa:8221/>
2010-10-28 15:16:17+0000 [-] Dispatching: <charichuelo:http://charichuelo.ppa:8221/>
2010-10-28 15:16:17+0000 [-] Dispatching: <americium:http://americium.ppa:8221/>
2010-10-28 15:16:17+0000 [-] Dispatching: <terranova:http://terranova.ppa:8221/>
2010-10-28 15:16:17+0000 [-] Dispatching: <protactinium:http://protactinium.ppa:8221/>
2010-10-28 15:16:24+0000 [-] <yellow:http://yellow.buildd:8221/> communication failed (User timeout caused connection failure.)
2010-10-28 15:16:24+0000 [-] <yellow:http://yellow.buildd:8221/> failure (None)
2010-10-28 15:16:24+0000 [-] <genip:http://genip.buildd:8221/> communication failed (User timeout caused connection failure.)
2010-10-28 15:16:24+0000 [-] <genip:http://genip.buildd:8221/> failure (None)
2010-10-28 15:16:24+0000 [-] <crested:http://crested.buildd:8221/> communication failed (User timeout caused connection failure.)
2010-10-28 15:16:24+0000 [-] <crested:http://crested.buildd:8221/> failure (None)
2010-10-28 15:16:24+0000 [-] <adare:http://adare.buildd:8221/> communication failed (User timeout caused connection failure.)
2010-10-28 15:16:25+0000 [-] <adare:http://adare.buildd:8221/> failure (None)
2010-10-28 15:16:25+0000 [-] <rothera:http://rothera.buildd:8221/> communication failed (User timeout caused connection failure.)
2010-10-28 15:16:25+0000 [-] <rothera:http://rothera.buildd:8221/> failure (None)
2010-10-28 15:16:25+0000 [-] <palmer:http://palmer.buildd:8221/> communication failed (User timeout caused connection failure.)
2010-10-28 15:16:25+0000 [-] <palmer:http://palmer.buildd:8221/> failure (None)
2010-10-28 15:16:25+0000 [-] <vernadsky:http://vernadsky.buildd:8221/> communication failed (User timeout caused connection failure.)
2010-10-28 15:16:25+0000 [-] <vernadsky:http://vernadsky.buildd:8221/> failure (None)
2010-10-28 15:16:31+0000 [-] <gourd:http://gourd.buildd:8221/> communication failed (User timeout caused connection failure.)
2010-10-28 15:16:40+0000 [-] <gourd:http://gourd.buildd:8221/> failure (None)
2010-10-28 15:16:41+0000 [-] <hubbard:http://hubbard.buildd:8221/> communication failed (User timeout caused connection failure.)

Related branches

Julian Edwards (julian-edwards) wrote :

This might be fixed with the re-written b-m that's about to deploy, let's leave this open for a while and see if it happens again.

Changed in soyuz:
status: New → Triaged
importance: Undecided → High
tags: added: buildd-manager
Changed in soyuz:
assignee: nobody → Julian Edwards (julian-edwards)
status: Triaged → Fix Released
milestone: none → 10.11
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers