build-master isn't removing its pidfile when stopped

Bug #751129 reported by Tom Haddon
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

The build-master isn't removing it's pidfile when stopped, which is making the nodowntime rollout fail because the service check gets confused looking for a process (based on the existence of a pidfile) that no longer exists.

Revision history for this message
Tom Haddon (mthaddon) wrote :

I guess I should mention that it's running "bin/killservice --wait=60 buildd-manager".

tags: added: canonical-losa-lp
Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Francis J. Lacoste (flacoste) wrote : Re: build-master isn't removing up it's pidfile when stopped

Downgrading to High as their is a work-around implemented in the initscript wrapper which removes the PID file after bin/killservice completes

summary: - build-master initscript isn't removing up it's pidfile
+ build-master isn't removing up it's pidfile when stopped
Changed in launchpad:
importance: Critical → High
tags: added: critical-analysis
summary: - build-master isn't removing up it's pidfile when stopped
+ build-master isn't removing its pidfile when stopped
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.