Re: [libvirt] [Users] vdsmd seg fault

On Fri, 2013-10-18 at 14:16 +0300, Dan Kenigsberg wrote: > On Thu, Oct 17, 2013 at 05:15:48PM -0400, Jason Brooks wrote: > > > > > > ----- Original Message ----- > > > From: "Dan Ferris" <dferris(a)prometheusresearch.com&gt; > > > To: &quot;&lt;users(a)ovirt.org&gt;&quot; <users(a)ovirt.org&gt; > > > Sent: Tuesday, October 15, 2013 9:24:44 AM > > > Subject: [Users] vdsmd seg fault > > > > > > I updated to the latest Fedora 19 on two test servers, and now vdsmd > > > will not start. > > > > > > Systedctl says this: > > > > > > dsmd.service - Virtual Desktop Server Manager > > > Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) > > > Active: failed (Result: exit-code) since Mon 2013-10-14 12:31:30 > > > EDT; 23h ago > > > Process: 1788 ExecStart=/lib/systemd/systemd-vdsmd start > > > (code=exited, status=139) > > > > > > Oct 14 12:31:30 rs0-ovirt0.rexdb.us python[1862]: DIGEST-MD5 ask_user_info() > > > Oct 14 12:31:30 rs0-ovirt0.rexdb.us python[1862]: DIGEST-MD5 client step 2 > > > Oct 14 12:31:30 rs0-ovirt0.rexdb.us python[1862]: DIGEST-MD5 ask_user_info() > > > Oct 14 12:31:30 rs0-ovirt0.rexdb.us python[1862]: DIGEST-MD5 > > > make_client_response() > > > Oct 14 12:31:30 rs0-ovirt0.rexdb.us python[1862]: DIGEST-MD5 client step 3 > > > Oct 14 12:31:30 rs0-ovirt0.rexdb.us systemd-vdsmd[1788]: > > > /lib/systemd/systemd-vdsmd: line 185: 1862 Segmentation fault > > > "$VDSM_TOOL" nwfilter > > > Oct 14 12:31:30 rs0-ovirt0.rexdb.us systemd-vdsmd[1788]: vdsm: Failed to > > > define network filters on libvirt[FAILED] > > > Oct 14 12:31:30 rs0-ovirt0.rexdb.us systemd[1]: vdsmd.service: control > > > process exited, code=exited status=139 > > > Oct 14 12:31:30 rs0-ovirt0.rexdb.us systemd[1]: Failed to start Virtual > > > Desktop Server Manager. > > > Oct 14 12:31:30 rs0-ovirt0.rexdb.us systemd[1]: Unit vdsmd.service > > > entered failed state. > > > > > > Has anyone else experienced this? > > > > I just hit this on one of my test installs. > > > > I did yum downgrade libvirt* and then vdsmd would start > > Which was the faulty libvirt? Was there anything interesting at the > /var/log/libvirtd.log? libvirt-1.0.5.6-3.fc19 -- it started fine until I rebooted. SElinux is permissive on these machines, btw. These machines are nested inside of my main oVirt install, as well. I couldn't see anything in the libvirtd.log that looked different from the libvirtd.log on a node w/ the downgraded libvirt.