From owner-freebsd-stable@FreeBSD.ORG Tue Oct 11 21:28:14 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 198721065670 for ; Tue, 11 Oct 2011 21:28:14 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id D15F48FC08 for ; Tue, 11 Oct 2011 21:28:13 +0000 (UTC) Received: from PWSVL-EXCHTS-02.internal.cacheflow.com (sai-rp.bluecoat.com [10.2.2.126] (may be forged)) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id p9BLSBko024045 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Oct 2011 14:28:12 -0700 (PDT) Received: from PWSVL-EXCMBX-01.internal.cacheflow.com ([fe80::15bc:12e2:4676:340f]) by PWSVL-EXCHTS-02.internal.cacheflow.com ([fe80::4910:317f:407:6ecc%14]) with mapi id 14.01.0289.001; Tue, 11 Oct 2011 14:28:06 -0700 From: "Li, Qing" To: Steven Hartland , "freebsd-stable@freebsd.org" Thread-Topic: serious packet routing issue causing ntpd high load? Thread-Index: AQHMhzIZXtTqHHvuj0KxmXj++SlrlJV3qfww Date: Tue, 11 Oct 2011 21:28:06 +0000 Message-ID: References: <2740DA0E7C0F495BA00E6D4BC0FE8F37@multiplay.co.uk> <040F9FF759DA441392432EDBD5C4D2CF@multiplay.co.uk> In-Reply-To: <040F9FF759DA441392432EDBD5C4D2CF@multiplay.co.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.2.2.106] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "liv3d@multiplay.co.uk" Subject: RE: serious packet routing issue causing ntpd high load? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Oct 2011 21:28:14 -0000 Okay, I just reproduced the problem. The strange thing is the routing message appears to be endless, but if I exit "route monitor" and=20 restart it, the message disappears. That indicates to me it is not the kernel that is generating the routing message continuously, but maybe it is a socket buffer issue ? Otherwise when "route monitor" is resumed the messages should also resume, which is not the case here. Of course why the DNS message being generated in FIB <1> triggers a=20 RTM_MISS in FIB <2> is an issue and I am looking into it as well. --Qing > -----Original Message----- > From: Steven Hartland [mailto:killing@multiplay.co.uk] > Sent: Monday, October 10, 2011 2:51 AM > To: Li, Qing; freebsd-stable@freebsd.org > Cc: liv3d@multiplay.co.uk > Subject: Re: serious packet routing issue causing ntpd high load? >=20 > ----- Original Message ----- > From: "Li, Qing" >=20 > >> RTM_MISS: Lookup failed on this address: len 184, pid: 0, seq 0, > errno > >> 0, flags: > >> locks: inits: > >> sockaddrs: > >> ::A.B.C.D > >> > > > > Would it be possible for you to email me what exactly does > "::A.B.C.D" > > map into WRT your system or infrastructure ? >=20 > Sorry for the slow reply been out of the country. >=20 > All the hosts are local machines same /24 connecting to the server for > mysql. It seems to be that every packet either to or from for the mysql > server is generating an RTM_MISS. >=20 > > And are you able to share your "ifconfig -a" and "netstat -rn" output > > with me privately ? >=20 > On its way. >=20 > Regards > Steve >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > This e.mail is private and confidential between Multiplay (UK) Ltd. and > the person or entity to whom it is addressed. In the event of > misdirection, the recipient is prohibited from using, copying, printing > or otherwise disseminating it or any information contained in it. >=20 > In the event of misdirection, illegible or incomplete transmission > please telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk.