Find reason for reboot 2

[TIgerV]

I discovered recently that back in February, my Hipath 4000 was restarted. It wasn't restarted 'nicely'; it appears it just decided to reboot. APC power logs indicate nothing abnormal, but the Hipath Server shows it has only been up x number of days, which used to be over 1300; and is now triple digits.

Is there an AMO I can use to see why it rebooted? Like a last restart and maybe look back through logs?

It's odd- system was running fine and is running fine since.

Tony


--TIger

 

[Moriendi]

It sounds like you're looking at the uptime visible in the portal GUI, so I guess you are HP4K V6, or OS4K V7/V8.

If you are looking at the linux uptime, then it sounds like the whole system rebooted. A telephony (only) restart would not affect that uptime. So for that you'd want the portal logs which will gather all pertinent logs from both processors (if duplex). Also useful would be the HISTA from the RMX. Hista will most likely have wrapped (cyclic file) but the logs are archived into the portal logs anyway. So from the Portal GUI (not the Assistant) you want to download the full logs. It should create a zip for you to download but if the file is too big it may fail to create it, in which case you'll have to poke around the logs manually. Look in /var/log/messages for which ever processor rebooted, you'll probably want one of the archives. You don't say if you have a simplex or duplex, or if one processor reloaded, or both.

 

[sbcsu]

You can also
DIS-SIGNL:SYSTEM;
to see how long each HiPath processor is up.
If using HISTA to see logs and they have overwritten then check the size of the HISTA file
(REG-HISTA
If it is only 2500 then you can increase it by
DEL-HISTA;
ADD-HISTA:10000;
However that will delete any records that were there.