Bug 32043

Summary:	Failed to create socket, when path does not exists
Product:	systemd	Reporter:	Michal Vyskocil <mvyskocil>
Component:	general	Assignee:	Lennart Poettering <lennart>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Michal Vyskocil 2010-12-02 03:18:59 UTC

After start with --log-level=debug I found this in dmesg.

[  104.674323] systemd[1]: Using notification socket /org/freedesktop/systemd1/notify
[  104.687521] systemd[1]: Failed to get system D-Bus connection, retrying later: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
[  104.692660] systemd[1]: Failed to get API D-Bus connection, retrying later: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
[  104.698432] systemd[1]: Successfully created private D-Bus server.

I realized the dbusd is not running. The reason was /var/run/dbus directory was missing for unknown reason, so the socket() call ends with an error. Simple mkdir /var/run/dbus && sytemctl restart dbus.service fixed that.

Distribution: openSUSE 11.4, systemd-13-2.1.x86_64

BTW: I found few logs with the same error

red.fedorapeople.org/f14.systemd.dmesg
ausil.fedorapeople.org/dmesg
pastebin.com/SV3KHTye
pastebin.com/j3b13faz

Comment 1 Lennart Poettering 2011-01-20 15:44:15 UTC

This is actually simply misleading in systemd, those error messages should be ignored.

I have now changed systemd git to not generate these messages anymore.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.