Comment 5 for bug 1869796

On Tue, Mar 31, 2020 at 02:15:11PM -0000, Christian Ehrhardt  wrote:
> Mar 30 20:44:55 millbarge systemd[1]: libvirtd.service: Found left-over process 3054 (dnsmasq) in control group while starting unit. Ignoring.
> => That is ok, some things are expected to live over to the new restarted service

Nice to know.

> 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.
>
> That might be related to your issue, but I'm not entirely sure.

I'd also hope this is just a warning, but.. you never know.

>
> Unless you restarted plenty of services already could you run the following pelase:
> $ systemctl status $(for f in $(dpkg -L libvirt-daemon-system | grep systemd | grep -e socket -e service); do basename $f; done | xargs)
>
> I can then compare that with new-installs and upgrades that I can retry.

Unfortunately I've rebooted several times since then. Very handy little
one-liner for getting "package" status, thanks.

> Also was your upgrade from
> - former focal version

My update was from a former focal version.

Thanks