Hi All, While during scale tests with large numbers of routes, we occasionally hit a strange issue in our container. The *vpp process became unresponsive*, after attaching the process to gdb we could see the *vpp_main thread is stuck on a specific function*. Any pointer to debug such issues would be of great help.
*Back Trace:* #0 0x00007f6895f1bc56 in clib_bitmap_get (ai=0x7f683ad339c0, i=826) at /development/libvpp/src/vppinfra/bitmap.h:201 #1 0x00007f6895f20357 in tw_timer_expire_timers_internal_1t_3w_1024sl_ov (tw=0x7f683ad30000, now=131.6111045732342, callback_vector_arg=0x7f683ad330c0) at /development/libvpp/src/vppinfra/tw_timer_template.c:744 #2 0x00007f6895f20b36 in tw_timer_expire_timers_vec_1t_3w_1024sl_ov (tw=0x7f683ad30000, now=131.6111045732342, vec=0x7f683ad330c0) at /development/libvpp/src/vppinfra/tw_timer_template.c:814 #3 0x00007f68961fd166 in vlib_main_or_worker_loop (vm=0x7f689649ce00 <vlib_global_main>, is_main=1) at /development/libvpp/src/vlib/main.c:1857 #4 0x00007f68961fd8b1 in vlib_main_loop (vm=0x7f689649ce00 <vlib_global_main>) at /development/libvpp/src/vlib/main.c:1928 #5 0x00007f68961fe578 in vlib_main (vm=0x7f689649ce00 <vlib_global_main>, input=0x7f683a60ffb0) at /development/libvpp/src/vlib/main.c:2145 #6 0x00007f6896264865 in thread0 (arg=140087174745600) at /development/libvpp/src/vlib/unix/main.c:666 #7 0x00007f6895ebd600 in clib_calljmp () from /usr/local/lib/libvppinfra.so.1.0.1 #8 0x00007fff47e2f760 in ?? () #9 0x00007f6896264ddb in vlib_unix_main (argc=21, argv=0x563cecf5f900) at /development/libvpp/src/vlib/unix/main.c:736 Thanks, Rajith
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16759): https://lists.fd.io/g/vpp-dev/message/16759 Mute This Topic: https://lists.fd.io/mt/74973962/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
