From: Ben Greear <greearb@candelatech.com>
To: NetDev <netdev@vger.kernel.org>
Subject: avahi error: IP_ADD_MEMBERSHIP failed: No buffer space available
Date: Tue, 30 May 2006 11:07:47 -0700 [thread overview]
Message-ID: <447C89F3.5040909@candelatech.com> (raw)
This is an FC5 64-bit system with 1GB RAM and dual-core Opteron.
When I create a bunch of virtual interfaces, I see this in
/var/log/messages. The kernel is 2.6.16.16 plus my hacks.
At first look, it doesn't appear I actually need the avahi tool, so
I'm just going to disable it. But, I thought someone might
want to be aware of the problem...
May 30 11:01:37 x64-1u avahi-daemon[2022]: Joining mDNS multicast group on inter
face eth2#16.IPv4 with address 172.1.2.18.
May 30 11:01:37 x64-1u avahi-daemon[2022]: Registering new address record for 17
2.1.2.18 on eth2#16.
May 30 11:01:37 x64-1u avahi-daemon[2022]: New relevant interface eth2#17.IPv4 f
or mDNS.
May 30 11:01:37 x64-1u avahi-daemon[2022]: Joining mDNS multicast group on inter
face eth2#17.IPv4 with address 172.1.2.19.
May 30 11:01:37 x64-1u avahi-daemon[2022]: IP_ADD_MEMBERSHIP failed: No buffer s
pace available
May 30 11:01:37 x64-1u avahi-daemon[2022]: Registering new address record for 17
2.1.2.19 on eth2#17.
May 30 11:01:37 x64-1u avahi-daemon[2022]: New relevant interface eth2#18.IPv4 f
or mDNS.
May 30 11:01:37 x64-1u avahi-daemon[2022]: Joining mDNS multicast group on inter
face eth2#18.IPv4 with address 172.1.2.20.
May 30 11:01:37 x64-1u avahi-daemon[2022]: IP_ADD_MEMBERSHIP failed: No buffer s
pace available
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2006-05-30 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 18:07 Ben Greear [this message]
2006-05-30 18:34 ` avahi error: IP_ADD_MEMBERSHIP failed: No buffer space available Stefan Rompf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=447C89F3.5040909@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).