❦ 4 mai 2017 22:37 +0100, "Israel G. Lugo" :
>> 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.
>
On 05/02/2017 04:13 PM, Vincent Bernat wrote:
> 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.
Is the
❦ 2 mai 2017 16:47 +0200, Ondrej Zajicek :
>> 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
>
On Tue, May 02, 2017 at 03:16:08PM +0200, Vincent Bernat wrote:
> Hey!
>
> Just got an instance of BIRD dying unexpectedly after displaying the
> following message:
>
> nl_get_reply: No buffer space available
>
> It's from netlink.c:
>
> int x = recvmsg(nl->fd, &m, 0);
> if (x <
Hey!
Just got an instance of BIRD dying unexpectedly after displaying the
following message:
nl_get_reply: No buffer space available
It's from netlink.c:
int x = recvmsg(nl->fd, &m, 0);
if (x < 0)
die("nl_get_reply: %m");
Manpage for netlink(7) says an applicati
