Actually FRR bgpd enables this by default:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Apr 1 2022
Hi, @dberlin ! Thanks, you are right about the root cause.
I believe that we need to remove the max-size and action-on-max-size from rsyslog.conf. So, leave everything related to rotating logs to logrotate, and to sending logs to rsyslog - UNIX-way. :)
More detail :
I happened today in 17 vyos clusters after a switch failure. Same logs and no bgp process running:
Mar 31 2022
I can confirm that the issue is fixed on today's rolling release!
Submitted this PR: https://github.com/vyos/vyos-1x/pull/1256
PR https://github.com/vyos/vyos-1x/pull/1260
set protocols bgp parameters no-suppress-duplicates
Mar 30 2022
Bugfix just got merged into FRR codebase - next VyOS rolling ISO image will have the fix.
Thank you. I can confirm it works as expected in 1.3.1-S1.
Issue found.
On freh 1.3.1-S1 intallation:
Mar 29 2022
Hi @freelancer . PR mentioned by @Viacheslav was merged on February 17, so fix should be included in 1.3.1
Is this fixed in the released 1.3.1? It looks like it was merged into equuleus, but I don't see it in the 1.3.1 changelog at https://blog.vyos.io/vyos-1.3.1-release.
Mar 28 2022
FRR bugreport filed https://github.com/FRRouting/frr/issues/10911
@m.korobeinikov
Does your configuration include this scripts corrections? https://docs.vyos.io/en/equuleus/automation/command-scripting.html#executing-configuration-scripts
The below is also not possible on route maps
like with Mikrotik you can bond almost any interface, like vlans even
Mar 27 2022
I'm not comfortable posting my config here for ever but I've uploaded it to ubuntu pastebin and set it to expire in a week: https://paste.ubuntu.com/p/BW5KxyjPQr/
Can not get it crashed here. Please share your full config.
Still seems to be broken on 1.4-rolling-202203270930
Re-run with the latest FRR code-base and it also seems to be fixed - please try the latest VyOS version ;)
This is a problem with the underlaying routing daemon FRR.
Feels like the bug was introduced in https://github.com/FRRouting/frr/commit/36295a387c241d3dba7aaa305a1860a6a07ab0cf