How to View Linux System Reboot Date and Time

by SathiyaMoorthy on October 7, 2011

Question: From the uptime command, I know how many days and hours the system is up and running. Is there a easy way to view the exact date and time on when the system was last rebooted? i.e Exactly from what date and time the system has been up and running?

Answer: Uptime does give this information indirectly. In the following example, it indicates that the system has been up and running for “137 days, 6 hours and 13 minutes”. But, you can’t quickly calculate the exact reboot date and time from this.

$ uptime
 20:52:01 up 137 days,  6:13,  1 user,  load average: 0.00, 0.00, 0.00

Instead of saying the system has been up and running for the last “137 days, 6 hours and 13 minutes”, wouldn’t be nice if it says the system has been running since “Sat May 14 20:38″ (or something like that)? That is exactly what any one of the following three method does.

1. Last command

Use the ‘last reboot’ command, which will display all the previous reboot date and time for the system. This picks the information from the /var/log/wtmp file.

$ last reboot
reboot   system boot  2.6.32-100.28.5. Sat May 14 20:38 - 23:55 (137+06:16)
reboot   system boot  2.6.32-100.28.5. Sun Apr 24 21:28 - 23:37 (15+09:08)  

wtmp begins Thu Sun 24 17:28:47 2011

2. Who command

Use the ‘who -b’ command which displays the last system reboot date and time.

$ who -b
system boot  2011-05-14 20:38

3. Use the perl code snippet

If you insist on using the uptime output to calculate the last reboot time, you can do it manually, or use the following perl code-snippet.

uptime | \
perl -ne '/.*up +(?:(\d+) days?,? +)?(\d+):(\d+),.*/; $total=((($1*24+$2)*60+$3)*60);
$now=time(); $now-=$total; $now=localtime($now); print $now,"\n";'

In this example, the above code-snippet displayed the following output:

Sat May 14 20:38:39 2011

I don’t remember exactly from where I got the above perl code-snippet. But, that didn’t stop me from trying to figure out what it does. Let us take this opportunity to learn little perl. This is what the above perl code-snippet does:

  • -n is perl command line option. Causes the perl program to loop over the input
  • -e is perl command line option. Indicates that it is a perl one liner ( i.e perl will not expect a file name, something like “perl filename.pl”).

Following are the Regex used, and its explanations:

  • .*up + – Match anything until the string “up” and one or more space, for matching the following from uptime output.
  • (?:(\d+) days?,? +) – Single group
  • (?:(\d+) days?,? +)? – Question mark followed by this group says that this group is optional

This part says, if there is a days part in uptime output, capture it, or ignore. The following breaks down the above group in detail.

  • (?:pattern) – Non capturing parenthesis which is used to group, but don’t capture the matched to memory which is $1, $2 etc ..
  • (\d+) – Match one or more digit and put it into $1 (because this is the first group)
  • SPACE days? – Match the literal space followed by day or days
  • ,? – comma is optional
  • SPACE+ – one or more spaces

The following breaks down this pattern (\d+):(\d+),.*/

  • (\d+) – Capture the hour part into $2
  • : – Followed by colon
  • (\d+) – Capture the minute part into $3
  • , – Match comma
  • .* – Match everything else

Following are the rest of the time function in the above perl code-snippet.

  • $total=((($1*24+$2)*60+$3)*60) – Calculate the total amount of seconds the system is UP. i.e (((days*24+hours)*60+minutes)*60 which gives the seconds (like an epoch calculation)
  • $now=time(); – Get the current time in seconds ( epoch time )
  • $now-=$total; – Subtract total system running time from current time. So this is getting the exact time in second when the system was started
  • $now=localtime($now); – Convert the epoch time ( time in seconds ). localtime returns given epoch time in human readable format
  • print $now,”\n” – Finally, this prints the time.

Linux Sysadmin Course Linux provides several powerful administrative tools and utilities which will help you to manage your systems effectively. If you don’t know what these tools are and how to use them, you could be spending lot of time trying to perform even the basic administrative tasks. The focus of this course is to help you understand system administration tools, which will help you to become an effective Linux system administrator.
Get the Linux Sysadmin Course Now!

If you enjoyed this article, you might also like..

  1. 50 Linux Sysadmin Tutorials
  2. 50 Most Frequently Used Linux Commands (With Examples)
  3. Top 25 Best Linux Performance Monitoring and Debugging Tools
  4. Mommy, I found it! – 15 Practical Linux Find Command Examples
  5. Linux 101 Hacks 2nd Edition eBook Linux 101 Hacks Book

Bash 101 Hacks Book Sed and Awk 101 Hacks Book Nagios Core 3 Book Vim 101 Hacks Book

{ 9 comments… read them below or add one }

1 jalal hajigholamali October 7, 2011 at 3:27 am

Hi,

Very nice article, thanks a lot

2 Sachin October 7, 2011 at 3:40 am

Very good Artical

3 madAndroid October 7, 2011 at 4:46 am

Dude!! awesome article, thanks very much :) )

4 harish chndra October 7, 2011 at 8:47 am

thanks a lot for this scenario.

5 fred October 7, 2011 at 9:15 am

Hi,

Note that if your system is running for a long time the reboot time may not be present in the /var/log/wtmp* file (on my default debian lenny, it only keeps one rotation), so the last cpommand may not work.

You can also use the logs (dmesg file) and their access time with the stat command as follow:
stat /var/log/dmesg | grep Modify

6 Donald Russell October 9, 2011 at 9:16 pm

To see when the last reboot was, I have a lastboot function which uses the date command to calculate the date x seconds ago, where x is from the uptime.

/bin/date -d”$(awk ‘{print $1,”seconds ago”;}’ /proc/uptime)”

7 Phani October 10, 2011 at 4:42 am

Nice Article Thank you.

8 Pratk November 12, 2011 at 7:52 am

Hi,
Its very knowledgeablearticle.. Along with mentioned method, we can check the system reboot from sar logs of the system.

-Pratik.

9 chakri October 6, 2013 at 2:22 pm

Hi,

better if this article stuffed like why reboot happened …..

Leave a Comment

Previous post:

Next post: