package libvirt-bin 1.2.8-0ubuntu11.2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

[johan lindquist]

automatic upgrading using aptitude

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: libvirt-bin 1.2.8-0ubuntu11.2
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Thu Jan 15 11:09:00 2015
DuplicateSignature: package:libvirt-bin:1.2.8-0ubuntu11.2:subprocess installed post-installation script was killed by signal (Terminated)
ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated)
KernLog:

ProcCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-29-generic root=UUID=d6330c49-3639-4cdd-b69d-89a76ae2a307 ro splash quiet nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
SourcePackage: libvirt
Title: package libvirt-bin 1.2.8-0ubuntu11.2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
UpgradeStatus: Upgraded to utopic on 2014-12-08 (38 days ago)
modified.conffile..etc.apparmor.d.local.usr.sbin.libvirtd: [modified]
mtime.conffile..etc.apparmor.d.local.usr.sbin.libvirtd: 2013-06-05T15:41:35.355973

[Serge Hallyn (serge-hallyn)]

Thanks for reporting this bug. Could you please show the contents of /var/log/libvirt/libvirtd.log and look in /var/log/syslog for any meaningful messages?

What does 'sudo status libvirt-bin' show at the moment? If it does not show 'Running', then what does 'sudo start libvirt-bin' show, and does 'sudo /usr/sbin/libvirtd -v' show anything helpful?

[johan lindquist (smilfinken)]

-----8<-----
johan@jaguar:/$ sudo status libvirt-bin
libvirt-bin start/running, process 2646
----->8-----

The last entry in libvirtd.log is from over a month ago:
-----8<-----
2014-12-11 13:53:10.886+0000: 2732: info : libvirt version: 1.2.8, package: 1.2.8-0ubuntu11.1
2014-12-11 13:53:10.886+0000: 2732: error : libxlConnectOpen:470 : internal error: libxenlight state driver is not active
2014-12-11 13:53:11.053+0000: 2726: error : virNetSocketReadWire:1527 : End of file while reading data: Input/output error
2014-12-11 13:53:11.087+0000: 2732: error : libxlConnectOpen:470 : internal error: libxenlight state driver is not active
2014-12-11 13:53:11.088+0000: 2726: error : virNetSocketReadWire:1527 : End of file while reading data: Input/output error
2014-12-11 13:53:11.122+0000: 2732: error : libxlConnectOpen:470 : internal error: libxenlight state driver is not active
2014-12-11 13:53:11.123+0000: 2726: error : virNetSocketReadWire:1527 : End of file while reading data: Input/output error
----->8-----

libvirtd in itself seems to start up properly, however.

I also just noticed that after the last reboot (libvirtd still won't configure properly) I have no $HOME since nfs fails to mount due to rpc.statd not running. /var/log/syslog is empty, so it seems I might have some other problems to deal with as well. Not sure how relevant the bug report is considering these things.

[johan lindquist (smilfinken)]

Followup on last comment, I reinstalled syslog-ng (removing the rsyslog package that I don't know why it was still on there) and now all is well. No libvirtd errors, system starts up (and logfiles get written to) like nothing out of the ordinary ever happened. Suggest ignoring this report and closing the bug.

[Serge Hallyn (serge-hallyn)]

Thanks for the update. I will mark this 'invalid' meaning "cannot be reproduced now".