-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
bgpd crash #9046
Comments
Can you provide a pcap of an example session where this occurs? |
And |
Hi, Sure. Last night I've compiled 8.0-dev for one of the routers and keep 8.1-dev on other one. Even 8.0-dev is crashing:
My configs that I'm running: Now I will try to do a tcpdump over my all BGP sessions and I'll post them. Is ok? |
Could you disable |
By the way, would it be possible to get a full coredump? |
Sure, I've set my router to dump the core. Here are the PCAPs: Crash happend at 09:46:40 for R01 and 09:46:40 for R02, EEST / Bucharest time. |
Thanks, I'm waiting for coredump, that would be the best thing to figure out what's the problem here. |
Yep. I'm waiting for the next crash. I'm also doing tcpdump again for this crash. I set the "core" limit to "unlimited" for BGP process. I hope it will dump the core. |
I will try to disable it after this crash. |
Ok, got the crash and core dump:
Here is the core dump for R01: https://nextcloud.easynet.dev/index.php/s/PHCqmLXQccxtL78 I have also the debug symbols installed on my systems. I disabled the |
Could you run on your machine and paste the output here?:
|
Sure. Here it is:
Even with no bgp dumpening I still got a crash. |
Can we have a coredump when it crashes without BGP dampening enabled as well? |
Sure. I'm waiting for it :). |
This is the core dump on R02 with frr 8.0-dev:
|
This crash is also with BGP dampening enabled. But you said it's crashing even when it's disabled. Or I'm missing something? |
Yes. It had bgp dampening enabled. After crash I disabled it. I'm still waiting for R01 to crash with dampening off. |
I don't know if that crash it was without bgp dampening off or not, but after I posted the crash log for R01 I disabled the bgp dampening. I'm not sure if it took the command or not, but in the |
I'm trying to replicate the issue, but no joy. Maybe you have a minimal configuration to replicate this crash? |
Hi @ton31337, Unfortunately the daemon didn't crashed with dampening off. |
I tried to build a FRR testbed. After I activated on testbed bgp damping, R01 crashed. Also the FRR testbed crashed. Both are running latest 8.1. |
Any chance I can get this testbed for testing? |
I'm trying, but I'm facing another issue: zebra is crashing in latest 8.1-dev :(.
After few seconds zebra is crashing, but without an crash signal:
This FRR testbed is receiving the full table of IPv4. |
Ok. Fixed the issue. Seems that with 4GB of RAM is not enough to keep zebra running with full table :|. I've activated the bgp dampening on this testbed. |
OK, I'm able to replicate the crash on my testbed. |
No, coredump is needed only. But it would be the best if I would have an access to that box. |
Sure. Check your email please. |
bgp_damp_info_unclaim already calls bgp_reuselist_del. We must not call it again here. Fixes FRRouting#9046. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
@EasyNetDev would be great if you could check this PR – #9215. |
bgp_damp_info_unclaim already calls bgp_reuselist_del. We must not call it again here. Fixes FRRouting#9046. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com> (cherry picked from commit 96d6b8c)
bgp_damp_info_unclaim already calls bgp_reuselist_del. We must not call it again here. Fixes FRRouting#9046. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com> (cherry picked from commit 96d6b8c)
bgp_damp_info_unclaim already calls bgp_reuselist_del. We must not call it again here. Fixes FRRouting#9046. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com> (cherry picked from commit 96d6b8c)
bgp_damp_info_unclaim already calls bgp_reuselist_del. We must not call it again here. Fixes FRRouting#9046. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com> (cherry picked from commit 96d6b8c)
bgp_damp_info_unclaim already calls bgp_reuselist_del. We must not call it again here. Fixes FRRouting#9046. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
bgp_damp_info_unclaim already calls bgp_reuselist_del. We must not call it again here. Fixes FRRouting#9046. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
bgp_damp_info_unclaim already calls bgp_reuselist_del. We must not call it again here. Fixes FRRouting#9046. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
bgp_damp_info_unclaim already calls bgp_reuselist_del. We must not call it again here. Fixes FRRouting#9046. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
bgp_damp_info_unclaim already calls bgp_reuselist_del. We must not call it again here. Fixes FRRouting#9046. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
bgp_damp_info_unclaim already calls bgp_reuselist_del. We must not call it again here. Fixes FRRouting#9046. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
Hi,
I notice that my FRR is crashing with these in logs, on both routers:
R01:
R02:
[X] Did you check if this is a duplicate issue?
[X] Did you test it on the latest FRRouting/frr master branch?
Versions
This is the version of FRR:
The text was updated successfully, but these errors were encountered: