dbus and avahi-daemon not started after package install

Bug #1065775 reported by Diogo Matsubara
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
New
Undecided
Unassigned

Bug Description

After installing maas 0.1+bzr1264+dfsg-0+1264+133~ppa0~quantal1 dbus and avahi-daemon are not started causing this error in /var/log/apache2/error.log

eNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] mod_wsgi (pid=10965): Target WSGI script '/usr/share/maas/wsgi.py' cannot be loaded as Python module.
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] mod_wsgi (pid=10965): Exception occurred processing WSGI script '/usr/share/maas/wsgi.py'.
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] Traceback (most recent call last):
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] File "/usr/share/maas/wsgi.py", line 30, in <module>
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] start_up()
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] File "/usr/lib/python2.7/dist-packages/maasserver/start_up.py", line 59, in start_up
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] inner_start_up()
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] File "/usr/lib/python2.7/dist-packages/maasserver/start_up.py", line 81, in inner_start_up
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] setup_maas_avahi_service()
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] File "/usr/lib/python2.7/dist-packages/maasserver/maasavahi.py", line 52, in setup_maas_avahi_service
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] service.publish()
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] File "/usr/lib/python2.7/dist-packages/maasserver/maasavahi.py", line 44, in publish
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] self.service.publish()
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] File "/usr/lib/python2.7/dist-packages/maasserver/zeroconfservice.py", line 44, in publish
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] bus = dbus.SystemBus()
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 194, in __new__
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] private=private)
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 100, in __new__
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 122, in __new__
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
[Fri Oct 12 00:38:23 2012] [error] [client 10.98.0.13] DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

Restarting both services and apache2 makes the web ui work again.

Tags: sru-12.10
description: updated
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

I routinely see these problems when running tests in a dev branch, depending on where I am. The problem seems to be that Avahi may decide to exit after starting if it sees that it's not on the right kind of network.

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

I should add that for some reason, restarting the avahi service manually fixes it for me.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

I see this in /var/log/apt/term.log:

Setting up libdaemon0 (0.14-2build1) ...
Setting up avahi-daemon (0.6.31-1ubuntu2) ...
reload: Unknown instance:
invoke-rc.d: initscript dbus, action "force-reload" failed.
avahi-daemon start/running, process 11443
Setting up dbconfig-common (1.8.47+nmu1) ...

Changed in maas:
importance: Undecided → Critical
tags: added: sru-12.10
no longer affects: maas (Ubuntu)
no longer affects: maas
Revision history for this message
Diogo Matsubara (matsubara) wrote :
Revision history for this message
Diogo Matsubara (matsubara) wrote :
Revision history for this message
Diogo Matsubara (matsubara) wrote :
Revision history for this message
Diogo Matsubara (matsubara) wrote :

<roaksoax> ubuntu@autopkgtest:/etc$ grep -sr haldaemon *
<roaksoax> dbus-1/system.d/landscape.conf: <policy user="haldaemon">

Changed in dbus (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for dbus (Ubuntu) because there has been no activity for 60 days.]

Changed in dbus (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Diogo Matsubara (matsubara) wrote :

I just reproduced this bug on a pristine saucy VM running MAAS: 1.4+bzr1701+dfsg-0+1727+212~ppa0~ubuntu13.10.1

After I installed MAAS (apt-get install maas maas-dns maas-dhcp), both avahi-daemon and dbus services were not running causing the same error in apache logs I originally posted in this bug.

Changed in dbus (Ubuntu):
status: Expired → New
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.