Hi Angelo,
What is that you are looking for ?
Time at which reboot occurred or the cause of the same?
Time at which it occurred is already pointed out by Mubeen
#last -n (n = 1,2,3 .. to n)
based on the time of reboot (this time is a record of machine start and not
of stop as you may have preferred), look into /var/log/messages for entries
matching the time. It may be indicative of the cause.
Before you jump to power, you must understand that RAM and other peripherals
can also cause such issues. Do you have RAID, and do you monitor that?
#dmidecode --type chassis (or --type system, whichever gives better info
about the make)
|_ since some makes are known to be troublesome.. eg:
edge/supermicro(india)
{not to mistake edge for Dell or IBM brand}
#uname -a
|_ was kernel upgraded? If so, then you may want to check if the system
worked fine earlier i.e. before kernel upgrade. To know how many kernels you
can boot cat grub.conf or menu.lst
Which MTA are you using? --- is it sendmail? If yes, you may (if traffic is
high) need to contemplate migrating to a modular MTA (postfix or
netqmail--'a patched-n-maintained qmail' with Maildir format--to avoid file
locking associated with mbox) for performance that in turn helps system and
its admin.
Also you haven't mentioned if this happens too frequently.
Above three are just considerations. You may get cause of reboot, if
recorded before reboot, in /var/log/messages
That's all that comes to my mind now... Good luck hunting
[Non-text portions of this message have been removed]
