From owner-freebsd-net@FreeBSD.ORG Wed Oct 13 03:06:02 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C1A016A4CE for ; Wed, 13 Oct 2004 03:06:02 +0000 (GMT) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AA5743D2D for ; Wed, 13 Oct 2004 03:06:02 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) i9D34qUr054272; Tue, 12 Oct 2004 20:04:53 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (pc1.oakwoodazabu1-unet.ocn.ne.jp [220.110.140.201]) by mail.meer.net (8.12.10/8.12.2/meer) with ESMTP id i9D34oFd054649; Tue, 12 Oct 2004 20:04:51 -0700 (PDT) (envelope-from gnn@neville-neil.com) Date: Wed, 13 Oct 2004 12:04:48 +0900 Message-ID: From: gnn@FreeBSD.org To: "Stephane Raimbault" In-Reply-To: References: User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: net@FreeBSD.org Subject: Re: Error 49, socket problem? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Oct 2004 03:06:02 -0000 At Tue, 12 Oct 2004 12:52:15 -0600, Stephane Raimbault wrote: > > I have some busy boxes part of a cluster which seems to occassionaly get an > Error 49 on various network based applications at the same time. > > Here is from an apache proxy log > > [Fri Oct 08 11:26:45 2004] [error] (49)Can't assign requested address: > proxy: HTTP: attempt to connect to 127.0.0.1:81 (127.0.0.1) failed > [Fri Oct 08 11:26:45 2004] [error] (49)Can't assign requested address: > proxy: HTTP: attempt to connect to 127.0.0.1:81 (127.0.0.1) failed > [Fri Oct 08 11:26:45 2004] [error] (49)Can't assign requested address: > proxy: HTTP: attempt to connect to 127.0.0.1:81 (127.0.0.1) failed > [Fri Oct 08 11:26:46 2004] [error] (49)Can't assign requested address: > proxy: HTTP: attempt to connect to 127.0.0.1:81 (127.0.0.1) failed > [Fri Oct 08 11:26:46 2004] [error] (49)Can't assign requested address: > proxy: HTTP: attempt to connect to 127.0.0.1:81 (127.0.0.1) failed > > > Various other things at the same time give a similar error. Am I running > out of sockets on the system? What is the best way to diagnose this > problem. It seems pretty intermitent, however it seems to occur when the > boxes are at some of the busiest moments in it's day. That's the loopback address (127.0.0.1) and the error you're getting is "Address Not Available" (/usr/include/sys/errno.h shows this). I have no idea what apahce is trying to do in that case, but you should attempt to figure that out. One theory is that this is some sort of external attack which puts the loopback address into a URL to try and get apache to do something "bad". But, I'm not an apache expert. Later, George