-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
Date: Mon, 26 Jan 2015 12:53:22 +0100 (CET) To: OS-EN
Subject: systemd says "Failed to open private bus connection: ... /run/user/9/dbus/user_bus_socket"
Hi, I get this entry in the _warning_ log: <3.4> 2015-01-26 12:23:01 Telcontar systemd 6618 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory User 9 is "news", can login but does not, and runs some cron jobs with fetchnews, and the leafnode daemon, serving nntp on localhost. By the timestamp I know that it is cron. This entry in "/etc/cron.d/mine": - -3,8,13,18,23,28,33,38,43,48,53,58 * * * * news /var/lib/news/bin/cronscriptparafetchnews That script contains: #!/bin/bash HORA=`date --rfc-3339=ns` echo "================> $HORA Start fetchnews session" >> /var/lib/news/fetchnews.cron.log 2>&1 /usr/sbin/fetchnews -vv >> /var/lib/news/fetchnews.cron.log 2>&1 HORA=`date --rfc-3339=ns` echo "================> $HORA End fetchnews session" >> /var/lib/news/fetchnews.cron.log 2>&1 I know, or guess, that the bus connection is created on login, but a cron job does not login. In fact, the tree does exist: Telcontar:~ # tree /run/user/9 /run/user/9 └── systemd └── private 1 directory, 1 file Telcontar:~ # But not the dbus directory. I'd tend to ignore that log entry, but it comes in the warning log, not in the messages log, so whoever designed that thought the error to be important. But I don't know what real effect it may have. The recent thread "[opensuse] What is /run/user/<user-id> directory and how to make sure it's created?" maybe related to this issue. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlTGXBkACgkQtTMYHG2NR9ULzACfardxnQMlPBF5BZTC9Qso2nv+ cAwAnj/Ras4t7OKBWavJXFyB8+/kPQ86 =OIEm -----END PGP SIGNATURE-----