From owner-freebsd-isp@FreeBSD.ORG Wed Aug 25 12:12:11 2004 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F14616A4CE for ; Wed, 25 Aug 2004 12:12:11 +0000 (GMT) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB43C43D5D for ; Wed, 25 Aug 2004 12:12:10 +0000 (GMT) (envelope-from Barbish3@adelphia.net) Received: from barbish ([67.20.101.71]) by mta11.adelphia.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP id <20040825121210.NWVG404.mta11.adelphia.net@barbish>; Wed, 25 Aug 2004 08:12:10 -0400 From: "JJB" To: =?iso-8859-1?Q?Carlos_Alarc=F3n?= , Date: Wed, 25 Aug 2004 08:12:09 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: <000701c48a55$c9303710$95150c0a@CARLOSXP> Importance: Normal cc: FreeBSD-isp@freebsd.org Subject: RE: Where i can check a log about the last reboot time of my freebsd box X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Barbish3@adelphia.net List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Aug 2004 12:12:11 -0000 owner-freebsd-isp@freebsd.org wrote: > Hi, im having troubles with a freebsd box, suddenly this fbox reboots > many times on a day, every hour at least, :(, i dont know what could > be happening, this fbox was working great, i'd like to know if a log > on the system could helpme to check if a program or process is making > some bad things.. > With this box i share internet to many clients.. am worried :(. > thanks in advance. > > Carlos Alarcón > A normal running system that suddenly starts rebooting its self is more that likely an overheating problem caused by a thick layer of dust on the motherboard chips or early signs of a failing power supply. You will not find any log error messages about this.