Re: [Users] vdsmd seg fault

On 10/16/2013 8:55 AM, Dan Kenigsberg wrote: >On Wed, Oct 16, 2013 at 08:33:10AM -0600, Dan Ferris wrote: >> >> >>On 10/16/2013 12:27 AM, Dan Kenigsberg wrote: >>>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? >>> >> >>gdb is complaining that vdsm-tool is a python script and not in elf format. > >doh me. `gdb python`, followed by `run /usr/bin/vdsm-tool nwfilter` is >what should be done. > >> >>However, running vdsm-tool nwfilter runs and has a return code of 0. > >But when it's called via systemd, the segfault still reproduces? > >Dan. > Yeah, that's correct. It segfaults when it runs from systemd. I just ran it from gdb: GNU gdb (GDB) Fedora 7.6.1-41.fc19 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/python2.7...Reading symbols from /usr/bin/python2.7...(no debugging symbols found)...done. (no debugging symbols found)...done. Missing separate debuginfos, use: debuginfo-install python-2.7.5-8.fc19.x86_64 (gdb) run /usr/bin/vdsm-tool nwfilter Starting program: /usr/bin/python /usr/bin/vdsm-tool nwfilter [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffe4bb8700 (LWP 8808)] [Thread 0x7ffff7fec740 (LWP 8804) exited] [Inferior 1 (process 8804) exited normally] (gdb) bt full No stack. Looks like it's happy. Is there any other info you want about my system? I'm even willing to let somebody log in and poke around.