From owner-freebsd-questions@FreeBSD.ORG Thu May 1 09:56:27 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB251106564A for ; Thu, 1 May 2008 09:56:27 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from snoogles.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 9C4718FC15 for ; Thu, 1 May 2008 09:56:27 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (localhost [127.0.0.1]) by snoogles.rachie.is-a-geek.net (Postfix) with ESMTP id A7A8B1CC91; Thu, 1 May 2008 01:56:26 -0800 (AKDT) From: Mel To: freebsd-questions@freebsd.org Date: Thu, 1 May 2008 11:56:24 +0200 User-Agent: KMail/1.9.7 References: <000001c8ab69$e2276ed0$6501a8c0@DIMENSION> In-Reply-To: <000001c8ab69$e2276ed0$6501a8c0@DIMENSION> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805011156.25336.fbsd.questions@rachie.is-a-geek.net> Cc: Olivier GARNIER Subject: Re: Nut problem and last message repeated in dmesg X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2008 09:56:27 -0000 On Thursday 01 May 2008 11:01:02 Olivier GARNIER wrote: > > Can anyone tell my how to see the "last message" which is repeated > > hundred > > times? ... > Apr 30 23:16:33 myhost upsmon[1011]: Poll UPS [ellipse@localhost] failed - > Server disconnected > > May 1 08:57:44 myhost upsmon[1011]: Poll UPS [ellipse@localhost] failed - > Data stale > > May 1 08:58:19 myhost last message repeated 7 times It's a bit bad choice of words, better would be "previous message repeated 7 times". So the message that is repeated, is the message directly above it. Sorry, can't help you with NUT, but it looks like server disconnects are not handled correctly and just generate hundreds of messages about stale data, rather then refreshing the data. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.