Revision history [back]

After using yum -y erase drbd-heartbeat-8.4.2-2.fc18.x86_64 drbd-bash-completion-8.4.2-2.fc18.x86_64 drbd-utils-8.4.2-2.fc18.x86_64 drbd-kernel-8.4.2-2.fc18.x86_64 drbd-udev-8.4.2-2.fc18.x86_64 drbd-8.4.2-2.fc18.x86_64 drbd-pacemaker-8.4.2-2.fc18.x86_64 drbd-xen-8.4.2-2.fc18.x86_64 running systemctl reports

$ systemctl status drbd.service
drbd.service
     Loaded: error (Reason: No such file or directory)
     Active: failed (Result: timeout) since Sun 2013-06-09 12:18:16 EDT; 1h 6min ago

Running sudo systemctl daemon-reload does not help.

What can I do to tell systemd not to expect drbd.service other than reboot?

After using yum -y erase drbd-heartbeat-8.4.2-2.fc18.x86_64 drbd-bash-completion-8.4.2-2.fc18.x86_64 drbd-utils-8.4.2-2.fc18.x86_64 drbd-kernel-8.4.2-2.fc18.x86_64 drbd-udev-8.4.2-2.fc18.x86_64 drbd-8.4.2-2.fc18.x86_64 drbd-pacemaker-8.4.2-2.fc18.x86_64 drbd-xen-8.4.2-2.fc18.x86_64 running systemctl reports

$ systemctl status drbd.service
drbd.service
     Loaded: error (Reason: No such file or directory)
     Active: failed (Result: timeout) since Sun 2013-06-09 12:18:16 EDT; 1h 6min ago

Running sudo systemctl daemon-reload does not help. Update: running $ sudo systemctl daemon-reexec does not help.

What can I do to tell systemd not to expect drbd.service other than reboot?

After using yum -y erase drbd-heartbeat-8.4.2-2.fc18.x86_64 drbd-bash-completion-8.4.2-2.fc18.x86_64 drbd-utils-8.4.2-2.fc18.x86_64 drbd-kernel-8.4.2-2.fc18.x86_64 drbd-udev-8.4.2-2.fc18.x86_64 drbd-8.4.2-2.fc18.x86_64 drbd-pacemaker-8.4.2-2.fc18.x86_64 drbd-xen-8.4.2-2.fc18.x86_64 running systemctl reports

$ systemctl status drbd.service
drbd.service
     Loaded: error (Reason: No such file or directory)
     Active: failed (Result: timeout) since Sun 2013-06-09 12:18:16 EDT; 1h 6min ago

Running sudo systemctl daemon-reload does not help. Update: running $ sudo systemctl daemon-reexec does not help.

What can I do to tell systemd not to expect drbd.service other than reboot?