On Tue, Oct 15, 2013 at 10:24:44AM -0600, Dan Ferris wrote:
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 haven't. Does the segfault introduce when you run
gdb vdsm-tool nwfilter
as root? Could you send the output of `bt full` if it does?