Your message dated Sun, 27 May 2018 21:23:08 +0200
with message-id <[email protected]>
and subject line Re: Bug#753576: systemd stopped responding to dbus.socket
connections
has caused the Debian Bug report #753576,
regarding systemd stopped responding to dbus.socket connections
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
753576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753576
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
-- System Information:
Debian Release: 7.5
APT prefers stable
APT policy: (600, 'stable'), (590, 'stable-updates'), (570, 'testing'), (560,
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.51-8
ii adduser 3.113+nmu3
ii dpkg 1.16.15
ii initscripts 2.88dsf-41+deb7u1
ii libacl1 2.2.51-8
ii libaudit0 1:1.7.18-1.1
ii libc6 2.13-38+deb7u1
ii libcap2 1:2.22-1.2
ii libcap2-bin 1:2.22-1.2
ii libcryptsetup4 2:1.4.3-4
ii libdbus-1-3 1.6.8-1+deb7u3
ii libgcrypt11 1.5.0-5+deb7u1
ii libkmod2 9-3
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.3-7.1
ii libselinux1 2.1.9-5
ii libsystemd-daemon0 204-8~bpo70+1
ii libsystemd-journal0 204-8~bpo70+1
ii libsystemd-login0 204-8~bpo70+1
ii libudev1 204-8~bpo70+1
ii libwrap0 7.6.q-24
ii sysv-rc 2.88dsf-41+deb7u1
ii udev 204-8~bpo70+1
ii util-linux 2.20.1-5.3
Versions of packages systemd recommends:
ii libpam-systemd 204-8~bpo70+1
Versions of packages systemd suggests:
pn systemd-ui <none>
-- Configuration Files:
/etc/systemd/system.conf changed:
[Manager]
DefaultControllers=cpu memory blkio
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Sam
On Thu, 3 Jul 2014 13:00:53 +0100 Sam Morris <[email protected]> wrote:
> 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.
Looks like Simon never replied and I guess you rebooted in the mean
time. The original bug was filed against a very old version by now, so I
guess it's best to close this old bug report at this point.
Sorry we couldn't get to the bottom of this back then.
Regards,
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
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
