-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Tue, 31 Mar 2015 03:13:34 +0200 (CEST) "Carlos E. R." <carlos.e.r@opensuse.org> пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi,
Since recently, I think, I get these messages on the warn log when a cron job runs, on two computers at least:
<3.4> 2015-03-31 02:34:01 minas-tirith systemd 4025 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:38:01 minas-tirith systemd 4096 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:44:01 minas-tirith systemd 4195 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:45:01 minas-tirith systemd 4229 - - Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:48:01 minas-tirith systemd 4508 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:54:01 minas-tirith systemd 4627 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:58:01 minas-tirith systemd 4873 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 03:00:01 minas-tirith systemd 4955 - - Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory
User 0 is root, and 9 is news. Those directories do not exist, obviously. Should they? (they are not logged-in).
I do not have /run/use/$UID/dbus even though I'm logged in.
And those messages are spamming the warning log. Anything that goes to the warning log is supposedly VERY important. It the message is trivial, it is a bug to create them on warning level, IMO.
- -- Cheers Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith))
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iF4EAREIAAYFAlUZ9MoACgkQja8UbcUWM1yziAD+Pc2t90zgZWvI8j9EB68yWFFY QHJeqvwnAUciZiXnZl0A+wUgb+TUJhDGQ2jFINuvXg75u21IZsJ0IY33JOHUqMSL =0Zh3 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlUaEu0ACgkQR6LMutpd94yKZQCffDsP4/HL5nM1owlMDVF03acb GMoAn30u/rkTMRJb6OCvhiuNHRHWpKtd =qcUh -----END PGP SIGNATURE-----