Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zebra and bgp crash at startup in master #170

Closed
dslicenc opened this issue Feb 6, 2017 · 0 comments
Closed

zebra and bgp crash at startup in master #170

dslicenc opened this issue Feb 6, 2017 · 0 comments
Assignees

Comments

@dslicenc
Copy link
Member

dslicenc commented Feb 6, 2017

installing frr deb causes core files to be generated at startup. Stacks follow:

bgpd

[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/bgpd --daemon -A 127.0.0.1'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f1c0068723e in vty_log_fixed ( buf=buf@entry=0x7ffe94a98e09 "BGP: Received signal 11 at 1486365436 (si_addr 0x0, PC 0x7f1c006871a1); aborting...", len=len@entry=83) at vty.c:2572 2572 vty.c: No such file or directory. (gdb) bt #0 0x00007f1c0068723e in vty_log_fixed ( buf=buf@entry=0x7ffe94a98e09 "BGP: Received signal 11 at 1486365436 (si_addr 0x0, PC 0x7f1c006871a1); aborting...", len=len@entry=83) at vty.c:2572 #1 0x00007f1c006a10d5 in zlog_signal (signo=<optimized out>, action=action@entry=0x7f1c006c619b "aborting...", siginfo=<optimized out>, program_counter=0x7f1c006871a1 <vty_log+79>) at log.c:499 #2 0x00007f1c006ab9d0 in core_handler (signo=<optimized out>, siginfo=<optimized out>, context=<optimized out>) at sigevent.c:235 #3 <signal handler called> #4 vty_log (level=0x0, proto_str=proto_str@entry=0x7ffe94a99538 "BGP: ", format=format@entry=0x7f1c006c01ec "Assertion %s' failed in file %s, line %u, function %s",
ctl=ctl@entry=0x7ffe94a99558, va=va@entry=0x7ffe94a995d8) at vty.c:2543
#5 0x00007f1c006a0b3b in vzlog (zl=0x1441590, priority=,
format=0x7f1c006c01ec "Assertion %s' failed in file %s, line %u, function %s", args=args@entry=0x7ffe94a995d8) at log.c:260 #6 0x00007f1c006a12d9 in zlog (zl=zl@entry=0x0, priority=priority@entry=2, format=format@entry=0x7f1c006c01ec "Assertion %s' failed in file %s, line %u, function %s") at log.c:677
#7 0x00007f1c006a1809 in _zlog_assert_failed (assertion=assertion@entry=0x7f1c006c71d5 "mt->n_alloc",
file=file@entry=0x7f1c006c71cc "memory.c", line=line@entry=43,
function=function@entry=0x7f1c006c7268 <func.8042> "mt_count_free") at log.c:722
#8 0x00007f1c006836c3 in mt_count_free (mt=) at memory.c:43
#9 0x00007f1c006b19a2 in mt_count_free (mt=) at memory.c:87
#10 qfree (mt=, ptr=) at memory.c:89
#11 0x00007f1c00693151 in thread_master_free (m=0x143b120) at thread.c:523
#12 0x000000000041552d in bgp_exit (status=0) at bgp_main.c:309
#13 sigint () at bgp_main.c:225
#14 0x00007f1c006aba24 in quagga_sigevent_process () at sigevent.c:111
#15 0x00007f1c006936a1 in thread_fetch (m=0x143b120, fetch=fetch@entry=0x7ffe94a99850) at thread.c:1172
#16 0x0000000000414210 in main (argc=4, argv=0x7ffe94a999e8) at bgp_main.c:570
(gdb)

zebra:

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by /usr/lib/frr/zebra -s 90000000 --daemon -A 127.0.0.1'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f00649c923e in vty_log_fixed ( buf=buf@entry=0x7ffc42b88809 "ZEBRA: Received signal 11 at 1486365436 (si_addr 0x0, PC 0x7f00649c91a1); aborting...", len=len@entry=85) at vty.c:2572 2572 vty.c: No such file or directory. (gdb) bt #0 0x00007f00649c923e in vty_log_fixed ( buf=buf@entry=0x7ffc42b88809 "ZEBRA: Received signal 11 at 1486365436 (si_addr 0x0, PC 0x7f00649c91a1); aborting...", len=len@entry=85) at vty.c:2572 #1 0x00007f00649e30d5 in zlog_signal (signo=<optimized out>, action=action@entry=0x7f0064a0819b "aborting...", siginfo=<optimized out>, program_counter=0x7f00649c91a1 <vty_log+79>) at log.c:499 #2 0x00007f00649ed9d0 in core_handler (signo=<optimized out>, siginfo=<optimized out>, context=<optimized out>) at sigevent.c:235 #3 <signal handler called> #4 vty_log (level=0x0, proto_str=proto_str@entry=0x7ffc42b88f38 "ZEBRA: ", format=format@entry=0x7f0064a021ec "Assertion %s' failed in file %s, line %u, function %s",
ctl=ctl@entry=0x7ffc42b88f58, va=va@entry=0x7ffc42b88fd8) at vty.c:2543
#5 0x00007f00649e2b3b in vzlog (zl=0xce5040, priority=,
format=0x7f0064a021ec "Assertion %s' failed in file %s, line %u, function %s", args=args@entry=0x7ffc42b88fd8) at log.c:260 #6 0x00007f00649e32d9 in zlog (zl=zl@entry=0x0, priority=priority@entry=2, format=format@entry=0x7f0064a021ec "Assertion %s' failed in file %s, line %u, function %s") at log.c:677
#7 0x00007f00649e3809 in _zlog_assert_failed (assertion=assertion@entry=0x7f0064a091d5 "mt->n_alloc",
file=file@entry=0x7f0064a091cc "memory.c", line=line@entry=43,
function=function@entry=0x7f0064a09268 <func.8042> "mt_count_free") at log.c:722
#8 0x00007f00649c56c3 in mt_count_free (mt=) at memory.c:43
#9 0x00007f00649f39a2 in mt_count_free (mt=) at memory.c:87
#10 qfree (mt=, ptr=) at memory.c:89
#11 0x00007f00649d5151 in thread_master_free (m=0xce86e0) at thread.c:523
#12 0x00000000004105f6 in sigint () at main.c:228
#13 0x00007f00649eda24 in quagga_sigevent_process () at sigevent.c:111
#14 0x00007f00649d56a1 in thread_fetch (m=0xce86e0, fetch=fetch@entry=0x7ffc42b89280) at thread.c:1172
#15 0x000000000040ca64 in main (argc=6, argv=0x7ffc42b89418) at main.c:481
(gdb)

Showed to Donald and he thinks he knows the issue and suggested assigning to him.

donaldsharp added a commit to donaldsharp/frr that referenced this issue Feb 6, 2017
thread.c was using malloc.  This was found by the
assert added to memory.c.

Fixes issues FRRouting#170

Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Jun 24, 2021
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Jun 24, 2021
When VNI configuration is performed using VLAN-VNI mapping (i.e., without
individual VXLAN interfaces) and flooded traffic is handled via multicast,
the multicast group corresponding to the VNI needs to be explicitly read
from the bridge FDB. This is relevant in the case of netlink interface to
the kernel and for the scenario where a new VNI is provisioned or comes up.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2603831
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Dec 7, 2022
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Dec 7, 2022
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 3, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 3, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 4, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 7, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 7, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 7, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 8, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 8, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 8, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 9, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 9, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
sworleys pushed a commit to sworleys/frr that referenced this issue Feb 9, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 10, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
sworleys pushed a commit to sworleys/frr that referenced this issue Feb 13, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)

Signed-off-by: Stephen Worley <sworley@nvidia.com>
sworleys pushed a commit to sworleys/frr that referenced this issue Feb 13, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)

Signed-off-by: Stephen Worley <sworley@nvidia.com>
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 15, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 15, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 17, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 23, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 24, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 27, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Feb 27, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Mar 8, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Mar 14, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Mar 20, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Mar 21, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Mar 27, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
donaldsharp pushed a commit to donaldsharp/frr that referenced this issue Mar 31, 2023
When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.

Signed-off-by: Vivek Venkatraman <vivek@nvidia.com>

Ticket: #2613048
Reviewed By:
Testing Done:
1. Manual verification - logs in the ticket
2. Precommit (user job FRRouting#171) and evpn-min (user job FRRouting#170)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants