From owner-freebsd-isp  Fri Apr 19  7:14:28 2002
Delivered-To: freebsd-isp@freebsd.org
Received: from smtp1.amigo.net (smtp1.amigo.net [209.94.64.30])
	by hub.freebsd.org (Postfix) with ESMTP id 2C2DF37B400
	for <freebsd-isp@freebsd.org>; Fri, 19 Apr 2002 07:14:24 -0700 (PDT)
Received: from stalker.amigo.net (billing.amigo.net [209.94.67.250])
	by smtp1.amigo.net (8.11.4/8.11.4) with ESMTP id g3JELXB21871;
	Fri, 19 Apr 2002 08:21:33 -0600 (MDT)
	(envelope-from randys@amigo.net)
Date: Fri, 19 Apr 2002 08:14:47 -0600 (MDT)
From: Randy Smith <randys@amigo.net>
X-X-Sender: randy@stalker.amigo.net
To: Andy Farkas <andyf@speednet.com.au>
Cc: freebsd-isp@freebsd.org
Subject: Re: Clarification of kernel log in messages
In-Reply-To: <Pine.BSF.4.33.0204191224330.71410-100000@backup.af.speednet.com.au>
Message-ID: <20020419081023.K2170-100000@stalker.amigo.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isp.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isp>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isp>
X-Loop: FreeBSD.org

Andy,

This machine has been in production for two and a half years. So, I would
be surprised if it is the cable.

-- 
Randy Smith
Amigo.Net Systems Administrator
1-719-589-6100 x 4185
http://www.amigo.net/

On Fri, 19 Apr 2002, Andy Farkas wrote:

> Date: Fri, 19 Apr 2002 12:27:42 +1000 (EST)
> From: Andy Farkas <andyf@speednet.com.au>
> To: Randy Smith <randys@amigo.net>
> Subject: Re: Clarification of kernel log in messages
>
> On Thu, 18 Apr 2002, Randy Smith wrote:
> > > I would feel a bit unconfortable about it. Maybe even a _lot_
> > > unconfortable. It's a should-not-occur situation, and may be
> > > your first inkling of an impending failure. That's me wearing
> > > my 37-years-as-a-mainframe-system-programmer hat, but I think
> > > the situation translates well from one arena to the other.
> >
> > What could cause that, other than impending hardware failure? What can I
> > do to monitor this and/or track down the problem? (Hardware is not my thing,
> > generally.)
> >
> > Thanks for the input.
> >
> > Randy
> >
>
> It *could* be a flaky scsi cable. You never said if this was a new system
> or an established one - if its new, you could just now be seeing cable
> probs...
>
> --
>
>  :{ andyf@speednet.com.au
>
>         Andy Farkas
>     System Administrator
>    Speednet Communications
>  http://www.speednet.com.au/
>
>
>
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message