1

Several errors after upgrade (systemd issue?)

view story
linux-howto

https://bbs.archlinux.org – miky76 wrote:when I try to add any deamons to systemctl, I get always the same errors [root@artemide ~]# systemctl enable dbus Operation failed: Invalid argument [root@artemide ~]# systemctl status dbus Failed to get D-Bus connection: No connection to service manager. [root@artemide ~]# systemctl start dbus Failed to get D-Bus connection: No connection to service manager. [root@artemide ~]#can anyone can point me to the right direction?thanksIf you want to blame systemd, then you have to actually boot on it, first. falconindy https://bbs.archlinux.org/profile.php?id=30251 2012-1 (HowTos)

Danial's picture
Submitted by Danial on 12/14/2012

Stories similar to Several errors after upgrade (systemd issue?)

are dbus.service and dbus.socket running?systemctl status dbus.service systemctl status dbus.socketif yes, have you tried re-installing systemd-analyze, not only the python2 packages?

Xylankant https://bbs.archlinux.org/profile.php?id=48144

2012-09-06T22:34:26Z

[awesome] Dbus error 14 weeks 21 hours ago

Hi guys,my newly configured awesome desktop got this issue when I try to start an application using d-bus :(terminator:947): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-5AMlNl46V1: Connection refusedBut systemctl status dbus.service says dbus is active and running.I don't know what's wrong, do you have any idea ?Thanks

capta

Then look at the journal for errors... You'll need to look at messages for the PID that systemd-load-modules ran as. Messages will not show up for the service. 'systemctl status' shows you the pid, and then you can run 'journalctl -b _PID=$pid'

falconindy https://bbs.archlinux.org/profile.php?id=30251

2013-01-28T13:50:50Z

Title says it all. This is a fresh Fedora 17 system running on a Xen hypervisor.

I had very similar or maybe the same problem.My error was:localhost dbus[324]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.

Hi,after boot if i run "systemctl status lxdm" i see this error:Failed to issue method call: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.And also i have others issues:1.

Before I ran that command I ran ls -l /etc/systemd/system/display-manager.service and got the outputlrwxrwxrwx 1 root root 35 Oct 14 02:20 /etc/systemd/system/display-manager.service -> /usr/lib/systemd/system/kdm.serviceSo it looks like the symlink was already created when I ran systemctl enableI tried to create it again anyway though and it just returned "ln: failed to create symbolic li

When I upgrading my current machine from sysvinit to systemd, in order to use systemctl to enable services, I first had to reboot the system.With the new install media for October using systemd, is it possible to enable these services using systemctl during the install (ie, so I could add 'systemctl enable foo.service' to install scripts)?I do realize that I could just manually symlink,

hi,

i am trying to build a new rpm package for fedora 17, i have already created a package review

However, I cant interpret the systemd error messages.

Code: [root@fc17-64 tmp]# systemctl enable tntnet.service ln -s '/usr/lib/systemd/system/tntnet.service' '/etc/systemd/system/multi-user.target.wants/tntnet.service'

Code: [root@fc17-64 tmp]# systemctl start tntnet.service J