On 7/23/06, Tamouh H. [EMAIL PROTECTED] 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 21)
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 21)
Jul 20 17:45:19 freebsd syslogd: restart
Jul 20 17:45:19 freebsd syslogd: kernel boot file is /boot/kernel/kernel
[EMAIL PROTECTED] /usr/local/apache/logs]# last -n 42
mcuserttyp0ip.ip.ip.ipThu Jul 20 19:07 still logged in
reboot ~ Thu Jul 20 17:45
mcuserttyp0ip.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=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2
AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow
real memory = 1073676288 (1023 MB)
avail memory = 1041735680 (993 MB)
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 Version 1.1 irqs 0-23 on motherboard
ioapic1 Version 1.1 irqs 24-27 on motherboard
ioapic2 Version 1.1 irqs 28-31 on motherboard
kbd1 at kbdmux0
acpi0: A M I OEMRSDT 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: ACPI CPU on acpi0
acpi_throttle0: ACPI CPU Throttling on cpu0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge at device 6.0 on pci0
pci3: ACPI PCI bus on pcib1
ohci0: OHCI (generic) USB controller 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: OHCI (generic) USB controller 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.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
