Problem with libvirt-daemon-system package during Debian upgrade

Written by Claudio Kuenzler - 0 comments

Published on July 2nd 2021 - Listed in Linux Virtualization KVM

During an upgrade of Debian 9 (Stretch) to 10 (Buster), the following error was seen while upgrading the libvirt-daemon-system package:

root@debian ~ # apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
dh-python guile-2.0-libs libasyncns0 libbind9-140 libblas-common libboost-atomic1.67.0 libboost-filesystem1.62.0 libboost-iostreams1.62.0 libboost-random1.62.0 libboost-regex1.67.0 libboost-system1.62.0 libboost-thread1.62.0
libboost-thread1.67.0 libcaca0 libdns162 libevent-2.0-5 libflac8 libgfortran3 libhiredis0.13 libice6 libicu57 libisc160 libisccc140 libisccfg140 liblvm2app2.2 liblvm2cmd2.02 liblwres141 libogg0 libperl5.24 libpulse0
libpython3.5-minimal libpython3.5-stdlib librados2 librbd1 libsdl1.2debian libsm6 libsndfile1 libvorbis0a libvorbisenc2 libx11-xcb1 libxen-4.8 libxi6 libxtst6 linux-image-4.9.0-7-amd64 patch python-certifi python-chardet python-gi
python-idna python-ipaddr python-libvirt python-libxml2 python-pkg-resources python-requests python-six python-urllib3 python3-pyasn1 python3.5 python3.5-minimal rename sgml-base tcpd x11-common xml-core
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up libvirt-daemon-system (5.0.0-4+deb10u1) ...
virtlockd.service is a disabled or a static unit, not starting it.
Job for virtlogd-admin.socket failed.
See "systemctl status virtlogd-admin.socket" and "journalctl -xe" for details.
A dependency job for virtlogd.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript virtlogd, action "start" failed.
- virtlogd.service - Virtual machine log manager
   Loaded: loaded (/lib/systemd/system/virtlogd.service; indirect; vendor preset: enabled)
   Active: active (running) since Wed 2021-06-30 15:25:21 CEST; 1 day 14h ago
     Docs: man:virtlogd(8)
           https://libvirt.org
Main PID: 28006 (virtlogd)
    Tasks: 2 (limit: 4915)
   Memory: 1.5M
   CGroup: /system.slice/virtlogd.service
           |- 28006 /usr/sbin/virtlogd

Jul 02 06:22:16 irczsrvp05 systemd[1]: Dependency failed for Virtual machine log manager.
Jul 02 06:22:16 irczsrvp05 systemd[1]: virtlogd.service: Job virtlogd.service/start failed with result 'dependency'.
Jul 02 06:23:12 irczsrvp05 systemd[1]: Reloading Virtual machine log manager.
Jul 02 06:23:12 irczsrvp05 systemd[1]: Reloaded Virtual machine log manager.
Jul 02 06:23:15 irczsrvp05 systemd[1]: Dependency failed for Virtual machine log manager.
Jul 02 06:23:15 irczsrvp05 systemd[1]: virtlogd.service: Job virtlogd.service/start failed with result 'dependency'.
Jul 02 06:24:57 irczsrvp05 systemd[1]: Reloading Virtual machine log manager.
Jul 02 06:24:57 irczsrvp05 systemd[1]: Reloaded Virtual machine log manager.
Jul 02 06:24:59 irczsrvp05 systemd[1]: Dependency failed for Virtual machine log manager.
Jul 02 06:24:59 irczsrvp05 systemd[1]: virtlogd.service: Job virtlogd.service/start failed with result 'dependency'.
dpkg: error processing package libvirt-daemon-system (--configure):
installed libvirt-daemon-system package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
libvirt-daemon-system
E: Sub-process /usr/bin/dpkg returned an error code (1)

The output also shows that the virtlogd.service could not be restarted due to a dependency problem.

The solution is to restart not only virtlogd.service but also virtlogd.socket:

Problem with libvirt-daemon-system package during Debian upgrade

Add a comment

Comments (newest first)

Blog Tags: