Ubuntu
libvirt package

  1. Bug #1738834
  2. Comment #10

Comment 10 for bug 1738834

Revision history for this message
Janåke Rönnblom (jan-ake) wrote :

This happens during the unattended-upgrade at night. The libvirt-bin is then not fully upgraded/installed.

Jul 18 06:12:07 x systemd[1]: Reloading Virtual machine log manager.
Jul 18 06:12:07 x systemd[1]: Reloaded Virtual machine log manager.
Jul 18 06:12:09 x systemd[1]: Dependency failed for Virtual machine log manager.
Jul 18 06:12:09 x systemd[1]: virtlogd.service: Job virtlogd.service/start failed with result 'dependency'.

It seems to me that the virtlogd is reloaded however seconds later the virtlogd is tried to be started. Could systemd when installing libvirt-bin try to start virtlogd even though its already running? And what dependency failed?

The only way to fix this is to stop virtlogd and virtlockd. Then libvirt-bin can be upgraded using apt-get