Hello Yureka,
you are right that this should not be happening.
Would it be possible for you to enable core dumps on the routers and try
to get core files of the aborts?
If core files and binary are not easy to obtain, simple backtraces will
help us too.
We also need your config file.
Thank you for testing BIRD v3!
David
On 2/7/25 17:45, Yureka via Bird-users wrote:
After deploying bird 3.0.1, the bird process keeps crashing on several
of my routers, which had never crashed before on bird 2.x.
Within ~5min, I've seen the bird process crash with SIGABRT 27 times:
16x `Withdrawn route never seen before`
8x `Assertion '!rt_export_feed_active(&c->reimporter)' failed at
nest/proto.c:756`
2x `Assertion 'rt_export_get_state(&c->out_req) == TES_DOWN' failed at
nest/proto.c:755`
1x `Assertion '!old' failed at nest/rt-table.c:1510`
My config is using a mix of Babel with RTT extensions, OSPF, iBGP and
eBGP.
"withdrawn route never seen before" sure sounds like one of my peers
is misbehaving but
1) this should not crash bird
2) it should provide more information about which peer is misbehaving
I can not judge which of the other assertions are errors about the
bird-internal state which should never happen in the first place, or
which are caused by bad peer behaviour (which, again, should not crash
bird).
Best regards,
Yureka
--
David Petera (he/him) | BIRD Tech Support | CZ.NIC, z.s.p.o.
