There is an issue, although it is not directly related to the title of
this thread.

It used to be possible to install libvirt 1.3.3 over 1.2.16 on Ubuntu 15.10 
***without any issue.***
Now, on Ubuntu 16.10, trying to install libvirt 1.3.3 from the ***same 
sources*** triggers the error already depicted above:
systemctl status libvirt-bin
● libvirt-bin.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Thu 2016-04-28 19:10:19 
CEST; 1min 3s ago
     Docs: man:libvirtd(8)
           http://libvirt.org
  Process: 11398 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, 
status=1/FAILURE)
 Main PID: 11398 (code=exited, status=1/FAILURE)

Apr 28 19:10:19 samsung-ubuntu systemd[1]: Failed to start Virtualization 
daemon.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: libvirt-bin.service: Unit entered 
failed state.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: libvirt-bin.service: Failed with 
result 'exit-code'.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: libvirt-bin.service: Service 
hold-off time over, scheduling restart.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: Stopped Virtualization daemon.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: libvirt-bin.service: Start request 
repeated too quickly.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: Failed to start Virtualization 
daemon.

What has changed?
I finally figured it out.
On Ubuntu 15.10, we had the shared libraries in /usr/lib as expected:
dpkg --contents libvirt0_1.2.16-2ubuntu11_amd64.deb | grep so
-rw-r--r-- root/root   3607776 2015-09-29 03:02 ./usr/lib/libvirt.so.0.1002.16
-rw-r--r-- root/root     10168 2015-09-29 03:02 
./usr/lib/libvirt-lxc.so.0.1002.16
-rw-r--r-- root/root     14264 2015-09-29 03:02 
./usr/lib/libvirt-qemu.so.0.1002.16
lrwxrwxrwx root/root         0 2015-09-29 03:02 ./usr/lib/libvirt-qemu.so.0 -> 
libvirt-qemu.so.0.1002.16
lrwxrwxrwx root/root         0 2015-09-29 03:02 ./usr/lib/libvirt.so.0 -> 
libvirt.so.0.1002.16
lrwxrwxrwx root/root         0 2015-09-29 03:02 ./usr/lib/libvirt-lxc.so.0 -> 
libvirt-lxc.so.0.1002.16

Since libvirt 1.3.3 installs its libraries over the previous ones in the same 
folder, everything worked fine:
dpkg --contents libvirt_1.3.3-14_amd64.deb | grep so
...
-rwxr-xr-x root/root   3718272 2016-04-28 19:09 ./usr/lib/libvirt.so.0.1003.3
-rwxr-xr-x root/root     34952 2016-04-28 19:09 
./usr/lib/libvirt-admin.so.0.1003.3
-rwxr-xr-x root/root     14272 2016-04-28 19:09 
./usr/lib/libvirt-qemu.so.0.1003.3
-rwxr-xr-x root/root     14272 2016-04-28 19:09 
./usr/lib/libvirt-lxc.so.0.1003.3
-rwxr-xr-x root/root    264496 2016-04-28 19:09 ./usr/lib/libnss_libvirt.so.2
lrwxrwxrwx root/root         0 2016-04-28 19:09 ./usr/lib/libvirt.so -> 
libvirt.so.0.1003.3
lrwxrwxrwx root/root         0 2016-04-28 19:09 ./usr/lib/libvirt-qemu.so.0 -> 
libvirt-qemu.so.0.1003.3
lrwxrwxrwx root/root         0 2016-04-28 19:09 ./usr/lib/libvirt-admin.so.0 -> 
libvirt-admin.so.0.1003.3
lrwxrwxrwx root/root         0 2016-04-28 19:09 ./usr/lib/libvirt-lxc.so.0 -> 
libvirt-lxc.so.0.1003.3
lrwxrwxrwx root/root         0 2016-04-28 19:09 ./usr/lib/libvirt.so.0 -> 
libvirt.so.0.1003.3
lrwxrwxrwx root/root         0 2016-04-28 19:09 ./usr/lib/libvirt-admin.so -> 
libvirt-admin.so.0.1003.3
lrwxrwxrwx root/root         0 2016-04-28 19:09 ./usr/lib/libvirt-qemu.so -> 
libvirt-qemu.so.0.1003.3
lrwxrwxrwx root/root         0 2016-04-28 19:09 ./usr/lib/libvirt-lxc.so -> 
libvirt-lxc.so.0.1003.3

Alas! Someone in Canonical decided to change that and now the libraries have 
moved to a different folder:
dpkg --contents libvirt0_1.3.1-1ubuntu10_amd64.deb | grep so
-rw-r--r-- root/root     10168 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-lxc.so.0.1003.1
-rw-r--r-- root/root     14264 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-qemu.so.0.1003.1
-rw-r--r-- root/root     30680 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-admin.so.0.1003.1
-rw-r--r-- root/root   3689792 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt.so.0.1003.1
lrwxrwxrwx root/root         0 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-admin.so.0 -> libvirt-admin.so.0.1003.1
lrwxrwxrwx root/root         0 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-qemu.so.0 -> libvirt-qemu.so.0.1003.1
lrwxrwxrwx root/root         0 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt.so.0 -> libvirt.so.0.1003.1
lrwxrwxrwx root/root         0 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-lxc.so.0 -> libvirt-lxc.so.0.1003.1

That explains the confusion:
Apr 28 19:18:45 samsung-ubuntu systemd[1]: Stopped Virtualization daemon.
Apr 28 19:18:45 samsung-ubuntu systemd[1]: Starting Virtualization daemon...
Apr 28 19:18:45 samsung-ubuntu libvirtd[12918]: /usr/sbin/libvirtd: 
/usr/lib/x86_64-linux-gnu/libvirt-admin.so.0: version 
`LIBVIRT_ADMIN_PRIVATE_1.3.3' not found (required by /usr/sbin/libvirtd)
Apr 28 19:18:45 samsung-ubuntu libvirtd[12918]: /usr/sbin/libvirtd: 
/usr/lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_1.3.3' not found 
(required by /usr/sbin/libvirtd)
Apr 28 19:18:45 samsung-ubuntu libvirtd[12918]: /usr/sbin/libvirtd: 
/usr/lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_PRIVATE_1.3.3' not 
found (required by /usr/sbin/libvirtd)
Apr 28 19:18:45 samsung-ubuntu systemd[1]: libvirt-bin.service: Main process 
exited, code=exited, status=1/FAILURE
Apr 28 19:18:45 samsung-ubuntu systemd[1]: Failed to start Virtualization 
daemon.
Apr 28 19:18:45 samsung-ubuntu systemd[1]: libvirt-bin.service: Unit entered 
failed state.
Apr 28 19:18:45 samsung-ubuntu systemd[1]: libvirt-bin.service: Failed with 
result 'exit-code'.
Apr 28 19:18:45 samsung-ubuntu systemd[1]: libvirt-bin.service: Service 
hold-off time over, scheduling restart.
Apr 28 19:18:45 samsung-ubuntu systemd[1]: Stopped Virtualization daemon.
Apr 28 19:18:45 samsung-ubuntu systemd[1]: libvirt-bin.service: Start request 
repeated too quickly.
Apr 28 19:18:45 samsung-ubuntu systemd[1]: Failed to start Virtualization 
daemon.

As a conclusion, my humble advice is to move all the libraries back to 
/usr/lib... don't you agree?
BTW,  the "NotifyAccess=all" has no involvement in this issue as far as I can 
experience.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1574566

Title:
  package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in libvirt package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  upgrade 15.10 -> 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libvirt-bin 1.3.1-1ubuntu10
  ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon Apr 25 12:44:51 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-06 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: libvirt
  Title: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (0 days ago)
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2016-04-14T14:20:45.067249

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1574566/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to