From owner-freebsd-current@FreeBSD.ORG Fri Apr 22 18:21:05 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44C2B16A4CE for ; Fri, 22 Apr 2005 18:21:05 +0000 (GMT) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0980243D53 for ; Fri, 22 Apr 2005 18:21:05 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.50 (FreeBSD)) id 1DP2m0-0006PU-Nq; Fri, 22 Apr 2005 18:21:04 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.50 (FreeBSD)) id 1DP2lt-0003nb-CN; Fri, 22 Apr 2005 08:20:57 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17001.16520.774703.612151@roam.psg.com> Date: Fri, 22 Apr 2005 08:20:56 -1000 To: Charles Swiger References: <17001.9557.627987.505930@roam.psg.com> cc: FreeBSD Current Subject: Re: significant increase in ipfw pullup failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 18:21:05 -0000 >> on a 1ru system with an fxp >> yesterday, i cvsupped Apr 21 17:00 and built, first time in a few weeks >> previously i got an ipfw pullup failed a couple of times a day >> now i get them every few minutes >> >> anyone else seeing this, or should i start to send someone into >> the colo to check cables? > > What it means is that the IPFW code didn't see a long enough packet to > contain enough data to be logged usefully. That could be a sign of > hardware problems like a flaky cable or a NIC that is going wonky: if > you can check "netstat -i" and look for excessive input errors or > collisions. > > If the machine is connected to a managed switch, look for "runt > packets", smaller than 54 bytes (56?, whatever the minimum valid size > is).... sorry, did all that before whining. but, as i might not have, your asking was quite appropriate. # netstat -m 204 mbufs in use 134/13120 mbuf clusters in use (current/max) 0/4/3536 sfbufs in use (current/peak/max) 319 KBytes allocated to network 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile # netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll fxp0 1500 00:30:48:51:c8:5e 47087068 0 46603594 0 0 fxp0 1500 RG.NET/24 rip 47394365 - 47237789 - - fxp0 1500 ssh/32 ssh 5129 - 0 - - fxp1* 1500 00:30:48:51:c8:5f 0 0 0 0 0 lo0 16384 857260 0 857260 0 0 lo0 16384 your-net localhost 223262 - 223262 - - it appears to be a plain increase in the reporting of pullup failed. randy