On Mon, Mar 30, 2020 at 09:09:56PM -0000, Simon Déziel wrote: > On 2020-03-30 4:54 p.m., Seth Arnold wrote: > > 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. > > This should let you see today's logs related to $UNIT_NAME: > > journalctl -S today -u $UNIT_NAME
Thanks Simon, that's really useful: $ journalctl -S yesterday -u libvirt* -- Logs begin at Mon 2020-02-10 21:23:01 UTC, end at Tue 2020-03-31 01:27:06 UTC. -- Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 17:58:04 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 17:58:04 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 20:44:31 millbarge dnsmasq[3054]: reading /etc/resolv.conf Mar 30 20:44:31 millbarge dnsmasq[3054]: using nameserver 127.0.0.53#53 Mar 30 20:44:55 millbarge systemd[1]: libvirtd-ro.socket: Succeeded. Mar 30 20:44:55 millbarge systemd[1]: Closed Libvirt local read-only socket. Mar 30 20:44:55 millbarge systemd[1]: Stopping Libvirt local read-only socket. Mar 30 20:44:55 millbarge systemd[1]: libvirtd-ro.socket: Socket service libvirtd.service already active, refusing. Mar 30 20:44:55 millbarge systemd[1]: Failed to listen on Libvirt local read-only socket. Mar 30 20:44:55 millbarge systemd[1]: Stopping Virtualization daemon... Mar 30 20:44:55 millbarge systemd[1]: libvirtd.service: Succeeded. Mar 30 20:44:55 millbarge systemd[1]: Stopped Virtualization daemon. Mar 30 20:44:55 millbarge systemd[1]: libvirtd-admin.socket: Succeeded. Mar 30 20:44:55 millbarge systemd[1]: Closed Libvirt admin socket. Mar 30 20:44:55 millbarge systemd[1]: Stopping Libvirt admin socket. Mar 30 20:44:55 millbarge systemd[1]: libvirtd.socket: Succeeded. Mar 30 20:44:55 millbarge systemd[1]: Closed Libvirt local socket. Mar 30 20:44:55 millbarge systemd[1]: Stopping Libvirt local socket. Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local socket. Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin socket. Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local read-only socket. Mar 30 20:44:55 millbarge systemd[1]: libvirtd.service: Found left-over process 3054 (dnsmasq) in control group while starting unit. Ignoring. Mar 30 20:44:55 millbarge systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 30 20:44:55 millbarge systemd[1]: libvirtd.service: Found left-over process 3055 (dnsmasq) in control group while starting unit. Ignoring. Mar 30 20:44:55 millbarge systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. 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 Mar 31 00:02:58 millbarge systemd[1]: Stopping Suspend/Resume Running libvirt Guests... Mar 31 00:02:58 millbarge libvirt-guests.sh[3865897]: Running guests on default URI: Mar 31 00:02:58 millbarge libvirt-guests.sh[3865910]: Running guests on Mar 31 00:02:58 millbarge libvirt-guests.sh[3865859]: R Mar 31 00:02:58 millbarge systemd[1]: libvirt-guests.service: Succeeded. Mar 31 00:02:58 millbarge systemd[1]: Stopped Suspend/Resume Running libvirt Guests. Mar 31 00:02:58 millbarge systemd[1]: Stopping Virtualization daemon... Mar 31 00:02:58 millbarge systemd[1]: libvirtd.service: Succeeded. Mar 31 00:02:58 millbarge systemd[1]: Stopped Virtualization daemon. Mar 31 00:03:00 millbarge systemd[1]: libvirtd-admin.socket: Succeeded. Mar 31 00:03:00 millbarge systemd[1]: Closed Libvirt admin socket. Mar 31 00:03:00 millbarge systemd[1]: libvirtd-ro.socket: Succeeded. Mar 31 00:03:00 millbarge systemd[1]: Closed Libvirt local read-only socket. Mar 31 00:03:00 millbarge systemd[1]: libvirtd.socket: Succeeded. Mar 31 00:03:00 millbarge systemd[1]: Closed Libvirt local socket. -- Reboot -- Mar 31 00:04:08 millbarge systemd[1]: Listening on Libvirt local socket. Mar 31 00:04:08 millbarge systemd[1]: Listening on Libvirt admin socket. Mar 31 00:04:08 millbarge systemd[1]: Listening on Libvirt local read-only socket. Mar 31 00:04:12 millbarge systemd[1]: Starting Virtualization daemon... Mar 31 00:04:12 millbarge systemd[1]: Started Virtualization daemon. Mar 31 00:04:12 millbarge systemd[1]: Starting Suspend/Resume Running libvirt Guests... Mar 31 00:04:12 millbarge systemd[1]: Finished Suspend/Resume Running libvirt Guests. Mar 31 00:04:13 millbarge dnsmasq[3011]: started, version 2.80 cachesize 150 Mar 31 00:04:13 millbarge dnsmasq[3011]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Mar 31 00:04:13 millbarge dnsmasq-dhcp[3011]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Mar 31 00:04:13 millbarge dnsmasq-dhcp[3011]: DHCP, sockets bound exclusively to interface virbr0 Mar 31 00:04:13 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:04:13 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 Mar 31 00:04:13 millbarge dnsmasq[3011]: read /etc/hosts - 7 addresses Mar 31 00:04:13 millbarge dnsmasq[3011]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Mar 31 00:04:13 millbarge dnsmasq-dhcp[3011]: read /var/lib/libvirt/dnsmasq/default.hostsfile Mar 31 00:27:57 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:27:57 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 Mar 31 00:27:57 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:27:57 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 Mar 31 00:27:57 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:27:57 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 Mar 31 00:27:57 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:27:57 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 Mar 31 00:27:57 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:27:57 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 Mar 31 00:27:57 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:27:57 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 Mar 31 00:27:57 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:27:57 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 Mar 31 00:27:57 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:27:57 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 Mar 31 00:27:57 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:27:57 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 Mar 31 00:27:57 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:27:57 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 Mar 31 00:27:57 millbarge dnsmasq[3011]: reading /etc/resolv.conf Mar 31 00:27:57 millbarge dnsmasq[3011]: using nameserver 127.0.0.53#53 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869796 Title: vague error during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1869796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
