find out what time server reboot

[kholikt]

Hi,

In which log I can find out what time my server was reboot. I know that uptime can show the uptime but is there anyway I can find the exact time entry in the log somewhere

[Ranjith P B]

Hi Kholikit,

/etc/shutdownlog file. or
use
#who -b
it gives the last booting time.

Cheers,
Ranjith

[kholikt]

I see lot of errors in my syslog was suspect the reboot is it due to the following

Dec 18 18:21:50 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.0.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190794 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.0.0 -n 124190747 -a
Dec 18 18:21:51 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.0.1" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190798 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.0.1 -n 124190748 -a
Dec 18 18:21:51 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.0.2" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190802 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.0.2 -n 124190749 -a
Dec 18 18:21:51 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.0.3" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190806 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.0.3 -n 124190750 -a
Dec 18 18:21:52 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.0.4" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190810 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.0.4 -n 124190751 -a
Dec 18 18:21:52 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.0.5" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190814 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.0.5 -n 124190752 -a
Dec 18 18:21:52 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.0.6" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190818 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.0.6 -n 124190753 -a
Dec 18 18:21:53 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.0.7" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190822 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.0.7 -n 124190754 -a
Dec 18 18:21:53 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.1.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190826 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.1.0 -n 124190755 -a
Dec 18 18:21:53 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.1.1" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190830 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.1.1 -n 124190756 -a
Dec 18 18:21:54 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.1.2" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190834 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.1.2 -n 124190757 -a
Dec 18 18:21:54 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.1.3" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190838 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.1.3 -n 124190758 -a
Dec 18 18:21:54 myserver EMS [1895]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_10_0_0.10.19.0.0.1.4" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 124190842 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.1.4 -n 124190759 -a

[Fabian Briseño]

Hello.
It looks like a disk array failed?. con you confirm, did the server reboot correctly ?. Run an ioscan to see if this disk are in NO_HW state.

[Ranjith P B]

Hello,
Execute
#/opt/resmon/bin/resdata -R 124190842 -r /storage/events/disks/default/0_10_0_0.10.19.0.0.1.4 -n 124190759 -a
it seems to be some disk problem.
Does ioscan -fn shows no_hw.?

[Mark Nieuwboer]

Hi kholikt,

If it's not a planned shutdown look in the /var/adm/crash.

grtz. Mark

[Peter Godron]

Hi,
/etc/shutdownlog
will show when the server was shut down, but for crashes there will be no time-stamps.

So it depends on how your server shut down.

For further logs, you could check:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1047077

[Yogeeraj_1]

hi,

first of all verify that there is no hardware failures.

You may consult the root mail account on the server itself for more information generated by the EMS.


THE GSP log will also give you some more information.

please check.

kind regards
yogeeraj

[Mridul Shrivastava]

Hi,

syslog contains entry after server was rebooted and If you want to find out last time when server was rebooted, have a look on OLDsyslog.log.....

So I can assure that server has not rebooted after the error messages in syslog.log been logged....

[Mridul Shrivastava]

If you need to know more about these EMS errors please update the /var/opt/resmon/log/event.log ....
This will have more detailed description of these events so we can investigate further...

[Mariusz Grabowski_2]

simply check 'uptime' - you'll see for how long the os is up ;)

[Patrick Wallek]

You can also do a 'who -r' and this will show the exact time the server came back up.

[Simon Hargrave]

# last reboot

this will also show you all instances of reboots. One entry for the pseudo user reboot is added to the wtmp file every time a server is rebooted, so you will be able to see if you've had multiple reboots for example.

[Arturo Galbiati]

Hi,
/etc/shutdownlog

HTH,
Art

[George Liu_4]

last|grep boot

[siva0123]

Hey
i just found out that the who -b and who -r is not the one to be believed when they are used alone , may be u can use them together with uptime to know that.

This is the o/p from my machine and obviuosly it shows dec 20 but it is not showing me the year ...

root@test:/ -: who -b
. system boot Dec 20 12:29
root@test:/ -: uptime
2:37pm up 367 days, 2:08, 2 users, load average: 0.22, 0.18, 0.21

root@test:/ -: who -r
. run-level 3 Dec 20 12:29 3 0 S


Thanks,
Siva

[siva0123]

For that matter u cannot rely on last reboot and last | grep boot too.

They are not reporting the year.

The best option should be cat /etc/shutdownlog

or use the above commands lat reboot or who -b or who -r , whatever it is together with uptime to know the exact boot time


Thanks,
Siva

[Geoff Wild]

Actually, it's

last |grep reboot

Rgds...Geoff

[Raj D.]

Kho;ilt,

1. # cat /etc/shutdownlog
2. # last | grep reboot
3. If the server failed due to any sudden power failure etc, there will not be any log in the log file(shutdownlog).

hth,
Raj.

[Raj D.]

Kholiklt,

1. # cat /etc/shutdownlog
2. # last | grep reboot
3. If the server failed due to any sudden power failure etc, there will not be any log in the log file(shutdownlog).

hth,
Raj.

[Raj D.]

Kholiklt,

1. # cat /etc/shutdownlog
2. # last | grep reboot
3. If the server reboted due to any sudden power failure etc, there will not be any log in the log file(shutdownlog).

hth,
Raj.

[Sp4admin]

Hello,

you can check a couple of places.

check /etc/shutdownlog
check /var/adm/crash ** see its the server
check who -b ** the should show a time

sp,