LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

RE: No buffer space available

To: 'Roberto Nibali' <ratz@xxxxxxxxxxxx>, lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: No buffer space available
From: Jeremy Kusnetz <JKusnetz@xxxxxxxx>
Date: Mon, 30 Sep 2002 11:32:07 -0400
Yikes, here is what I'm getting in dmesg now.  I have not run the commands
yet, but have taken my eth2 up and down out of the cron job:

nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
NET: 34 messages suppressed.
Neighbour table overflow.
NET: 13 messages suppressed.
Neighbour table overflow.
NET: 5 messages suppressed.
Neighbour table overflow.
NET: 10 messages suppressed.
Neighbour table overflow.
NET: 14 messages suppressed.
Neighbour table overflow.
NET: 6 messages suppressed.
Neighbour table overflow.
IPVS: ip_route_output error, dest: 10.75.128.14
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
NET: 15 messages suppressed.
Neighbour table overflow.
NET: 32 messages suppressed.
Neighbour table overflow.
NET: 45 messages suppressed.
Neighbour table overflow.
NET: 13 messages suppressed.
Neighbour table overflow.
NET: 31 messages suppressed.
Neighbour table overflow.
NET: 52 messages suppressed.
Neighbour table overflow.
NET: 21 messages suppressed.
Neighbour table overflow.
NET: 12 messages suppressed.
Neighbour table overflow.
NET: 11 messages suppressed.
Neighbour table overflow.
NET: 18 messages suppressed.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
RPC: sendmsg returned error 105
nfs: RPC call returned error 105
NET: 25 messages suppressed.
Neighbour table overflow.
NET: 1 messages suppressed.
Neighbour table overflow.
NET: 38 messages suppressed.
Neighbour table overflow.
NET: 41 messages suppressed.


> Ok. But why again do you need 53 VIP's? A VIP is a service and I have a 
> bit a hard time understanding how you can find 53 services to load 
> balance. I mean, I know about /etc/services, but seriously may I ask, 
> what you're load balancing? Could dump a 'ipvsadm -n -L' for me please?

Well we run ISP services for 53 different domains.  Each domain get's their
own IP address, thus 53 VIPs.  Each of those 53 VIPs get their own mail,
pop, web, radius, etc. etc.  Thus the 53 VIPs * 8 services each, * number of
realservers.

I think I can take the 8 services each down to 3.  FTP and POP need to have
their own IP address they listen to so I know which domain the user came
from, so they just need to use their username instead of username@domainname
to authenticate.  HTTP-SSL needs it's own IP address for each domain since
you can do named virtual hosting with apache+ssl.  The rest of the services
can just listen to the realservers main IP address.

All that should help, but it still leaves me with 1000 RIPs

> Yes, I didn't realize that you're checking 2688 RIPs :) Ok, this looks 
> like a new dimension to LVS. I'm glad someone really tries something 
> funny after all those years of LVS development.

Glad I be the first! Don't know whether I should :) or :(

> Well, you can try it right away and see if that line stil appears in the 
> dmesg?

I'll try and let you know.



<Prev in Thread] Current Thread [Next in Thread>