From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <43D07B91.1090309@list.ru> Date: Fri, 20 Jan 2006 08:56:33 +0300 From: Genix User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050815) X-Accept-Language: en-us, en MIME-Version: 1.0 To: shigorin@gmail.com, ALT Linux Sisyphus discussion list Subject: Re: [sisyphus] Re: =?KOI8-R?Q?=F3=D0=CC=CF=DB=CE=CF=CA_=C7=CC=C0?= =?KOI8-R?Q?=CB=CF=C4=D2=CF=CD_=C1_ALC3_=CE=C1_nForce2?= References: <43CFD29F.1050205@diyaorg.dp.ua> <20060119192016.GE11208@osdn.org.ua> In-Reply-To: <20060119192016.GE11208@osdn.org.ua> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 20 Jan 2006 05:56:03.0517 (UTC) FILETIME=[32687ED0:01C61D86] Cc: X-BeenThere: sisyphus@lists.altlinux.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ALT Linux Sisyphus discussion list List-Id: ALT Linux Sisyphus discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2006 05:56:19 -0000 Archived-At: List-Archive: List-Post: Michael Shigorin wrote: >>- часто даже localhost не пингуется и при попытке пинговать >>выдаёт сообщение: >>//========================================= >>[root@dig root]# ping 10.0.0.1 >>connect: No buffer space available >>[root@dig root]# ping localhost >>connect: No buffer space available >>//========================================= > > > А вот этого не видел. нашел в гугле, может поможет: http://archive.linuxvirtualserver.org/html/lvs-users/2002-09/msg00238.html A. Possible Causes for this Problem ----------------------------------- o fragmentation You might have a big amount of fragmented packets coming in an your buffer space simply can't cope with it anymore before all packets are assembled. o MTU(route output) < MTU(needed) In case this occurs, the kernel needs to fragment the packets and send them off then causing a lot of skb_alloc() and memory allocations in that direction. o wrong default gateway configuration You might run your box with a wrong DGW pointing to an internal IP address configured on your box. The reason why it still works could be an intelligent router before your box. o neigbour table overflow Your arp cache experienced some kind of overflow due to strange settings in /proc/sys/net/ipv4/neigh/<$INTERFACE>/* or due to circular routing entries. o generally a weird /proc/sys/net/* configuration It could be anything there, let's hope it's not there. B. How to Hunt Down those Problems ---------------------------------- I need the following outputs _when_ the problems occurs: o ip -s -s link show o ip addr show o ip link show dev lo o ip rule show o ip route show table main o cat /proc/net/softnet_stat o cat /proc/net/rt_cache_stat o cat /proc/net/raw (especially after a ping) o cat /proc/net/netlink o cat /proc/slabinfo Could you also test if starting a tcpdump on either one of the interfaces triggers the problem somehow in that that the error messages show up more frequently? C. Possible Band-Aid for the Problem ------------------------------------ o reboot (this is not really a solution) o crontab that sets link state down/up (also not very nice) o crontab that does 'ip route flush cache' I hope you can do something with my information and that it will reveil a hint on where to search next. Sorry that we don't have a solution for this right now. -- У каждого в башке свои тараканы...