From owner-freebsd-questions Sun Apr 23 2: 0:24 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id 9DAE537B8E0 for ; Sun, 23 Apr 2000 02:00:19 -0700 (PDT) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id DAA56620; Sun, 23 Apr 2000 03:01:04 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Sun, 23 Apr 2000 03:01:04 -0600 (CST) From: Ryan Thompson To: Kaan XRS Cc: freebsd-questions@freebsd.org Subject: Re: server In-Reply-To: <3902B909.1595FC7F@superonline.com> Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please CC freebsd-questions@freebsd.org when replying Kaan XRS wrote to Ryan Thompson: > Everything is OK in kernel. Hardware: 233MMX 128MB Ram 6.4 gb Hdd. It > doesn`t give any error in /var/log/messages while rebooting. 20 ircd > servers and their services are running on this servers. I haven`t > updated to 4.0 yet but have you received an error like this before? >=20 > Kaan =D6RS When you say "error like this", you must realize that there are many reasons why a kernel will panic and auto-reboot the system... So, YES, I have witnessed machines auto-reboot (personally, only due to hardware malfunctions, or human error, or call panic()'s while testing), but NO, I don't know why your particular configuration is forcing reboots. If there are indeed no errors in /var/log/messages, and you did not see any unusual console messages during "normal" system operation, or right before the reboot (you should have, since the system appears to have been shut down cleanly), then you truly need to try kernel dump debugging. Do read the handbook section on making the most of a crash dump. OTOH, if you can find some shred of evidence (logs) to show us that might suggest to someone of experience WHY your system is exhibiting this behaviour, someone (perhaps myself) can assist you in determining how to correct the underlying problem. Even subjective indicators can help: o Does this happen during times of high load? =09=09is it disk intensive, or CPU intensive? o If you can monitor it, how much memory is free during: o "Normal" operation o Right before the reboot =09A good way to do this is to add a new CRON job that runs =09every minute that pipes the output of vmstat to a log file. =09After a reboot, examine that log file and try to look for =09spikes or dips or anything unusual. =09If that isn't a fine enough measure (i.e., spikes occur =09in << 60 seconds), a perl script that sleep()s for a few =09seconds and pipes `vmstat` to a file might be advantageous.=20 o Other things to watch for are active processes, problem users, etc. -- Ryan Thompson Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies=09http://www.sasknow.com #106-380 3120 8th St=09E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message