ESX 3.5 automatically reboot on HP ProLiant DL380

[paolorealcomm]

Hi,

i'm new to vmware.

I have a HP ProLiant server DL 380 G5 with ESX 3.5 and 4 virtual server. I have installed thi server 2 week ago.

during two night the ESX server has beenautomatically reboot (at about 6:15 am) whit apparently no reasons.

How can I do to check why the server was rebooted?

Thanks

[jayolsen]

If you have the HP agents installed with system management homepage running you can go to and logon and check the logs tab. Look at the integrated logs from there.

[depping]

You might want to login to the console and check /var/log/messages. Or connect with the vCenter Client to the host directly and check the events tab, or click ädministration and the system log. Click the pulldown for the various log files. Messages will probably give you a hint,

Duncan

Blogging: http://www.yellow-bricks.com

If you find this information useful, please award points for "correct" or "helpful".

[paolorealcomm]

i have read /var/log/messages but i can't understand...

Feb 5 11:15:00 hostname vmware-hostd[1795]: Accepted password for user root from 127.0.0.1

Feb 5 19:42:40 hostname vmware-hostd[1795]: Accepted password for user root from 127.0.0.1

Feb 6 04:29:17 hostname ntpd[1674]: synchronisation lost

Feb 6 06:15:21 hostname syslogd 1.4.1: restart.

Feb 6 06:15:22 hostname syslog: syslogd startup succeeded

Feb 6 06:15:22 hostname kernel: klogd 1.4.1, log source = /proc/kmsg started.

Feb 6 06:15:22 hostname kernel: Linux version 2.4.21-57.ELvmnix (mts@pa-lin-bld401.eng.vmware.com) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-14)) #1 Wed Oct 15 19:00:05 PDT 2008[VMnix version 123630]

Feb 6 06:15:22 hostname kernel: BIOS-provided physical RAM map:

Feb 6 06:15:22 hostname kernel: BIOS-e820: 0000000000000000 - 000000000009f400 (usable)

Feb 6 06:15:22 hostname kernel: BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)

Feb 6 06:15:22 hostname kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)

Feb 6 06:15:22 hostname kernel: BIOS-e820: 0000000000100000 - 00000000cfe54000 (usable)

Feb 6 06:15:22 hostname kernel: BIOS-e820: 00000000cfe54000 - 00000000cfe5c000 (ACPI data)

Feb 6 06:15:22 hostname kernel: BIOS-e820: 00000000cfe5c000 - 00000000cfe5d000 (usable)

Feb 6 06:15:22 hostname kernel: BIOS-e820: 00000000cfe5d000 - 00000000d0000000 (reserved)

Feb 6 06:15:22 hostname kernel: BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)

Feb 6 06:15:22 hostname kernel: BIOS-e820: 00000000fec00000 - 00000000fed00000 (reserved)

Feb 6 06:15:22 hostname syslog: klogd startup succeeded

...

...

...

[Lightbulb]

If the HP management agents are installed you may want to disable ASR.

In some cases ASR feature will shut down the system when the issues does not warrant it. Also with ASR enabled you will not get a chance to determine the status of the problem by checking console etc. The down side to this is your system will possibly remain hung in a nonfunctional state until you can manually power cycle. So it is a trade off.

Type rpm -qa | grep hp this should show you which HP components are installed.

Type hplog -v to get a listing of ASRs (If that in fact is what is occurring)

You can disable ASR by typing hplog -a DISABLE

Also if HP agents are installed check /var/spool/compaq/cma.log for errors.

Message was edited by: Lightbulb Highlighting

[paolorealcomm]

Thanks for the answer, but i don't have HP management installed on my server

[avlieshout]

Are there any coredumps on /var/core or /root/old_cores ?

Also check /var/log/vmkernel and /var/log/vmkwarning

ASR is no HP feature, but is a BIOS feature. If It is set to disable the server will not automatically reboot whenever is gets a PSOD.

Arnim van Lieshout

Visit my blog at:

[jayolsen]

You could try running memtest to make sure the memory is good and not causing an issue, if you can take the downtime that is.

[depping]

Looking at the messages there's nothing related to the restart, well it says it has been restarted but no reason. could you post the vmkernel log and the vmkwarning?

Duncan

Blogging: http://www.yellow-bricks.com

If you find this information useful, please award points for "correct" or "helpful".

[benma]

As mentioned above try to disable ASR in your BIOS.

I had this problem with a 3.02 Host on a DL360

[paolorealcomm]

i have now disabled ASR...