From owner-freebsd-questions@FreeBSD.ORG Sun Jul 23 11:44:17 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 453A916A4DA for ; Sun, 23 Jul 2006 11:44:17 +0000 (UTC) (envelope-from freebsd.ph@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7581643D46 for ; Sun, 23 Jul 2006 11:44:16 +0000 (GMT) (envelope-from freebsd.ph@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so1969400uge for ; Sun, 23 Jul 2006 04:44:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=sv7uUGUzGoj/ozDf+iKYxY3Ll07D9CyZEBhJu/FP//9AGH5bL3e8yoPc8hVMc+qs0n1E+7i+Dno++wtYKSV6SwLuwYvAkfVapK5BISKDBEPGyrRTyEke1zOHgLr+IZZCE6ybUoXYAL/qQ6Yz/R5Y+sB5bn68q/3XZzMZEIx2TM0= Received: by 10.78.117.10 with SMTP id p10mr1098882huc; Sun, 23 Jul 2006 04:44:15 -0700 (PDT) Received: by 10.78.141.18 with HTTP; Sun, 23 Jul 2006 04:44:15 -0700 (PDT) Message-ID: Date: Sun, 23 Jul 2006 19:44:15 +0800 From: "jan gestre" To: "Tamouh H." In-Reply-To: <20060723022733.6DB1943D4C@mx1.FreeBSD.org> MIME-Version: 1.0 References: <20060723022733.6DB1943D4C@mx1.FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Questions Subject: Re: strange reboot on FreeBSD 6.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 11:44:17 -0000 On 7/23/06, Tamouh H. wrote: > > > Hello, > > I have a machine that I've been monitoring for strange reboots. The > machine is hardly ever used, in fact it sits idle 99.9% of the time. When > a hardware failure occurs, does FreeBSD still records 'reboot' in the last > command ? > > All the sudden at no specific intervals, the machine reboots. No user > logins, no access, nothing triggers it. Just a reboot. This is what > /var/log/all.log says: > > Jul 20 17:35:00 freebsd /usr/sbin/cron[27682]: (root) CMD > (/usr/libexec/atrun) > Jul 20 17:35:00 freebsd /usr/sbin/cron[27683]: (root) CMD > (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1) > Jul 20 17:35:02 freebsd kernel: arplookup 66.249.129.65 failed: host is > not on local network > Jul 20 17:35:02 freebsd last message repeated 4 times > Jul 20 17:40:00 freebsd /usr/sbin/cron[27697]: (root) CMD > (/usr/libexec/atrun) > Jul 20 17:40:00 freebsd /usr/sbin/cron[27698]: (root) CMD > (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1) > Jul 20 17:45:19 freebsd syslogd: restart > Jul 20 17:45:19 freebsd syslogd: kernel boot file is /boot/kernel/kernel > > [root@freebsd /usr/local/apache/logs]# last -n 42 > mcuser ttyp0 ip.ip.ip.ip Thu Jul 20 19:07 still logged in > reboot ~ Thu Jul 20 17:45 > mcuser ttyp0 ip.ip.ip.ip Sat Jul 15 18:27 - 19:22 (00:55) > > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Opteron(tm) Processor 146 (1992.34-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 > > Features=0x78bfbff > AMD Features=0xe0500800 > real memory = 1073676288 (1023 MB) > avail memory = 1041735680 (993 MB) > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-27 on motherboard > ioapic2 irqs 28-31 on motherboard > kbd1 at kbdmux0 > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 > cpu0: on acpi0 > acpi_throttle0: on cpu0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 6.0 on pci0 > pci3: on pcib1 > ohci0: mem 0xfeafc000-0xfeafcfff irq 19 at > device 0.0 on pci3 > ohci0: [GIANT-LOCKED] > usb0: OHCI version 1.0, legacy support > usb0: SMM does not respond, resetting > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 3 ports with 3 removable, self powered > > i have experienced this thing myself in my old debian box, apparently bad hardware(power supply, deteriorating motherboard and fluctuating electric voltage) are causing one way or another this reboot with no user intervention. this frequent reboot you're experiencing are indications that your box will soon become a paperweight. as for what you can do, you can transfer your drive to another box with the same bios configuration, it should work and you should also backup the contents of that box.