[ovs-discuss] Core dumps generated when running ovs tests in parallel

[Numan Siddique]

Hi,

On my Fedora 29 when ever I run all the ovs tests with "-j5", I see few
core dumps generated for ovsdb-server and python2.

Here's the back trace
************
[root at nusiddiq ovsdb]# gdb ./ovsdb-server
/opt/core_dumps/core.ovsdb-server.24604
GNU gdb (GDB) Fedora 8.2-6.fc29
...
...
Core was generated by `ovsdb-server --monitor --pidfile --no-db'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f813cdfe3e8 in poll () from /lib64/libc.so.6
Missing separate debuginfos, use: dnf debuginfo-install
glibc-2.28-26.fc29.x86_64 libatomic-8.3.1-2.fc29.x86_64
libcap-ng-0.7.9-5.fc29.x86_64 libevent-2.1.8-3.fc29.x86_64
openssl-libs-1.1.1b-2.fc29.x86_64 python3-libs-3.7.2-4.fc29.x86_64
unbound-libs-1.8.3-2.fc29.x86_64 zlib-1.2.11-14.fc29.x86_64
(gdb) bt
#0  0x00007f813cdfe3e8 in poll () from /lib64/libc.so.6
#1  0x00000000004453c4 in time_poll (pollfds=pollfds at entry=0xfbb320,
n_pollfds=2, handles=handles at entry=0x0, timeout_when=24471727,
elapsed=elapsed at entry=0x7fff612d09ac) at ../lib/timeval.c:326
#2  0x000000000043b1c4 in poll_block () at ../include/openvswitch/hmap.h:232
#3  0x0000000000406dd7 in main_loop (is_backup=0x7fff612d0a5e,
exiting=0x7fff612d0a5f, run_process=0x0, remotes=0x7fff612d0ab0,
unixctl=0xfb1420, all_dbs=0x7fff612d0af0, jsonrpc=0xf7eec0,
    config=0x7fff612d0b10) at ../ovsdb/ovsdb-server.c:280
#4  main (argc=<optimized out>, argv=<optimized out>) at
../ovsdb/ovsdb-server.c:460


[root at nusiddiq ovsdb]# gdb /usr/bin/python2
/opt/core_dumps/core.python2.26288
GNU gdb (GDB) Fedora 8.2-6.fc29
..
..
Core was generated by `/usr/bin/python2 ../../../../tests/test-daemon.py
--pidfile --monitor'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f7074fbeccb in select () from /lib64/libc.so.6
Missing separate debuginfos, use: dnf debuginfo-install
python2-2.7.15-11.fc29.x86_64
(gdb) bt
#0  0x00007f7074fbeccb in select () from /lib64/libc.so.6
#1  0x00007f7074c50e10 in ?? () from
/usr/lib64/python2.7/lib-dynload/timemodule.so
#2  0x00007f70753b114b in PyEval_EvalFrameEx () from
/lib64/libpython2.7.so.1.0
#3  0x00007f70753b01ac in PyEval_EvalFrameEx () from
/lib64/libpython2.7.so.1.0
#4  0x00007f70753b1902 in PyEval_EvalCodeEx () from
/lib64/libpython2.7.so.1.0
#5  0x00007f70753b1b9d in PyEval_EvalCode () from /lib64/libpython2.7.so.1.0
#6  0x00007f70753b7b4f in ?? () from /lib64/libpython2.7.so.1.0
#7  0x00007f70753b7af8 in PyRun_FileExFlags () from
/lib64/libpython2.7.so.1.0
#8  0x00007f70753b790c in PyRun_SimpleFileExFlags () from
/lib64/libpython2.7.so.1.0
#9  0x00007f70753bd5ba in Py_Main () from /lib64/libpython2.7.so.1.0
#10 0x00007f7074eee413 in __libc_start_main () from /lib64/libc.so.6
#11 0x000055c873ddc0ae in _start ()
****************

The glibc version is 2.28 (glibc-2.28-26.fc29.x86_64)

We have seen similar crashes with ovn-controller and ovs-vswitchd in this
BZ - https://bugzilla.redhat.com/show_bug.cgi?id=1685058

And the backtrace goes to libc.

Is anyone aware of this or have any pointers what could be going on here ?

Thanks
Numan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20190316/78d6e26b/attachment-0001.html>