You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens every time I run the topotests/bgp_l3vpn_to_bgp_vrf test. Looks like zebra in one of the rX always crash( it's slightly different every time on which one crashes) The stack trace is the same though.
The text was updated successfully, but these errors were encountered:
I think this is a variant of the same thing:
r1: zebra crashed. Core file found - Backtrace follows:
[New LWP 23705]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/frr/zebra'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007f257f6fa428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#0 0x00007f257f6fa428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #1 0x00007f257f6fc02a in __GI_abort () at abort.c:89 #2 0x00007f25800fca74 in _zlog_assert_failed (assertion=assertion@entry=0x556acb147492 "!client->t_write", file=file@entry=0x556acb14745c "zebra/zserv.c", line=line@entry=627, function=function@entry=0x556acb147890 <func.15934> "zserv_handle_client_close") at lib/log.c:710 #3 0x0000556acb125028 in zserv_handle_client_close (thread=) at zebra/zserv.c:627 #4 0x00007f258011ea30 in thread_call (thread=thread@entry=0x7ffd69433910) at lib/thread.c:1576 #5 0x00007f25800f9f58 in frr_run (master=0x556acd3615d0) at lib/libfrr.c:879 #6 0x0000556acb0df1c4 in main (argc=1, argv=0x7ffd69433bf8) at zebra/main.c:394
r1: Daemon bgpd not running
2018-06-21 04:06:25,258 ERROR: assert failed at "bgp_vrf_netns.test_bgp_vrf_netns_topo/test_bgp_vrf_learn": r1: Daemon bgpd not running
This happens every time I run the topotests/bgp_l3vpn_to_bgp_vrf test. Looks like zebra in one of the rX always crash( it's slightly different every time on which one crashes) The stack trace is the same though.
The text was updated successfully, but these errors were encountered: