Re: [vpp-dev] VPP crash while creating nsh map #vpp #nsh #vxlan-gpe
I tried to run VPP in frontend, and got a little more stack info, not sure if that help: /usr/bin/vpp[10048]: received signal SIGSEGV, PC 0x7f6d686bdb62, faulting address 0x7f716924487c /usr/bin/vpp[10048]: #0 0x7f6d6818ae6a 0x7f6d6818ae6a /usr/bin/vpp[10048]: #1 0x7f6d67ecd890 0x7f6d67ecd890 /usr/bin/vpp[10048]: #2 0x7f6d686bdb62 l2input_node_fn_avx2 + 0x5e2 /usr/bin/vpp[10048]: #3 0x7f6d68149506 0x7f6d68149506 /usr/bin/vpp[10048]: #4 0x7f6d6814cdbc vlib_main + 0xedc /usr/bin/vpp[10048]: #5 0x7f6d68189f66 0x7f6d68189f66 /usr/bin/vpp[10048]: #6 0x7f6d67c61834 0x7f6d67c61834 /usr/bin/vpp[10048]: vl_msg_api_trace_save:252: Message table length 36210 Aborted (core dumped) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14227): https://lists.fd.io/g/vpp-dev/message/14227 Mute This Topic: https://lists.fd.io/mt/34696238/21656 Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452 Mute #nsh: https://lists.fd.io/mk?hashtag=nsh=1480452 Mute #vxlan-gpe: https://lists.fd.io/mk?hashtag=vxlan-gpe=1480452 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] VPP crash while creating nsh map #vpp #nsh #vxlan-gpe
Core dump: root@server1-38:~# cat _usr_bin_vpp.0.crash ProblemType: Crash Architecture: amd64 Date: Thu Oct 17 11:15:11 2019 DistroRelease: Ubuntu 18.04 ExecutablePath: /usr/bin/vpp ExecutableTimestamp: 1566409810 ProcCmdline: /usr/bin/vpp -c /etc/vpp/startup.conf ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcMaps: 13000e000-13002f000 rw-s 00:19 3 /dev/shm/global_vm 13002f000-13105 rw-s 00:19 4 /dev/shm/vpe-api 13105-13400e000 rw-s 01042000 00:19 3 /dev/shm/global_vm 10-100260 rw-s 00:0f 852941 /memfd:buffers-numa-0 (deleted) 100260-14 ---p 00:00 0 5616b0a6a000-5616b0b34000 r-xp fc:02 283580 /usr/bin/vpp 5616b0d33000-5616b0d34000 r--p 000c9000 fc:02 283580 /usr/bin/vpp 5616b0d34000-5616b0d35000 rw-p 000ca000 fc:02 283580 /usr/bin/vpp 5616b2a8c000-5616b2aad000 rw-p 00:00 0 [heap] 7fd0522a6000-7fd0522bd000 r-xp fc:02 917808 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fd0522bd000-7fd0524bc000 ---p 00017000 fc:02 917808 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fd0524bc000-7fd0524bd000 r--p 00016000 fc:02 917808 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fd0524bd000-7fd0524be000 rw-p 00017000 fc:02 917808 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fd0524be000-7fd054aee000 rw-p 00:00 0 7fd054aee000-7fd055eee000 rw-s 00:09 858508 socket:[858508] 7fd055eee000-7fd07a0fe000 rw-p 00:00 0 7fd07a0fe000-7fd07b4fe000 rw-s 00:09 858161 socket:[858161] 7fd07b4fe000-7fd07b501000 r-xp fc:02 269401 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/nsh_test_plugin.so 7fd07b501000-7fd07b70 ---p 3000 fc:02 269401 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/nsh_test_plugin.so 7fd07b70-7fd07b701000 r--p 2000 fc:02 269401 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/nsh_test_plugin.so 7fd07b701000-7fd07b702000 rw-p 3000 fc:02 269401 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/nsh_test_plugin.so 7fd07b702000-7fd07b706000 r-xp fc:02 269397 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/lb_test_plugin.so 7fd07b706000-7fd07b905000 ---p 4000 fc:02 269397 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/lb_test_plugin.so 7fd07b905000-7fd07b906000 r--p 3000 fc:02 269397 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/lb_test_plugin.so 7fd07b906000-7fd07b907000 rw-p 4000 fc:02 269397 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/lb_test_plugin.so 7fd07b907000-7fd07b914000 r-xp fc:02 263329 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/acl_test_plugin.so 7fd07b914000-7fd07bb13000 ---p d000 fc:02 263329 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/acl_test_plugin.so 7fd07bb13000-7fd07bb14000 r--p c000 fc:02 263329 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/acl_test_plugin.so 7fd07bb14000-7fd07bb15000 rw-p d000 fc:02 263329 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/acl_test_plugin.so 7fd07bb15000-7fd07bb1e000 r-xp fc:02 269400 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/nat_test_plugin.so 7fd07bb1e000-7fd07bd1d000 ---p 9000 fc:02 269400 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/nat_test_plugin.so 7fd07bd1d000-7fd07bd1e000 r--p 8000 fc:02 269400 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/nat_test_plugin.so 7fd07bd1e000-7fd07bd1f000 rw-p 9000 fc:02 269400 /usr/lib/x86_64-linux-gnu/vpp_api_test_plugins/nat_test_plugin.so 7fd07bd1f000-7fd085d3f000 rw-p 00:00 0 7fd085d3f000-7fd087d3f000 rw-s 00:05 852940 /memfd:stat_segment_test (deleted) 7fd087d3f000-7fd087d4a000 r-xp fc:02 923378 /lib/x86_64-linux-gnu/libnss_files-2.27.so 7fd087d4a000-7fd087f49000 ---p b000 fc:02 923378 /lib/x86_64-linux-gnu/libnss_files-2.27.so 7fd087f49000-7fd087f4a000 r--p a000 fc:02 923378 /lib/x86_64-linux-gnu/libnss_files-2.27.so 7fd087f4a000-7fd087f4b000 rw-p b000 fc:02 923378 /lib/x86_64-linux-gnu/libnss_files-2.27.so 7fd087f4b000-7fd087f51000 rw-p 00:00 0 7fd087f51000-7fd087f68000 r-xp fc:02 923375 /lib/x86_64-linux-gnu/libnsl-2.27.so 7fd087f68000-7fd088167000 ---p 00017000 fc:02 923375 /lib/x86_64-linux-gnu/libnsl-2.27.so 7fd088167000-7fd088168000 r--p 00016000
[vpp-dev] VPP crash while creating nsh map #vpp #nsh #vxlan-gpe
Hi, I got VPP crashed when trying to add more nsh map. My case is this: client -> router1 (vpp, 192.168.1.34) -> node1 (vpp, 192.168.1.37) -> ... -> node2 (vpp, 192.168.1.40) -> ... node1/2 work as nodes of a nfv cluster, ,and router1 has two vxlan-gpe tunnels with node1/2: vpp# show vxlan-gpe [0] lcl 192.168.1.34 rmt 192.168.1.37 vni 100 fib-idx 0 sw-if-idx 4 decap-next-protocol nsh [1] lcl 192.168.1.34 rmt 192.168.1.40 vni 101 fib-idx 0 sw-if-idx 11 decap-next-protocol nsh vpp# And router1 works as SFF to redirect client's icmp request to node2, trace like: Packet 6 00:04:13:626134: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x81 len 172 snaplen 172 mac 66 net 80 sec 0x5da8216b nsec 0x2708ea01 vlan 0 vlan_tpid 0 00:04:13:626138: ethernet-input IP4: 02:fe:c0:a8:01:28 -> 02:fe:c0:a8:01:22 00:04:13:626141: ip4-input UDP: 192.168.1.40 -> 192.168.1.34 tos 0x00, ttl 253, length 158, checksum 0x39b4 fragment id 0x UDP: 4790 -> 4790 length 138, checksum 0x 00:04:13:626144: ip4-lookup fib 0 dpo-idx 5 flow hash: 0x UDP: 192.168.1.40 -> 192.168.1.34 tos 0x00, ttl 253, length 158, checksum 0x39b4 fragment id 0x UDP: 4790 -> 4790 length 138, checksum 0x 00:04:13:626146: ip4-local UDP: 192.168.1.40 -> 192.168.1.34 tos 0x00, ttl 253, length 158, checksum 0x39b4 fragment id 0x UDP: 4790 -> 4790 length 138, checksum 0x 00:04:13:626148: ip4-udp-lookup UDP: src-port 4790 dst-port 4790 00:04:13:626149: vxlan4-gpe-input VXLAN-GPE: tunnel 1 next 4 error 0 00:04:13:626151: nsh-input nsh ver 0 ttl 3 len 6 (24 bytes) md_type 1 next_protocol 3 service path 14 service index 254 c1 1 c2 2 c3 3 c4 4 00:04:13:626156: error-drop rx:vxlan_gpe_tunnel1 00:04:13:626157: drop nsh-input: no mapping for nsh key vpp# Existing nsh rules are: vpp# show nsh map nsh entry nsp: 16 nsi: 255 maps to nsp: 16 nsi: 255 nsh_action push encapped by VXLAN GPE intf: 4 nsh entry nsp: 16 nsi: 254 maps to nsp: 16 nsi: 254 nsh_action pop encap-none nsh entry nsp: 15 nsi: 255 maps to nsp: 15 nsi: 255 nsh_action push encapped by VXLAN GPE intf: 4 nsh entry nsp: 15 nsi: 254 maps to nsp: 15 nsi: 254 nsh_action pop encap-none nsh entry nsp: 14 nsi: 255 maps to nsp: 14 nsi: 255 nsh_action push encapped by VXLAN GPE intf: 11 vpp# Since the packet trace complain that no expected nsp/nsi found, I add the missing nsp/nsi, using following cmd: vpp# create nsh map nsp 14 nsi 254 mapped-nsp 14 mapped-nsi 254 nsh_action pop encap-none 0 0 And once the client sent icmp packet again, the VPP would crashed immediately, and restarted, with nothing left. No other clues have been found currently, I'm guessing according to the packet trace, #1 this packet is expected to be sent to `vxlan_gpe_tunnel1`, but `vxlan4-gpe-input` shows that next idx is 4, which refer to `vxlan_gpe_tunnel0`, do I misuse vxlan-gpe tunnel here or miss some other rules? #2 if this CRASH is a known issue, what can I do to workaround this? If anybody needs any more information, I'd be glad to provide. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14192): https://lists.fd.io/g/vpp-dev/message/14192 Mute This Topic: https://lists.fd.io/mt/34696238/21656 Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452 Mute #nsh: https://lists.fd.io/mk?hashtag=nsh=1480452 Mute #vxlan-gpe: https://lists.fd.io/mk?hashtag=vxlan-gpe=1480452 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
