My system has rebooted

[go3mon]

Hi all, my system have now rebooted.
I found this in syslog.log:
Jan 31 23:47:53 esxhb027 EMS [5203]: ------ EMS Event Notification ------ Value: "UP (1)" for Resource: "/net/interfaces/lan/status/lan3" (Threshold: != " 1")
Jan 31 23:47:53 esxhb027 EMS [5203]: ----- EMS Monitor Restart due to system reboot ----- Title: MIB Monitor Command: /etc/opt/resmon/lbin/lanmond Vendor: Hewlett-Packard Co. Version: A.03.40 To obtain a list of currently monitored resources, execute the following: /opt/resmon/bin/resdata -M 1922569500



I chech network card:
root@esxhb027[/]: netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan3 1500 10.247.110.128 10.247.110.153 145 0 0 0 0
lan1 1500 62.87.13.0 62.87.13.12 10076 0 10271 0 0
lo0 4136 127.0.0.0 127.0.0.1 7636 0 7636 0 0
lan14* 1500 none none 0 0 0 0 0
lan6 1500 10.247.122.0 10.247.122.23 1082 0 1456 0 0
lan5* 1500 none none 0 0 0 0 0
lan4 1500 192.168.1.0 192.168.1.2 3 0 3 0 0


How I can find a crash dump?

[Patrick Wallek · Accepted solution]

The first places to look for what caused a crash:

1) /etc/shutdownlog
2) /var/adm/syslog/OLDsyslog.log
3) Look for crash dump in /var/adm/crash (or whatever the directory is set to in /etc/rc.config.d/crashconf)
4) There may be some cluues in /var/tombstones/ts99

[go3mon]

1) /etc/shutdownlog
2) /var/adm/syslog/OLDsyslog.log
3) Look for crash dump in /var/adm/crash (or whatever the directory is set to in /etc/rc.config.d/crashconf)
4) There may be some cluues in /var/tombstones/ts99



I have only a ts99:
195381 Jan 31 23:45 ts99

[John Payne_2]

Issue a "touch /etc/shutdownlog" so that the file is there for next time.

If the ts99 file has current data in it, (current timestamp, actual chassis codes, not just zeros, that sort of thing) it might be pointing you towards a HW issue. (Do you have a support contract?)

Otherwise, without anything else, you may just have to wait until the next one.

Do you have crashconf enabled in /etc/rc.config.d/crashconf?

Hope it helps
John

[Mridul Shrivastava]

May be u can try checking /var/opt/resmon/log/event.log and check if there are any critical event just before crash ?

If you have MP/GSP access then you can also check the sl/sel logs for any hardware related errors.

[go3mon]

this system is a Vpar, Do I found error log in VFP?

[Mridul Shrivastava]

VFP will give you the current status. If this is vpar, what was the status of the other vpars when this went down.. were they running fine ?
you can check the event.log of other vpars and see if there are any event at the time this vpar paniced.. Normally if a partition panics then there is an entry in event.log of other parition..

[go3mon]

Is not a Vpar problem...other Vpar works fine and have no problem...If I have other problems I open a case on HP support.

[Raj D.]

Pietro,

Check :

# tail -n 10 /etc/shutdownlog

And check if the last reboot entry is there.

# Check /var/adm/syslog/OLDsyslog.log and findout what was happened during reboot occured.

If there is any suddenpower failure , you will not find any reboot/shutdown log in /etc/shutdownlog

Also check any crash in /var/adm/crash/crash.0 .. or /etc/tombstones files for valid timestamp for any hpmc related error.

Once you find the cause of reboot you can go ahead for further debug.

cheers,
Raj.