[Users] vdsmd seg fault

[Dan Ferris]

Unfortunatly, I was not correct.  Not fixed. :(

VDSM died randomly yesterday.  This was the message from systemctl:

vdsmd.service - Virtual Desktop Server Manager
    Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
    Active: failed (Result: exit-code) since Fri 2013-10-25 12:06:29 
EDT; 7s ago
   Process: 20937 ExecStop=/lib/systemd/systemd-vdsmd stop (code=exited, 
status=0/SUCCESS)
   Process: 21498 ExecStart=/lib/systemd/systemd-vdsmd start 
(code=exited, status=139)
  Main PID: 5205 (code=killed, signal=TERM)
    CGroup: name=systemd:/system/vdsmd.service

Oct 25 12:06:29 rs0-ovirt0 python[21572]: DIGEST-MD5 ask_user_info()
Oct 25 12:06:29 rs0-ovirt0 python[21572]: DIGEST-MD5 client step 2
Oct 25 12:06:29 rs0-ovirt0 python[21572]: DIGEST-MD5 ask_user_info()
Oct 25 12:06:29 rs0-ovirt0 python[21572]: DIGEST-MD5 make_client_response()
Oct 25 12:06:29 rs0-ovirt0 python[21572]: DIGEST-MD5 client step 3
Oct 25 12:06:29 rs0-ovirt0 systemd-vdsmd[21498]: libvirt: Network Filter 
Driver error : Requested operation is not valid: nwfilter is in use
Oct 25 12:06:29 rs0-ovirt0 systemd-vdsmd[21498]: 
/lib/systemd/systemd-vdsmd: line 186: 21572 Segmentation fault 
"$VDSM_TOOL" nwfilter
Oct 25 12:06:29 rs0-ovirt0 systemd[1]: vdsmd.service: control process 
exited, code=exited status=139
Oct 25 12:06:29 rs0-ovirt0 systemd[1]: Failed to start Virtual Desktop 
Server Manager.
Oct 25 12:06:29 rs0-ovirt0 systemd[1]: Unit vdsmd.service entered failed 
state.



On 10/22/2013 8:41 PM, Dan Ferris wrote:
> So, just an update...
>
> I upgraded to Ovirt 3.3.0.1 today and I have the latest libvirt.
>
> I *THINK* the issue may be gone, but I will have to do a little more
> testing.
>
> Dan
>
> On 10/18/2013 11:15 AM, Dan Ferris wrote:
>> That did work.  vdsmd decided it would start again.
>>
>> Dan
>>
>> On 10/17/2013 3:15 PM, Jason Brooks wrote:
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Dan Ferris" <dferris at prometheusresearch.com>
>>>> To: "<users at ovirt.org>" <users at ovirt.org>
>>>> 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
>>>
>>> Jason
>>>
>>>>
>>>> Dan
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>