Red Hat Bugzilla – Bug 375851
setroubleshoot gives error during boot
Last modified: 2008-01-10 12:20:20 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:188.8.131.52) Gecko/20071030 Fedora/184.108.40.206-2.fc8 Firefox/220.127.116.11
Description of problem:
I'm seeing this error in /var/log/messages on F8:
Nov 11 11:02:22 beverly setroubleshoot: [rpc.ERROR] exception DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory#012Traceback (most recent call last):#012 File "/usr/lib/python2.5/site-packages/setroubleshoot/server.py", line 434, in RunFaultServer#012 setroubleshootd_dbus = SetroubleshootdDBus()#012 File "/usr/lib/python2.5/site-packages/setroubleshoot/server.py", line 345, in __init__#012 self.bus = dbus.SystemBus()#012 File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 201, in __new__#012 private=private)#012 File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 107, in __new__#012 bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)#012 File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 121, in __new__#012 bus = cls._new_for_bus(address_or_type, mainloop=mainloop)#012DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. look for setroubleshoot errors in /var/log/messages
What selinux policy is install? This problem has been observed with older policies.
These are all the selinux rpms that are installed on this system:
Maybe the problem is a side-effect of a yum / rpm hang during the last update
cycle. yum did hang on selinux-policy-targeted-3.0.8-47.fc8. After waiting for 2
hours I canceled yum with CTRL-C and re-run it without an error. Strange this is
that now two selinux-policy-targeted are installed!?
did you reboot and does the problem persist?
You can safely remove the older rpm via rpm -e
Yes, the problem is still there after a reboot.
closer examination of the error message shows that the system message bus is not
running. What does
% chkconfig --list messagebus
say, is it on for your run level?
% service messagebus status
say, is it running?
I don't think this is a setroubleshoot issue, other than the face we shouldn't
generate an unhandled exception if the bus is not running. That has since been
fixed in the 2.0 series, we now catch the exception and just report the error,
but you're still going to get the error logged if you're attempting to run with
this critical system service.
I can't reproduce the problem any more. Maybe one of the updates that were
applied in the meantime fixed the issue. service messagebus is now running.