[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2021-02-25 Thread Bug Watch Updater
** Changed in: debhelper (Debian)
   Status: Incomplete => New

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  New

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock-ro (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-ro.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local read-
  only socket.

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libvirt-daemon 6.0.0-0ubuntu6
 

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2020-08-29 Thread Launchpad Bug Tracker
This bug was fixed in the package libvirt - 6.6.0-1ubuntu2

---
libvirt (6.6.0-1ubuntu2) groovy; urgency=medium

  * d/p/u/lp-1892826-Revert-m4-virt-xdr-rewrite-XDR-check.patch: avoid clashes
between libtripc and glibc that break libvirt-lxc (LP: #1892826)
  * d/p/ubuntu-aa/lp-1892736-apparmor-allow-libvirtd-to-call-virtiofsd.patch:
allow libvirt to control virtiofsd (LP: #1892736)

libvirt (6.6.0-1ubuntu1) groovy; urgency=medium

  * Merge with Debian 6.6.0-1 from experimental
Among many other new features and fixes this includes fixes for:
(LP: #1874647) - Stale libvirt cache leads to VM startup failures
(LP: #1869796) - bad ordering and dependent restarts of services/sockets
Remaining changes:
- d/p/ubuntu-aa/lp-1847361-load-versioned-module.patch: allow loading
  versioned modules after qemu package upgrades (LP 1847361)
- libvirt-uri.sh: Automatically switch default libvirt URI for users
  via user profile (xen URI on dom0, qemu:///system otherwise)
- Disable libssh2 support (universe dependency)
- Disable firewalld support (universe dependency)
- Set qemu-group to kvm (for compat with older ubuntu)
- Additional apport package-hook
- Autostart default bridged network (As upstream does, but not Debian).
  In addition to just enabling it our solution provides:
  + do not autostart if subnet is already taken (e.g. in guests).
  + iterate some alternative subnets before giving up
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
  the group based access to libvirt functions as it was used in Ubuntu
  for quite long.
  + d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
  + d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
group.
- ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
- Update README.Debian with Ubuntu changes
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- fix autopkgtests
  + d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
vmlinuz available and accessible (Debian bug 848314)
  + d/t/control: fix smoke-qemu-session by ensuring the service will run
installing libvirt-daemon-system
  + d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as
long as the following undefine succeeds
  + d/t/smoke-lxc: use systemd instead of sysV to restart the service
- dnsmasq related enhancements
  + run dnsmasq as libvirt-dnsmasq (LP: 1743718)
  + d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
  + d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group
on purge
  + d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user
libvirt-dnsmasq and adapt the self tests to expect that config
  + d/libvirt-daemon-system.postinst: fix old libvirt-dnsmasq users group
  + Add dnsmasq configuration to work with system wide dnsmasq-base
- debian/rules: disable the netcf backend. (LP: 1764314)
- debian/patches/ubuntu/ovmf_paths.patch: adjust paths to secboot.fd UEFI
  Secure Boot enabled variants of the OVMF firmware and variable store for
  the paths where we ship these files in Ubuntu.
- d/p/ubuntu/set-default-machine-to-ubuntu.patch: to select default
  machine type correctly with newer qemu/libvirt
- d/control: add libzfslinux-dev to build-deps
- d/control: drop libvirt-lxc, vbox and xen drivers to suggest
- d/p/ubuntu/lp-1861125-ubuntu-models: recognize Ubuntu models for
  (LP 1861125) fixups
- Apparmor Delta that is Ubuntu specific or yet to be upstreamed
  split into logical pieces. File names in debian/patches/ubuntu-aa/:
  + 0003-apparmor-libvirt-qemu-Allow-read-access-to-overcommi.patch:
apparmor, libvirt-qemu: Allow read access to overcommit_memory
  + 0007-apparmor-libvirt-qemu-Allow-owner-read-access-to-PRO.patch:
apparmor, libvirt-qemu: Allow owner read access to @{PROC}/*/auxv
  + 0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
  + 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor,
libvirt-qemu: Add 9p support
  + 0030-virt-aa-helper-Complete-9p-support.patch: virt-aa-helper:
add l to 9p file options.
  + 0031-virt-aa-helper-Ask-for-no-deny-rule-for-readonly-dis.patch:
virt-aa-helper: Ask for no deny rule for readonly disk (renamed and
reworded, was virt-aa-helper-no-explicity-deny-for-basefiles.patch)
  + 0032-apparmor-libvirt-qemu-Allow-reading-charm-specific-c.patch:
apparmor, libvirt-qemu: Allow reading charm-specific ceph config
  + 0033-UBUNTU-only-apparmor-for-kvm.powerpc-LP-1680384.patch: allow
commands executed by ubuntu only kvm wrapper on 

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2020-08-19 Thread Christian Ehrhardt 
** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/389531

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Incomplete

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock-ro (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-ro.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local read-
  only socket.

  
  Thanks

  ProblemType: Bug
  DistroRelease: 

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2020-08-07 Thread Christian Ehrhardt 
The new code now handles sockets and services differently from libvirt 
packaging.
There might also have been changes to the various debhelpers, but the TL;DR is 
that I no more see this issue with libvirt 6.6.

I'll mark the bug as closed with that, but please report back if you
happen to find a combination that triggers it again.

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Incomplete

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock-ro (Stream)
Tasks: 0 

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2020-04-16 Thread Launchpad Bug Tracker
** Merge proposal unlinked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/382309

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Incomplete

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock-ro (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-ro.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local read-
  only socket.

  
  Thanks

  ProblemType: Bug
  DistroRelease: 

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2020-04-16 Thread Christian Ehrhardt 
I have tried to get this into 20.04 but it really does not behave the way it 
should.
- sockets are still restarted (more than ever)
- libvirt-guest is restarted (killing guests on upgrades)
...

This needs some more time and isn't feasible for a late minute change in 20.04.
I'm considering it as if it would be an SRU already, and for that the potential 
(and known) breakage clearly kills the little gain of that warning message 
being removed.

I'll make this part of the early (as it will need time and many tests to
do it right) 20.10 virt stack tasks.

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Incomplete

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded 

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2020-04-15 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/382309

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Incomplete

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock-ro (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-ro.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local read-
  only socket.

  
  Thanks

  ProblemType: Bug
  DistroRelease: 

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2020-04-15 Thread Christian Ehrhardt 
** Changed in: libvirt (Ubuntu)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Incomplete

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock-ro (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-ro.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local read-
  only socket.

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: 

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2020-04-15 Thread Christian Ehrhardt 
This will be fixed on the next merge, in the debhelper discussion we
settled on --no-also which is a hidden dh_systemd option.

OTOH the undocumented option even exists in Bionic, so for quite a while.
Maybe we should just add it to focal which would stop printing that warning and 
maybe solve more critical issues that we just haven't spotted yet.

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Incomplete

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock-ro (Stream)
 

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2020-04-03 Thread Balint Reczey
@paelzer I've left a comment in the Debian bug, too, and I agree that
the best fix would be in systemd, while I think for Focal a workaround
will be needed (maybe the one I proposed there, maybe one in libvirt).

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Incomplete

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● 

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2020-04-02 Thread Bug Watch Updater
** Changed in: debhelper (Debian)
   Status: New => Incomplete

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in debhelper package in Debian:
  Incomplete

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock-ro (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-ro.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local read-
  only socket.

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libvirt-daemon 6.0.0-0ubuntu6
  

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2020-04-01 Thread Christian Ehrhardt 
If you follow the Debian discussion it seems this tends to go the "please fix 
in systemd" way.
Therefore I'm adding a systemd task

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in debhelper package in Debian:
  New

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock-ro (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-ro.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on