From owner-freebsd-questions@FreeBSD.ORG Thu Oct 14 04:10:13 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 324F216A4CE for ; Thu, 14 Oct 2004 04:10:13 +0000 (GMT) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2A5B43D48 for ; Thu, 14 Oct 2004 04:10:10 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from [69.27.131.0] ([69.27.131.0]) by ns1.tiadon.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 13 Oct 2004 23:11:48 -0500 Message-ID: <416DFC1F.5090407@daleco.biz> Date: Wed, 13 Oct 2004 23:10:07 -0500 From: "Kevin D. Kinsey, DaleCo, S.P." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040712 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <9627EEB2-1D75-11D9-8BCD-000D9333E43C@secure-computing.net> <20041014001836.GA45271@xor.obsecurity.org> In-Reply-To: <20041014001836.GA45271@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Oct 2004 04:11:49.0201 (UTC) FILETIME=[ED495C10:01C4B1A3] cc: Eric Crist cc: FreeBSD Questions Subject: Re: Daily reboots... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2004 04:10:13 -0000 Kris Kennaway wrote: >On Wed, Oct 13, 2004 at 07:11:25PM -0500, Eric Crist wrote: > > >>Hello all, >> >>I don't know why, but my system keeps restarting at about 14:00 or >>14:30 every day. Really starting to p!ss me off. Any ideas what could >>be causing this, or how I could find it? >> >> > >Could be internal (e.g. cron job doing something special) or external >(e.g. something else causing a massive drain on the power line at the >time, dropping the voltage supplied to your system) factors. > > I've also experienced this due to CPU overheating; but it wasn't in the afternoon. An early morning cron job doing backups via tar and scp over a network caused the CPU (which had a dying fan) to overheat and the system shut down as a result, as near as we could tell in post-mortem. BIOS was apparently set to allow it to restart, and loads during the workday never peaked enough to tax the CPU as much as the nightly backup. Something of an interesting detective case (for us). Kevin Kinsey