This is in Debian since April, that would have shown up there.
Why would it only hit us thou?
I was upgrading Debian from 3.0 (stable) to 4.6 (unstable)
PRE
root@debian-stretch:~# systemctl status virtlogd.service virtlogd.socket
virtlogd-admin.socket virtlockd.service virtlockd.socket
virtlockd-admin.socket --no-pager --lines 2
● virtlogd.service - Virtual machine log manager
Loaded: loaded (/lib/systemd/system/virtlogd.service; indirect; vendor
preset: enabled)
Active: active (running) since Thu 2018-08-09 09:28:33 UTC; 7s ago
Docs: man:virtlogd(8)
http://libvirt.org
Main PID: 7080 (virtlogd)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/virtlogd.service
└─7080 /usr/sbin/virtlogd
Aug 09 09:28:35 debian-stretch systemd[1]: virtlogd.service: Failed to reset
devices.list: Operation not permitted
Aug 09 09:28:37 debian-stretch systemd[1]: virtlogd.service: Failed to reset
devices.list: Operation not permitted
● virtlogd.socket - Virtual machine log manager socket
Loaded: loaded (/lib/systemd/system/virtlogd.socket; enabled; vendor preset:
enabled)
Active: active (running) since Thu 2018-08-09 09:28:33 UTC; 7s ago
Listen: /var/run/libvirt/virtlogd-sock (Stream)
Aug 09 09:28:33 debian-stretch systemd[1]: Listening on Virtual machine log
manager socket.
Unit virtlogd-admin.socket could not be found.
● virtlockd.service - Virtual machine lock manager
Loaded: loaded (/lib/systemd/system/virtlockd.service; indirect; vendor
preset: enabled)
Active: inactive (dead)
Docs: man:virtlockd(8)
http://libvirt.org
● virtlockd.socket - Virtual machine lock manager socket
Loaded: loaded (/lib/systemd/system/virtlockd.socket; enabled; vendor
preset: enabled)
Active: active (listening) since Thu 2018-08-09 09:28:34 UTC; 7s ago
Listen: /var/run/libvirt/virtlockd-sock (Stream)
Aug 09 09:28:34 debian-stretch systemd[1]: Listening on Virtual machine lock
manager socket.
Unit virtlockd-admin.socket could not be found.
Upgrade just libvirt and dependencies:
This looked similar but not exactly the same, it turned out to be affected by
the jannson issue that I proposed a fix to Debian already.
Doing it all over again stretch to 4.5 (testing) which should expose the same
issue but not the swarm of red libjansson4 herrings.
[...]
Upgrade just libvirt and dependencies - stretch to testing.
# apt install libvirt-daemon-system
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libboost-iostreams1.62.0 libboost-random1.62.0 libboost-system1.62.0
libboost-thread1.62.0 librados2 librbd1
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
ca-certificates libcap-ng0 libcom-err2 libcomerr2 libcurl3-gnutls libidn2-0
libnghttp2-14 libpsl5 librtmp1 libunistring2 libvirt-clients
libvirt-daemon libvirt0 openssl publicsuffix
Suggested packages:
libvirt-daemon-driver-storage-gluster libvirt-daemon-driver-storage-rbd
libvirt-daemon-driver-storage-sheepdog
libvirt-daemon-driver-storage-zfs numad apparmor auditd nfs-common open-iscsi
pm-utils radvd systemtap zfsutils
The following NEW packages will be installed:
ca-certificates libcom-err2 libcurl3-gnutls libidn2-0 libnghttp2-14 libpsl5
librtmp1 libunistring2 openssl publicsuffix
The following packages will be upgraded:
libcap-ng0 libcomerr2 libvirt-clients libvirt-daemon libvirt-daemon-system
libvirt0
6 upgraded, 10 newly installed, 0 to remove and 248 not upgraded.
Need to get 9437 kB of archives.
After this operation, 5147 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
[...]
Setting up libvirt-daemon-system (4.5.0-1) ...
Installing new version of config file /etc/apparmor.d/abstractions/libvirt-qemu
...
Installing new version of config file /etc/apparmor.d/libvirt/TEMPLATE.lxc ...
Installing new version of config file /etc/apparmor.d/libvirt/TEMPLATE.qemu ...
Installing new version of config file
/etc/apparmor.d/usr.lib.libvirt.virt-aa-helper ...
Installing new version of config file /etc/apparmor.d/usr.sbin.libvirtd ...
Installing new version of config file /etc/default/libvirt-guests ...
Installing new version of config file /etc/init.d/libvirt-guests ...
Installing new version of config file /etc/libvirt/libvirtd.conf ...
Installing new version of config file /etc/libvirt/libxl.conf ...
Installing new version of config file /etc/libvirt/qemu.conf ...
Installing new version of config file /etc/libvirt/virtlockd.conf ...
Installing new version of config file /etc/libvirt/virtlogd.conf ...
Installing new version of config file /etc/logrotate.d/libvirtd.libxl ...
Installing new version of config file /etc/logrotate.d/libvirtd.lxc ...
Installing new version of config file /etc/logrotate.d/libvirtd.qemu ...
Installing new version of config file /etc/logrotate.d/libvirtd.uml ...
Installing new version of config file /etc/sasl2/libvirt.conf ...
Created symlink /etc/systemd/system/sockets.target.wants/virtlockd-admin.socket
→ /lib/systemd/system/virtlockd-admin.socket.
Created symlink /etc/systemd/system/sockets.target.wants/virtlogd-admin.socket
→ /lib/systemd/system/virtlogd-admin.socket.
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.
virtlogd-admin.socket couldn't start.
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 Thu 2018-08-09 09:35:36 UTC; 50s ago
Docs: man:virtlogd(8)
https://libvirt.org
Main PID: 6774 (virtlogd)
CGroup: /system.slice/virtlogd.service
└─6774 /usr/sbin/virtlogd
Aug 09 09:35:38 debian-stretch systemd[1]: virtlogd.service: Failed to reset
devices.list: Operation not permitted
Aug 09 09:35:41 debian-stretch systemd[1]: virtlogd.service: Failed to reset
devices.list: Operation not permitted
Aug 09 09:36:21 debian-stretch systemd[1]: virtlogd.service: Failed to reset
devices.list: Operation not permitted
Aug 09 09:36:25 debian-stretch systemd[1]: virtlogd.service: Failed to reset
devices.list: Operation not permitted
Aug 09 09:36:25 debian-stretch systemd[1]: Reloading Virtual machine log
manager.
Aug 09 09:36:25 debian-stretch systemd[1]: Reloaded Virtual machine log manager.
Aug 09 09:36:26 debian-stretch systemd[1]: virtlogd.service: Failed to reset
devices.list: Operation not permitted
Aug 09 09:36:26 debian-stretch systemd[1]: virtlogd.service: Failed to reset
devices.list: Operation not permitted
Aug 09 09:36:27 debian-stretch systemd[1]: Dependency failed for Virtual
machine log manager.
Aug 09 09:36:27 debian-stretch systemd[1]: virtlogd.service: Job
virtlogd.service/start failed with result 'dependency'.
dpkg: error processing package libvirt-daemon-system (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for ca-certificates (20170717) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for systemd (232-25+deb9u4) ...
Errors were encountered while processing:
libvirt-daemon-system
E: Sub-process /usr/bin/dpkg returned an error code (1)
# systemctl status virtlogd.service virtlogd.socket virtlogd-admin.socket
virtlockd.service virtlockd.socket virtlockd-admin.socket --no-pager --lines 2
● virtlogd.service - Virtual machine log manager
Loaded: loaded (/lib/systemd/system/virtlogd.service; indirect; vendor
preset: enabled)
Active: active (running) since Thu 2018-08-09 09:35:36 UTC; 1min 11s ago
Docs: man:virtlogd(8)
https://libvirt.org
Main PID: 6774 (virtlogd)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/virtlogd.service
└─6774 /usr/sbin/virtlogd
Aug 09 09:36:27 debian-stretch systemd[1]: virtlogd.service: Job
virtlogd.service/start failed with result 'dependency'.
Aug 09 09:36:31 debian-stretch systemd[1]: virtlogd.service: Failed to reset
devices.list: Operation not permitted
● virtlogd.socket - Virtual machine log manager socket
Loaded: loaded (/lib/systemd/system/virtlogd.socket; enabled; vendor preset:
enabled)
Active: active (running) since Thu 2018-08-09 09:35:36 UTC; 1min 11s ago
Listen: /var/run/libvirt/virtlogd-sock (Stream)
Aug 09 09:35:36 debian-stretch systemd[1]: Listening on Virtual machine
log manager socket.
● virtlogd-admin.socket - Virtual machine log manager socket
Loaded: loaded (/lib/systemd/system/virtlogd-admin.socket; enabled; vendor
preset: enabled)
Active: inactive (dead)
Listen: /var/run/libvirt/virtlogd-admin-sock (Stream)
Aug 09 09:36:27 debian-stretch systemd[1]: virtlogd-admin.socket: Socket
service virtlogd.service already active, refusing.
Aug 09 09:36:27 debian-stretch systemd[1]: Failed to listen on Virtual machine
log manager socket.
● virtlockd.service - Virtual machine lock manager
Loaded: loaded (/lib/systemd/system/virtlockd.service; indirect; vendor
preset: enabled)
Active: inactive (dead)
Docs: man:virtlockd(8)
https://libvirt.org
● virtlockd.socket - Virtual machine lock manager socket
Loaded: loaded (/lib/systemd/system/virtlockd.socket; enabled; vendor
preset: enabled)
Active: active (listening) since Thu 2018-08-09 09:36:26 UTC; 21s ago
Listen: /var/run/libvirt/virtlockd-sock (Stream)
Aug 09 09:36:26 debian-stretch systemd[1]: Stopping Virtual machine lock
manager socket.
Aug 09 09:36:26 debian-stretch systemd[1]: Listening on Virtual machine lock
manager socket.
● virtlockd-admin.socket - Virtual machine lock manager admin socket
Loaded: loaded (/lib/systemd/system/virtlockd-admin.socket; enabled; vendor
preset: enabled)
Active: active (listening) since Thu 2018-08-09 09:36:26 UTC; 21s ago
Listen: /var/run/libvirt/virtlockd-admin-sock (Stream)
Aug 09 09:36:26 debian-stretch systemd[1]: Listening on Virtual machine
lock manager admin socket.
Ok, so I'm not just stupid - Debian is affected the same way.
And that probably since libvirt 4.2 - 4 months ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786179
Title:
double virtlogd sockets with services running can trigger issues on
upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786179/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
