Launchpad itself

orphaned dbus processes from test suite runs on lucid buildbot slave

Bug #607255 reported by Tom Haddon
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Unassigned

Bug Description

Per https://pastebin.canonical.com/34769/ we're seeing lots of orphaned dbus processes from the lucid buildbot slave.

Tom Haddon (mthaddon)
tags: added: build-infrastructure canonical-losa-lp
Revision history for this message
Gary Poster (gary) wrote :

https://dev.launchpad.net/Foundations/Proposals/SimplifyMergeMachinery might bring buildbot out of the picture...however, I wouldn't be surprised if the error still existed.

Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Tom Haddon (mthaddon) wrote :

Just saw this again:

mthaddon@pigeonpea:~$ ps auwwxx | grep '/bin/dbus-daemon --fork --print-pid 5 --print-address 7' |wc -l
213

Is there a workaround for this? Can we just kill the processes/restart dbus, etc.?

Revision history for this message
Gary Poster (gary) wrote :

Good idea. I suspect we can; I also suspect that we could include dbus in the killall script that buildbot runs at start. I'll ask Maris.

Revision history for this message
Gary Poster (gary) wrote :

Maris agrees that killing the processes sounds reasonable and easy

Changed in launchpad-foundations:
assignee: nobody → Māris Fogels (mars)
Revision history for this message
Gary Poster (gary) wrote :

also see bug 617354.

Gary Poster (gary)
Changed in launchpad:
assignee: Māris Fogels (mars) → nobody
William Grant (wgrant)
Changed in launchpad:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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