Bug#753576: systemd stopped responding to dbus.socket connections
Oh, wait. I forgot step 0. Update and upgrade first. It's such a habit that I lump it in with importing the VMs. On 17-02-27 04:04 AM, Stephan Sokolow (You actually CAN reply) wrote: I'm not sure if it's the same problem, but, I have something that at least has similar symptoms which may be easier to reproduce: Release: The VirtualBox version of the bento/debian-8.6 Vagrant VM Reproduction: 1. apt-get install systemd-cron 2. Futz around until you realize jessie's systemd is too old to support hourly cronjobs. 3. apt-get install cron (without rebooting in between) On my VM, the attempt to reinstall started encountering timeouts when it attempted to setup the newly-installed packages and, from then on, any attempt to use `systemctl` resulted in `org.freedesktop.systemd1` timeouts. (To the point that Vagrant would error out unless I reset the VM because anything less drastic would die while trying to ask for a clean shutdown.) (I don't think my "trim it down further" ansible playbook touches anything relevant to this but it's also available on request.) -- Stephan Sokolow Note: My e-mail address IS valid. It's a little trick I use to fool "smarter" spambots and remind friends and family to use the custom aliases I gave them.
Bug#753576: systemd stopped responding to dbus.socket connections
I'm not sure if it's the same problem, but, I have something that at least has similar symptoms which may be easier to reproduce: Release: The VirtualBox version of the bento/debian-8.6 Vagrant VM Reproduction: 1. apt-get install systemd-cron 2. Futz around until you realize jessie's systemd is too old to support hourly cronjobs. 3. apt-get install cron (without rebooting in between) On my VM, the attempt to reinstall started encountering timeouts when it attempted to setup the newly-installed packages and, from then on, any attempt to use `systemctl` resulted in `org.freedesktop.systemd1` timeouts. (To the point that Vagrant would error out unless I reset the VM because anything less drastic would die while trying to ask for a clean shutdown.) (I don't think my "trim it down further" ansible playbook touches anything relevant to this but it's also available on request.) -- Stephan Sokolow Note: My e-mail address IS valid. It's a little trick I use to fool "smarter" spambots and remind friends and family to use the custom aliases I gave them.
Bug#753576: systemd stopped responding to dbus.socket connections
Package: systemd Version: 204-8~bpo70+1 Severity: normal My desktop has been up for 31 days. Today I noticed I could no longer connect to the system dbus daemon. I'll leave the system up as long as possible in case you need me to get any further information. # dbus-monitor --system Failed to open connection to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused # socat /run/dbus/system_bus_socket /dev/tty 2014/07/03 09:52:43 socat[24226] E connect(3, AF=1 /run/dbus/system_bus_socket, 29): Connection refused # sudo netstat -A unix -lnp | grep system_bus_socket unix 2 [ ACC ] STREAM LISTENING 7606 1/systemd /var/run/dbus/system_bus_socket # systemctl status dbus.socket dbus.socket - D-Bus System Message Bus Socket Loaded: loaded (/lib/systemd/system/dbus.socket; static) Active: active (running) since Mon 2014-06-02 09:51:06 BST; 1 months 0 days ago Listen: /var/run/dbus/system_bus_socket (Stream) Jun 02 09:51:06 oxylus systemd[1]: Starting D-Bus System Message Bus Socket. Jun 02 09:51:06 oxylus systemd[1]: Listening on D-Bus System Message Bus Socket. # systemctl status dbus.service dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static) Active: active (running) since Mon 2014-06-02 09:51:06 BST; 1 months 0 days ago Main PID: 1124 (dbus-daemon) CGroup: name=systemd:/system/dbus.service ├─1124 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation ├─1566 /usr/sbin/modem-manager └─1680 /usr/lib/accountsservice/accounts-daemon Jul 03 07:56:16 oxylus dbus-daemon[1124]: dbus[1124]: [system] Activated service 'org.freedesktop.PackageKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5 Jul 03 07:56:16 oxylus dbus[1124]: [system] Activated service 'org.freedesktop.PackageKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5 Jul 03 08:56:16 oxylus dbus-daemon[1124]: dbus[1124]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Jul 03 08:56:16 oxylus dbus[1124]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Jul 03 08:56:16 oxylus dbus-daemon[1124]: (packagekitd:22845): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion `G_IS_DBUS_CONNECTION (connection)' failed Jul 03 08:56:16 oxylus dbus-daemon[1124]: (packagekitd:22845): GLib-GObject-WARNING **: invalid (NULL) pointer instance Jul 03 08:56:16 oxylus dbus-daemon[1124]: (packagekitd:22845): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed Jul 03 08:56:17 oxylus dbus-daemon[1124]: (packagekitd:22845): PackageKit-ERROR **: failed to get pokit authority: Error initializing authority: Could not connect: Connection refused Jul 03 08:56:17 oxylus dbus-daemon[1124]: dbus[1124]: [system] Activated service 'org.freedesktop.PackageKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5 Jul 03 08:56:17 oxylus dbus[1124]: [system] Activated service 'org.freedesktop.PackageKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5 -- Package-specific info: -- systemd-delta: -- [MASKED] /etc/udev/rules.d/75-cd-aliases-generator.rules → /lib/udev/rules.d/75-cd-aliases-generator.rules 1 overridden configuration files found. -- systemctl dump: -- -- Contents of /var/lib/systemd/deb-systemd-helper-enabled: -- == /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/anacron.service == /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also == /etc/systemd/system/sockets.target.wants/ssh.socket == /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also == /etc/systemd/system/multi-user.target.wants/ssh.service /etc/systemd/system/sshd.service == /var/lib/systemd/deb-systemd-helper-enabled/sshd.service == == /var/lib/systemd/deb-systemd-helper-enabled/syslog.service == == /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also == /etc/systemd/system/multi-user.target.wants/rsyslog.service /etc/systemd/system/syslog.service == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/docker.io.service == == /var/lib/systemd/deb-systemd-helper-enabled/docker.io.service.dsh-also == /etc/systemd/system/multi-user.target.wants/docker.io.service --
Bug#753576: systemd stopped responding to dbus.socket connections
Am 03.07.2014 11:16, schrieb Sam Morris: Package: systemd Version: 204-8~bpo70+1 Severity: normal My desktop has been up for 31 days. Today I noticed I could no longer connect to the system dbus daemon. I'll leave the system up as long as possible in case you need me to get any further information. # dbus-monitor --system Failed to open connection to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused # socat /run/dbus/system_bus_socket /dev/tty 2014/07/03 09:52:43 socat[24226] E connect(3, AF=1 /run/dbus/system_bus_socket, 29): Connection refused # sudo netstat -A unix -lnp | grep system_bus_socket unix 2 [ ACC ] STREAM LISTENING 7606 1/systemd /var/run/dbus/system_bus_socket # systemctl status dbus.socket dbus.socket - D-Bus System Message Bus Socket Loaded: loaded (/lib/systemd/system/dbus.socket; static) Active: active (running) since Mon 2014-06-02 09:51:06 BST; 1 months 0 days ago Listen: /var/run/dbus/system_bus_socket (Stream) Jun 02 09:51:06 oxylus systemd[1]: Starting D-Bus System Message Bus Socket. Jun 02 09:51:06 oxylus systemd[1]: Listening on D-Bus System Message Bus Socket. # systemctl status dbus.service dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static) Active: active (running) since Mon 2014-06-02 09:51:06 BST; 1 months 0 days ago Main PID: 1124 (dbus-daemon) CGroup: name=systemd:/system/dbus.service ├─1124 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation ├─1566 /usr/sbin/modem-manager └─1680 /usr/lib/accountsservice/accounts-daemon Jul 03 07:56:16 oxylus dbus-daemon[1124]: dbus[1124]: [system] Activated service 'org.freedesktop.PackageKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5 Jul 03 07:56:16 oxylus dbus[1124]: [system] Activated service 'org.freedesktop.PackageKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5 Jul 03 08:56:16 oxylus dbus-daemon[1124]: dbus[1124]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Jul 03 08:56:16 oxylus dbus[1124]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Jul 03 08:56:16 oxylus dbus-daemon[1124]: (packagekitd:22845): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion `G_IS_DBUS_CONNECTION (connection)' failed Jul 03 08:56:16 oxylus dbus-daemon[1124]: (packagekitd:22845): GLib-GObject-WARNING **: invalid (NULL) pointer instance Jul 03 08:56:16 oxylus dbus-daemon[1124]: (packagekitd:22845): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed Jul 03 08:56:17 oxylus dbus-daemon[1124]: (packagekitd:22845): PackageKit-ERROR **: failed to get pokit authority: Error initializing authority: Could not connect: Connection refused Jul 03 08:56:17 oxylus dbus-daemon[1124]: dbus[1124]: [system] Activated service 'org.freedesktop.PackageKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5 Jul 03 08:56:17 oxylus dbus[1124]: [system] Activated service 'org.freedesktop.PackageKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5 That looks like a dbus problem to me. If dbus is running (and it apparently is), then it should be the process listening on /var/run/dbus/system_bus_socket. Does strace -p 1124 reveal anything useful? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#753576: systemd stopped responding to dbus.socket connections
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 Does strace -p 1124 reveal anything useful? I ran strace on both dbus and systemd. Both remain sleeping epoll_wait during the attempt to connect to the socket. -- Sam Morris https://robots.org.uk/ 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753576: systemd stopped responding to dbus.socket connections
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. 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? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#753576: systemd stopped responding to dbus.socket connections
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
