the dbus-daemon dropped down to normal levels last night. This morning, I killed dbus-daemon this morning and smf restarted the service.
This afternoon, it's back to 12% cpu usage. I got two errors when trying to connect to initially start dbus-monitor dbus-monitor --system Failed to open connection to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused dbus-monitor --system Failed to open connection to system message bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. I then restarted the dbus-daemon service and was able to connect run dbus-monitor. Hopefully dbus-monitor will capture when things go crazy. Any other suggestions on how to debug the system dbus-daemon? -- This message posted from opensolaris.org
