Bug#753576: systemd stopped responding to dbus.socket connections

[Sam Morris]

On Thu, Jul 03, 2014 at 01:35:59PM +0200, Michael Biebl wrote:
> Am 03.07.2014 13:03, schrieb Sam Morris:
> > On Thu, Jul 03, 2014 at 12:30:14PM +0200, Michael Biebl wrote:
> >> If dbus is running (and it apparently is), then it should be the process
> >> listening on /var/run/dbus/system_bus_socket.
> > 
> > I'm not sure about that... on another system where dbus is currently
> > working fine:
> > 
> > # netstat -A unix -lnp | grep dbus
> > unix  2      [ ACC ]     STREAM     LISTENING     7809     1/systemd           /var/run/dbus/system_bus_socket
> 
> Well, the socket was opened by systemd, but they've been handed over to
> dbus-daemon and incoming requests on the socket should be processed by
> dbus-daemon.

Ah, so the output of netstat is misleading for .socket units. I did more
testing with strace and, on the working system, connecting to the socket
with socat does indeed only wake up the dbus process, not systemd.

> If you restart dbus.service (probably not a good idea to do that from
> within the X session), does the problem go away?
> 
> But before you do restart dbus, Simon, do you have any ideas how to
> debug this further?

Ok, I'll wait before trying this.

-- 
Sam Morris <https://robots.org.uk/>
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078