On Tue, 23.05.17 23:01, prashantkumar dhotre (prashantkumardho...@gmail.com) wrote:
> Thanks. > my service runs during early bootup. > one intermittent issue I am seeing is that my service fails in > dbus_bus_get_private() with error: > > 07:45:19 : dbus_bus_get_private() failed with error: Failed to > connect to socket /var/run/dbus/system_bus_socket: No such file or > directory > > > dbus service started at 07:44:34 and my service started at 07:45:19 > which is 45 sec after dbus and also I see > /var/run/dbus/system_bus_socket present before this error. > not sure why dbus API is failing even though the socket is present. > So am I missing to add any dependency in my service file ? Maybe you haven#t configured dbus for socket activation, and dbus-daemon replaces the sockets already created or so? Also, /var/run is an old name for /run, and should nowadays just be a symlink. Is it possible that symlink is missing for you? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
