http://bugzilla.opensuse.org/show_bug.cgi?id=987668
http://bugzilla.opensuse.org/show_bug.cgi?id=987668#c2
--- Comment #2 from Eric Bischoff
After an upgrade of Leap 12.1,
I guess you mean 42.1.
Yes, sorry.
And what do you mean by "an upgrade"?
zypper ref && zypper up
Did you just update some packages from your configured repos? (BTW, the OBS Virtualization repo must be one of them to get libvirt 2.0.0.)
Yes, among the repos: Virtualization (openSUSE_Leap_42.1)
2016-07-05T14:44:15.426555+02:00 tegan libvirtd[15535]: Failed to notify systemd
Heh, that's not very helpful :).
Yes, tell the guys who do such messages :-)
Starting libvirtd manually with 'export LIBVIRT_DEBUG=1; /usr/sbin/libvirtd -l' might give something useful.
It just works and the output contains: 2016-07-05 17:55:04.617+0000: 32720: debug : virSystemdNotifyStartup:504 : Skipping systemd notify, not requested I understand the problem is not in libvirtd, but in its interaction with systemd. It fails notifying systemd that everything went fine. When running the daemon manually, it just tells us it does not try to notify systemd.
Problem is fairly similar, at least in its symptoms, to:
Symptoms do sound the same, but the underlying problem must be different. In the RH bug, libvirtd would not start with systemd > v229. libvirt.git commit c0bc1723, which is included in libvirt 2.0.0, fixed that issue.
Yes.
$ rpm -q libvirt libvirt-2.0.0-590.1.x86_64
$ rpm -q systemd systemd-210-95.1.x86_64
Here we have a "fixed" libvirt with older systemd. Does systemd v210 support sending a ready message to $NOTIFY_SOCKET?
Probably yes, since man 3 sd_notify on that machine mentions NOTIFY_SOCKET environment variable.
Is the NOTIFY_SOCKET env variable set correctly on the system?
# env | grep NOTIFY => no answer But a manual run of systemd-notify works. -- You are receiving this mail because: You are on the CC list for the bug.