From owner-freebsd-stable@FreeBSD.ORG Mon Nov 21 09:37:33 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81BEB16A41F for ; Mon, 21 Nov 2005 09:37:33 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35B2243D45 for ; Mon, 21 Nov 2005 09:37:33 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id E55E746BD0; Mon, 21 Nov 2005 04:37:31 -0500 (EST) Date: Mon, 21 Nov 2005 09:37:31 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Laurent C In-Reply-To: Message-ID: <20051121092647.Q49718@fledge.watson.org> References: <437F6315.4000403@gmail.com> <20051119180128.X82553@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: [FreeBSD6] kinfo_size mismatch 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: Mon, 21 Nov 2005 09:37:33 -0000 On Mon, 21 Nov 2005, Laurent C wrote: >> This is almost certainly a mismatch between the kernel version and a >> monitoring tool that is trying to inspect kernel state (specifically, >> retrieve process lists). If your buildworld/installworld doesn't match >> your kernel version, then you need to rebuild and make sure everything >> is in sync. If it does, it's probably a third-party package that is out >> of sync and needs updating. > > Ok, I will try to buildworld and builkernel again after a fresh cvsup. > But for "third party packages" do you mean the "port tree", becouse I > though that base system and ports were completely separated and can be > also upgraded separately. Thanks for your reply, -- Laurent Yes -- I'd start with the base system just to confirm everything really is sync. If the message goes away at that point, then that is good news. If everything is in sync, then that pretty much leaves us with a port or package as being the culprit. For example, if you're running an SNMP agent package that polls system state once a second, that could well be the source of the message. What's unfortunate is that whatever program it is is not reporting which program it is that is generating the error, and apparently not logging it via syslog (I assume you checked the system logs to make sure it's not also being sent there -- if not, you might want to). That is definitely a bug, and should be fixed once we find out the culprit. Robert N M Watson