Solaris shutdown and boot history

UNIX for Advanced & Expert Users
1

Hello.

I'm trying to get a Solaris (SunOS 5.10) shutdown and boot history. Unfortunately the /var/adm/wtmpx file does not cover the period I want to trace. It's been reset. Therefore the command, "last" (or "last reboot") does not reach back far enough.

Additionally the /var/adm/messages* files do not show any reboot information and I know the system was rebooted several times over the weekend.

Is there anywhere else I can grep to find this history? Right how all I have is "who -b" for the last reboot timestamp. This is a Solaris 10 server running Oracle 11g, so the only chink of light I can see, is examining the Oracle server alert logs.

Thanks.
Patrick/

2

You do not see anything like this in /var/adm/messages?

Sep 28 10:20:09 mysystem genunix: [ID 540533 kern.notice] ^MSunOS Release 5.10 Version Generic_142900-13 64-bit
Sep 28 10:20:09 mysystem genunix: [ID 683174 kern.notice] Copyright 1983-2010 Sun Microsystems, Inc.  All rights reserved.
Sep 28 10:20:09 mysystem Use is subject to license terms.
Sep 28 10:20:09 mysystem genunix: [ID 678236 kern.info] Ethernet address = aa:bb:cc:dd:ee:ff

This set of lines is the start of a system.

HTH

3

Nope...

 % grep 'Sun Microsystems' messages*
messages.0:Dec 29 11:01:40 au10qap0y0tels2 genunix: [ID 943907 kern.notice] Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
messages.0:Dec 29 14:11:04 au10qap0y0tels2 genunix: [ID 943907 kern.notice] Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.

..and it's definitely been rebooted since last December...

% who -b
   .       system boot  Sep 25 04:18
% ls -l mess*
-rw-r--r--   1 root     root     7465001 Oct  4 14:35 messages
-rw-r--r--   1 root     root       57734 Dec 29  2007 messages.0

:confused:

Very weird!

4

Maybe you are lucky with the cron log in /var/cron/log. You can find records like

! SIGTERM Tue Apr 27 15:35:01 2010
! ******* CRON ABORTED ******** Tue Apr 27 15:35:01 2010
! *** cron started ***   pid = 267 Tue Apr 27 15:38:56 2010

there, which is usually caused by a reboot.

5

Try executing "logadm" and this will roll your messages file. Read /etc/logadm.conf to see if you have anything setup to log messages.
I also suggest to insert a logadm entry in your crontab for root.