buildbot leaks dbus-daemon processes

Bug #667192 reported by Tom Haddon
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad Buildbot Configuration

Bug Description

We get number of processes alerts from buildbot because of the number of dbus-daemon processes that accumulate over time:

buildbot@pigeonpea:~$ ps fuwwxx | grep 'buildbot start' | grep -v grep
buildbot 362 0.0 0.3 76332 7372 ? Sl Oct14 0:27 /usr/bin/python /usr/bin/buildbot start /srv/buildbot/slaves/launchpad
buildbot@pigeonpea:~$ ps fuwwxx | grep dbus-daemon | grep -v grep | tail -1
buildbot 21191 0.0 0.0 29004 308 ? Ss Oct14 0:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
buildbot@pigeonpea:~$ ps fuwwxx | grep dbus-daemon | grep -v grep | wc -l

Tom Haddon (mthaddon)
tags: added: canonical-losa-lp
Revision history for this message
Tom Haddon (mthaddon) wrote :

Marking as "high" per recent LP/IS review call when operational issues were asked to be marked as "high" priority. This means we periodically need to restart buildbot instances and manually kill old dbus processes.

Changed in lpbuildbot:
status: New → Confirmed
importance: Undecided → High
Changed in lpbuildbot:
status: Confirmed → Triaged
Revision history for this message
Robert Collins (lifeless) wrote :

I've marked this paralleltest. I don't expect that feature to correct this situation, rather I expect it to obsolete it by running in containers that get shutdown. So when paralleltest is live on our CI environment (buildbot or not) this can be closed. Win.

tags: added: paralleltest
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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