[Babel-users] setsockopt(IPV6_JOIN_GROUP): Cannot allocate memory

[Baptiste Jonglez]

On Fri, Jan 31, 2014 at 08:39:43PM +0100, Julien Muchembled wrote:
> > I'm not sure why babeld is hitting this limit (high number of
> > neighbours?), but you may want to increase it and see if it helps.
> 
> I increased to 32768 on 2 machines and babeld stops complaining but I don't think this is a solution.
> Most of our nodes don't have more than 20 neighbours and the errors only happen after running for a long time.
> IOW, I suspect a leak somewhere.
> 

Could you try strace-ing babeld, to see how much setsockopt() syscalls it
performs?

Use the "-tt" option to print timestamps, for instance:

  strace -tt -o /tmp/strace.log babeld


Beware, the output might get very large, especially if you have to wait a
long time before the bug is triggered.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/babel-users/attachments/20140131/616bf94c/attachment.sig>