Hello Moby, There is a bug open that is the explanation for this behaviour. You can read the details here: https://bugzilla.opensuse.org/show_bug.cgi?id=918226 For the moment you can go back to the previous version of systemd (and add a lock so it doesn't upgrade until the fix is out) with this command: zypper -n in --oldpackage systemd-32bit-208-23.3.x86_64 systemd-208-23.3.x86_64 systemd-sysvinit-208-23.3.x86_64 && zypper al systemd-32bit systemd systemd-sysvinit Or you can apply a proposed patch: zypper ar -G bsc918226/standard">http://download.opensuse.org/repositories/home:/tsaupe:/branches:/openSUSE:/... systemd-patch zypper dup --repo systemd-patch Note: beware that this will yank out rsyslog if you happen to use it. -Michael On 02/18, Moby wrote:
Date: Wed, 18 Feb 2015 14:16:13 -0600 From: Moby <moby@mobsternet.com> To: opensuse@opensuse.org Subject: [opensuse] oss 13.1 dbus errors
I have an openSuse 13.1 system that uses systemd. The system has been running fine but after doing a zypper ref/up yesterday (against standard update repos), I have been seeing problems. After bootup, the machine runs fine for about 2 to 2.5 hours. After that, anytime I do a systemctl status <service>, I get following errors logged:
Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused
I get same errors if I try to start or stop a service. I have tried various things, such as attempting to restart the dbus service, to no avail. This machine has cron jobs that check service status every so often, and the checks all start failing once this condition is encountered. Is anyone else seeing the same thing?
Thanks in advance for any help.
--Moby
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org