Hi all, I am facing an occasional VPP crash when running CLIs ( show node counters) whilst under load. I am using VPP version v18.01.1-100~g3a6948c. Upgrading to a newer version is not an option for me currently.
VPP cores out of 'unix_cli_read_ready' Here is the BT: *(gdb) bt* *#0 0x00002ab99d694207 in raise () from /lib64/libc.so.6* *#1 0x00002ab99d6958f8 in abort () from /lib64/libc.so.6* *#2 0x0000000000405ef3 in os_panic () at /bfs-build/build-area.42/builds/LinuxNBngp_mainline_RH7/2018-09-13-1353/third-party/vpp/vpp_1801/build-data/../src/vpp/vnet/main.c:268* *#3 0x00002ab99cb106d2 in clib_mem_alloc_aligned_at_offset (os_out_of_memory_on_failure=1, align_offset=<optimized out>, align=4, size=8589930500)* * at /bfs-build/build-area.42/builds/LinuxNBngp_mainline_RH7/2018-09-13-1353/third-party/vpp/vpp_1801/build-data/../src/vppinfra/mem.h:105* *#4 vec_resize_allocate_memory (v=<optimized out>, length_increment=4294967296, data_bytes=<optimized out>, header_bytes=<optimized out>, header_bytes@entry=0, data_align=data_align@entry=4)* * at /bfs-build/build-area.42/builds/LinuxNBngp_mainline_RH7/2018-09-13-1353/third-party/vpp/vpp_1801/build-data/../src/vppinfra/vec.c:84* *#5 0x00002ab99b79d349 in _vec_resize (data_align=<optimized out>, header_bytes=<optimized out>, data_bytes=<optimized out>, length_increment=<optimized out>, v=<optimized out>)* * at /bfs-build/build-area.42/builds/LinuxNBngp_mainline_RH7/2018-09-13-1353/third-party/vpp/vpp_1801/build-data/../src/vppinfra/vec.h:142* *#6 unix_cli_read_ready (uf=0x2ab99fe8509c) at /bfs-build/build-area.42/builds/LinuxNBngp_mainline_RH7/2018-09-13-1353/third-party/vpp/vpp_1801/build-data/../src/vlib/unix/cli.c:2504* *#7 0x00002ab99b7a900a in linux_epoll_input (vm=<optimized out>, node=<optimized out>, frame=<optimized out>)* * at /bfs-build/build-area.42/builds/LinuxNBngp_mainline_RH7/2018-09-13-1353/third-party/vpp/vpp_1801/build-data/../src/vlib/unix/input.c:198* *#8 0x00002ab99b772caa in dispatch_node (last_time_stamp=54044224341205389, frame=0x0, dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_PRE_INPUT, node=0x2ab99e234f40, vm=0x2ab99b9c42c0 <vlib_global_main>)* * at /bfs-build/build-area.42/builds/LinuxNBngp_mainline_RH7/2018-09-13-1353/third-party/vpp/vpp_1801/build-data/../src/vlib/main.c:988* *#9 vlib_main_or_worker_loop (is_main=1, vm=0x2ab99b9c42c0 <vlib_global_main>) at /bfs-build/build-area.42/builds/LinuxNBngp_mainline_RH7/2018-09-13-1353/third-party/vpp/vpp_1801/build-data/../src/vlib/main.c:1498* *#10 vlib_main_loop (vm=0x2ab99b9c42c0 <vlib_global_main>) at /bfs-build/build-area.42/builds/LinuxNBngp_mainline_RH7/2018-09-13-1353/third-party/vpp/vpp_1801/build-data/../src/vlib/main.c:1628* *#11 vlib_main (vm=vm@entry=0x2ab99b9c42c0 <vlib_global_main>, input=input@entry=0x2ab9a055efa0)* * at /bfs-build/build-area.42/builds/LinuxNBngp_mainline_RH7/2018-09-13-1353/third-party/vpp/vpp_1801/build-data/../src/vlib/main.c:1783* Has anyone faced this issue? Any help will be greatly appreciated. Regards, Siddarth
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10830): https://lists.fd.io/g/vpp-dev/message/10830 Mute This Topic: https://lists.fd.io/mt/27367342/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
