CentOS 5 Crashing regularly, nothing in logs
| I am running CentOS 5.7, it is crashing almost every day and nothing is indicated in the /var/log/messages. It stops responding to ping requests and there is no network traffic to and from it. The system does not present these problems when running in a vm, only when running directly on the hardware. I have run this system on various hardware configurations and it happens only on the hardware systems. I am out of ideas as to what the problem can be. I have googled everything i can think of related to crashing and network problems. Here is the a copy of the entries in the messages /var/log/messages file from one of the incidents: Nov 3 12:26:59 localhost smartd[1984]: Device: /dev/hdb, opened Nov 3 12:27:00 localhost smartd[1984]: Device: /dev/hdb, found in smartd database. Nov 3 12:27:00 localhost smartd[1984]: Device: /dev/hdb, is SMART capable. Adding to "monitor" list. Nov 3 12:27:00 localhost smartd[1984]: Device: /dev/hdd, opened Nov 3 12:27:00 localhost smartd[1984]: Device: /dev/hdd, packet devices [this device CD/DVD] not SMART capable Nov 3 12:27:00 localhost smartd[1984]: Monitoring 1 ATA and 0 SCSI devices Nov 3 12:27:01 localhost smartd[1989]: smartd has fork()ed into background mode. New PID=1989. Nov 3 12:32:41 localhost nmbd[1968]: [2011/11/03 12:32:41, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) Nov 3 12:32:41 localhost nmbd[1968]: ***** Nov 3 12:32:41 localhost nmbd[1968]: Nov 3 12:32:41 localhost nmbd[1968]: Samba name server LOCALHOST is now a local master browser for workgroup MYGROUP on subnet xxx.xx.x.xxx Nov 3 12:32:41 localhost nmbd[1968]: Nov 3 12:32:41 localhost nmbd[1968]: ***** Nov 4 11:55:55 localhost syslogd 1.4.1: restart. Nov 4 11:55:55 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started. Nov 4 11:55:55 localhost kernel: Linux version 2.6.18-274.3.1.el5 (mockbuilder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-51)) #1 SMP Tue Sep 6 20:14:03 EDT 2011 Nov 4 11:55:55 localhost kernel: BIOS-provided physical RAM map: Nov 4 11:55:55 localhost kernel: BIOS-e820: 0000000000010000 - 000000000009fc00 (usable) Nov 4 11:55:55 localhost kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) Nov 4 11:55:55 localhost kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) Nov 4 11:55:55 localhost kernel: BIOS-e820: 0000000000100000 - 000000001dff0000 (usable) Nov 4 11:55:55 localhost kernel: BIOS-e820: 000000001dff0000 - 000000001dff3000 (ACPI NVS) Nov 4 11:55:55 localhost kernel: BIOS-e820: 000000001dff3000 - 000000001e000000 (ACPI data) Nov 4 11:55:55 localhost kernel: BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) Nov 4 11:55:55 localhost kernel: 0MB HIGHMEM available. Nov 4 11:55:55 localhost kernel: 479MB LOWMEM available. Nov 4 11:55:55 localhost kernel: found SMP MP-table at 000f4bc0 Nov 4 11:55:55 localhost kernel: Memory for crash kernel (0x0 to 0x0) notwithin permissible range Nov 4 11:55:55 localhost kernel: disabling kdump Nov 4 11:55:55 localhost kernel: Using x86 segment limits to approximate NX protection Can anyone give advice? |
No comments:
Post a Comment