HP-UX 11.31

[HP-UX 11.31]

Hi,

We have HP-UX 11.31 itanium servers (rx6600 and rx2660).
How can I check if server reboots/shutdown due to power failure?

Thanks,
Ranjeet

[Torsten.]

Check the shutdown logfile in /etc and compare with "uptime".

[Suraj K Sankari]

hi,

Check /etc/shutdownlog and /var/adm/syslog/syslog.log

Suraj

[Sharma Sanjeev]

Hi

Check /etc/shutdownlog or /var/adm/syslog/syslog.log or /etc/rc.log old

Regards
Sanjeev

[Johnson Punniyalingam]

Hi ,

You can check

# last |grep reboot
# uptime
# more /etc/shutdownlog

Check the Syslog,

cat /var/adm/syslog/syslog.log

Thanks,
Johnson

[Sajjad Sahir]

Dear Ranjeet

uptime is the command, if u want to see why it is see the log files.

cd /var/adm/syslog

tail -10 syslog.log

thanks and regards

Sajjad Sahir

[Dennis Handly]

If you don't have an UPS to perform a graceful shutdown, you won't find an entry in /etc/shutdownlog.
As others mentioned, you can look at uptime, last or /etc/rc.log.

[Gokul Chandola · Accepted solution]

Hi,
Check /etc/shutdownlog or /var/adm/syslog/syslog.log
and /var/adm/syslog/OLDsyslog.log

You will find there "REBOOT" like following..

$ cat OLDsyslog.log
Mar 15 22:03:43 HOSTNAME syslogd: restart
Mar 15 22:03:43 HOSTNAME vmunix: Found adjacent data tr. Growing size. 0x33de000
-> 0x73de000.
Mar 15 22:03:43 HOSTNAME vmunix: Pinned PDK malloc pool: base: 0xe000000100c22000
size=118648K
Mar 15 22:03:43 HOSTNAME vmunix: Loaded ACPI revision 2.0 tables.
Mar 15 22:03:43 HOSTNAME vmunix: MMIO on this platform supports Write Coalescing.

Regards,
Gokul Chandola

[Sunny Jaisinghani]

Check event logs under /var/opt/resmon/log for power supply related alerts.

You may also have a look at console logs

[Torsten.]

You can also check if there are related MP logs.

If you have UPS software installed, you should find related messages in

/var/adm/syslog/OLDsyslog.log

Without a UPS, the server will just go off without any messages. You will only find information about the last boot then.

[點燃]

Check these two files

etc/shutdownlog and /var/adm/syslog/syslog.log

Also the OLDsyslog.log file.

[HP-UX 11.31]

Hi,
Thank you all for your reply.

I found below text from OLDsyslog.log file but still unable to find the root cause for reboot.

Mar 17 22:01:43 docdev syslog: --- Successful Save Sets ---
Mar 17 22:01:43 docdev syslog: * doccont.eil.co.in:Probe savefs doccont.eil.co.in: succeeded.
Mar 17 22:01:43 docdev syslog: doccont.eil.co.in: /var level=incr, 44 MB 00:00:59 233 files
Mar 17 22:01:43 docdev syslog: doccont.eil.co.in: /usr level=incr, 0 KB 00:00:59 0 files
Mar 17 22:01:43 docdev syslog:
Mar 17 22:01:43 docdev above message repeats 2 times
Mar 17 22:01:43 docdev syslog: docdev.eil.co.in: index:doccont.eil.co.in level=9, 36 KB 00:00:42 4 files
Mar 17 22:01:43 docdev syslog:
Mar 17 22:07:38 docdev sshd[26560]: SSH: Server;Ltype: Kex;Remote: 10.10.1.163-26420;Enc: aes256-ctr;MAC: hmac-sha1;Comp: none
Mar 17 22:09:25 docdev sshd[13969]: SSH: Server;Ltype: Kex;Remote: 10.10.26.121-1032;Enc: aes256-ctr;MAC: hmac-sha1;Comp: none
Mar 17 22:09:36 docdev sshd[14027]: SSH: Server;Ltype: Kex;Remote: 10.10.26.121-1033;Enc: aes256-ctr;MAC: hmac-sha1;Comp: none
Mar 17 22:09:47 docdev sshd[14043]: SSH: Server;Ltype: Kex;Remote: 10.10.26.121-1035;Enc: aes256-ctr;MAC: hmac-sha1;Comp: none
Mar 17 22:17:17 docdev vmunix:
Mar 17 22:17:17 docdev vmunix: Shutting down machine, please wait.
Mar 17 22:17:17 docdev syslogd: going down on signal 15

[Duncan Edmonstone]

Ranjeet,

Well I'd be very suspicious of this:

Mar 17 21:48:53 docdev /usr/sbin/envd[1574]: ***** OVERTEMP_CRIT WARNING *****
Mar 17 21:48:53 docdev /usr/sbin/envd[1574]: Temperature exceeded the normal operation threshold. Correct the over-temperature condition.


Looks like the server is too hot - is this in a proper machine room? You might find more info in the system event logs on the Management Processor. Log in to the MP and enter:

SL

to look at the event logs, followed by E for the current logs...

HTH

Duncan

[Ganesan R]

Hi,

You can also the console logs. Log into GSP/MP and view the logs

[Torsten.]

This is exactly the reason:

Mar 17 21:48:53 docdev /usr/sbin/envd[1574]: ***** OVERTEMP_CRIT WARNING *****


If the temperature is much too high, the system will do a "reboot -qh", if still too high, it will power off to prevent damage.

You will find related messages in the MP logs.