Bird dying on nl_get_reply

[Vincent Bernat]

 ❦  2 mai 2017 16:47 +0200, Ondrej Zajicek <santiago at crfreenet.org> :

>> Or maybe we could just ignore the error and wait for
>> the next kernel sync to catch up. Or the 8192 value could be configured
>> at build-time. What's the best option?
>
> Well, you could try increase NL_RX_SIZE to say 64k. But the best solution
> would be to have a proper error handling in nl_get_reply(). The main
> question is why the buffer was full as it is not the buffer that get
> async notifications, it just gets responses.

On the hundreds BIRD running on our systems for a few months, it's the
first occurrence I had. The server doesn't have that many routes (less
than a hundred) either (we have servers with far more routes). I'll wait
if it happens again.
-- 
10.0 times 0.1 is hardly ever 1.0.
            - The Elements of Programming Style (Kernighan & Plauger)