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 server perhaps running other software that writes to netlink? My problem that lead to the fix on async socket was related to conntrackd, making huge amounts of writes. Perhaps that, or some other kind of low-level network related software? Regards, Israel
