From owner-freebsd-questions@FreeBSD.ORG Thu Feb 16 15:00:12 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 E77B616A420 for ; Thu, 16 Feb 2006 15:00:12 +0000 (GMT) (envelope-from mike@ascendency.net) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [63.240.77.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7150543D45 for ; Thu, 16 Feb 2006 15:00:12 +0000 (GMT) (envelope-from mike@ascendency.net) Received: from eisenhower.ascendency.net ([67.173.128.145]) by comcast.net (sccrmhc13) with ESMTP id <20060216150005013004g5gke>; Thu, 16 Feb 2006 15:00:06 +0000 Received: from Mike8500 (ipcop.localdomain [192.168.1.1]) (authenticated bits=0) by eisenhower.ascendency.net (8.13.4/8.13.4) with ESMTP id k1GExvmW028265 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 16 Feb 2006 09:00:00 -0600 (CST) (envelope-from mike@ascendency.net) From: "Mike Loiterman" To: Date: Thu, 16 Feb 2006 08:59:57 -0600 Message-ID: <021b01c63309$ab353130$0401a8c0@Mike8500> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Thread-Index: AcYzB3eK1zvJPVaHSGO6Z/K5fLXAhwAAIg4A In-Reply-To: <20060216134355.GA778@Alex1.kruijff.org> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (eisenhower.ascendency.net [192.168.1.22]); Thu, 16 Feb 2006 09:00:04 -0600 (CST) Cc: freebsd-questions@freebsd.org Subject: RE: Mysterious reboot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mike@ascendency.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2006 15:00:13 -0000 Alex de Kruijff wrote: > On Thu, Feb 16, 2006 at 01:46:19AM -0600, Mike Loiterman wrote: >> Afte being up for more than two months, I just noticed that my ver >> reliable and stable server mysteriously rebooted. I've had the same >> hardware and system setup for more than a year and haven't ever >> experienced anything like this before. I haven't added any new >> hardware in a very long time. I did upgrade mysql this morning via >> portupgrade, however. >> >> The system appears to have crashed, as dmesg shows that the various >> filesystems weren't unmounted correctly upon reboot, but aside from >> that single error, nothing else points to what the problem was. >> >> /var/log/messages just shows a user connectig via pop, and then the >> next line is the machine booting. >> >> We are having a pretty good rainstorm, but nothing else seems to >> have lost power and I have several other machines in this space that >> did not go down (servers, TVs, XBOX, laptops, etc). >> >> The machine seems to have gone down around 11:23 PM, so I checked >> /etc/cron to see if I had scheduled a job to be run at that time, >> but there are no jobs scheduled to be run on or near this time. >> >> Where can I begin to look for more clues as to why this machine >> seems to have crashed? Where would a kernel core dump be or a mysql >> core dump? > > You can look at /var/log/messages and find core files with 'find / > -name \*.core' > > I suspect the cause lies with your hardware. There might be something > broken that causes your computer to reboot spontaneous when > it gets busy > or hot and other times it just goes oke. I just ran (/usr/ports/sysutils/stress/) stress -c 2 which floored the CPU for the last five hours, while compiling emacs over and over. No crashes. No problems. CPU load was over 8 at some points. No files found in the search for *.core. I've also been observing my system...even when mail load from these mini-attacks is heaviest, maybe 800 messages a second, the system load barly goes over idle. There appeas to have been two such attacks. It's a 2.8 ghz machine with 3 gigs of RAM, it should be well able to handle that load even for sustained periods of time. The only real explanation was some sort of power fluctuation. I'll continue to monitor it carefully, but there doesn't seem to be anyway to definitivly identify the cause, but the machine crashing under load is looking less and less likely. If there is a problem, I suspect it will show up again within the next week or so, otherwise I'll chalk it up to a random event in the unverse. ------------------------------ Mike Loiterman grantADLER Tel: 630-302-4944 Fax: 773-442-0992 Email: mike@ascendency.net PGP Key: 0xD1B9D18E