LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 08-27-2018, 08:13 AM   #1
Rosika
Member
 
Registered: Apr 2017
Distribution: Lubuntu 64 bit
Posts: 253

Rep: Reputation: Disabled
incorrect reboot-logs?


Hi altogether;

Iīve recently taken a look at my reboot-logs with last -x | grep reboot .
Code:
reboot   system boot  4.4.0-134-generi Mon Aug 27 12:36   still running
reboot   system boot  4.4.0-134-generi Sun Aug 26 12:18   still running
reboot   system boot  4.4.0-134-generi Sat Aug 25 13:22   still running
reboot   system boot  4.4.0-133-generi Sat Aug 25 12:56 - 13:21  (00:25)
reboot   system boot  4.4.0-133-generi Thu Aug 23 12:40 - 13:21 (2+00:41)
reboot   system boot  4.4.0-133-generi Wed Aug 22 12:46 - 19:04  (06:17)
reboot   system boot  4.4.0-133-generi Tue Aug 21 11:37 - 18:48  (07:11)
reboot   system boot  4.4.0-133-generi Mon Aug 20 12:43 - 18:48 (1+06:05)
reboot   system boot  4.4.0-133-generi Sun Aug 19 12:02 - 18:48 (2+06:46)
reboot   system boot  4.4.0-133-generi Sat Aug 18 11:54 - 19:02  (07:08)
reboot   system boot  4.4.0-133-generi Fri Aug 17 12:23 - 18:35  (06:12)
reboot   system boot  4.4.0-133-generi Thu Aug 16 18:27 - 19:03  (00:35)
reboot   system boot  4.4.0-133-generi Thu Aug 16 12:28 - 19:03  (06:34)
reboot   system boot  4.4.0-133-generi Wed Aug 15 13:37 - 19:06  (05:29)
reboot   system boot  4.4.0-131-generi Wed Aug 15 14:51 - 19:06  (04:15)
reboot   system boot  4.4.0-131-generi Tue Aug 14 12:33 - 19:06 (1+06:33)
reboot   system boot  4.4.0-131-generi Mon Aug 13 11:40 - 19:06 (2+07:26)
reboot   system boot  4.4.0-131-generi Sun Aug 12 13:14 - 19:06 (3+05:52)
reboot   system boot  4.4.0-131-generi Sun Aug 12 14:26 - 13:13  (-1:-12)
reboot   system boot  4.4.0-131-generi Sat Aug 11 12:55 - 14:31  (01:35)
reboot   system boot  4.4.0-131-generi Thu Aug  9 16:30 - 19:05  (02:35)
reboot   system boot  4.4.0-131-generi Thu Aug  9 12:31 - 16:12  (03:40)
reboot   system boot  4.4.0-131-generi Wed Aug  8 15:29 - 19:03  (03:34)
reboot   system boot  4.4.0-131-generi Wed Aug  8 13:15 - 19:03  (05:48)
reboot   system boot  4.4.0-131-generi Mon Aug  6 13:03 - 19:05  (06:02)
reboot   system boot  4.4.0-131-generi Sun Aug  5 12:29 - 18:25  (05:55)
reboot   system boot  4.4.0-131-generi Sat Aug  4 13:52 - 19:07  (05:15)
reboot   system boot  4.4.0-131-generi Sat Aug  4 13:42 - 13:51  (00:08)
reboot   system boot  4.4.0-131-generi Sat Aug  4 11:38 - 11:44  (00:05)
reboot   system boot  4.4.0-131-generi Fri Aug  3 17:43 - 11:44  (18:00)
reboot   system boot  4.4.0-131-generi Fri Aug  3 17:30 - 11:44  (18:14)
reboot   system boot  4.4.0-131-generi Fri Aug  3 12:34 - 11:44  (23:09)
reboot   system boot  4.4.0-131-generi Thu Aug  2 17:05 - 18:51  (01:46)
reboot   system boot  4.4.0-131-generi Thu Aug  2 16:23 - 17:05  (00:41)
reboot   system boot  4.4.0-131-generi Thu Aug  2 12:19 - 16:22  (04:03)
Here it occurred to me that the first entry is correct. Well, my system is running right now, so thatīs o.k.

Yet the following two entries make no sense at all. Yesterday (Sun Aug 26) and the day before (Sat Aug 25) it shut down my computer as I always do.
A normal clean shutdown. Despite that fact thereīs the entry "still running".
But not so with all the other preceding entries.

And last -x | grep shutdown shows me the following:
Code:
shutdown system down  4.4.0-133-generi Sat Aug 25 13:21 - 13:22  (00:00)
shutdown system down  4.4.0-133-generi Wed Aug 22 19:04 - 12:40  (17:35)
shutdown system down  4.4.0-133-generi Tue Aug 21 18:48 - 12:46  (17:57)
shutdown system down  4.4.0-133-generi Sat Aug 18 19:02 - 12:02  (16:59)
shutdown system down  4.4.0-133-generi Fri Aug 17 18:35 - 11:54  (17:18)
shutdown system down  4.4.0-133-generi Thu Aug 16 19:03 - 12:23  (17:19)
shutdown system down  4.4.0-133-generi Wed Aug 15 19:06 - 12:28  (17:21)
shutdown system down  4.4.0-131-generi Sun Aug 12 13:13 - 13:14  (00:00)
shutdown system down  4.4.0-131-generi Sat Aug 11 14:31 - 14:26  (23:54)
shutdown system down  4.4.0-131-generi Thu Aug  9 19:05 - 12:55 (1+17:50)
shutdown system down  4.4.0-131-generi Thu Aug  9 16:12 - 16:30  (00:17)
shutdown system down  4.4.0-131-generi Wed Aug  8 19:03 - 12:31  (17:27)
shutdown system down  4.4.0-131-generi Mon Aug  6 19:05 - 13:15 (1+18:09)
shutdown system down  4.4.0-131-generi Sun Aug  5 18:25 - 13:03  (18:38)
shutdown system down  4.4.0-131-generi Sat Aug  4 19:07 - 12:29  (17:21)
shutdown system down  4.4.0-131-generi Sat Aug  4 13:51 - 13:52  (00:00)
shutdown system down  4.4.0-131-generi Sat Aug  4 11:44 - 13:42  (01:58)
shutdown system down  4.4.0-131-generi Thu Aug  2 18:51 - 12:34  (17:42)
shutdown system down  4.4.0-131-generi Thu Aug  2 17:05 - 17:05  (00:00)
shutdown system down  4.4.0-131-generi Thu Aug  2 16:22 - 16:23  (00:00)
Itīs odd that yesterdayīs shutdown (Sun Aug 26) doesnīt show up at all. And again: I performed a normal shutdown.

Does anybody know whatīs going on here?

Tnx a lot in advance.

Greetings
Rosika

P.S.:
my system: Lubuntu 16.04.5 LTS, 64 bit

Last edited by Rosika; 08-27-2018 at 10:38 AM.
 
Old 08-28-2018, 06:03 AM   #2
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 10,714

Rep: Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189
Taking a single line like that isn't very informative.

I would point you at August 25; the 'shutdown' & 'reboot' entries occur at 13:22 - like they're part of the same process.You check the logs before Aug 25 to see if it's a pattern.
 
Old 08-28-2018, 06:39 AM   #3
Rosika
Member
 
Registered: Apr 2017
Distribution: Lubuntu 64 bit
Posts: 253

Original Poster
Rep: Reputation: Disabled
Hi business_kid,

tnx for your answer.
Quote:
You check the logs before Aug 25 to see if it's a pattern.
Well, as you can see the logs before Aug 25 seem to be o.k.

I also checked today:
Code:
last -x | grep reboot
reboot   system boot  4.4.0-134-generi Tue Aug 28 12:20   still running
reboot   system boot  4.4.0-134-generi Mon Aug 27 14:57   still running
reboot   system boot  4.4.0-134-generi Mon Aug 27 12:36   still running
reboot   system boot  4.4.0-134-generi Sun Aug 26 12:18   still running
reboot   system boot  4.4.0-134-generi Sat Aug 25 13:22   still running
reboot   system boot  4.4.0-133-generi Sat Aug 25 12:56 - 13:21  (00:25)
reboot   system boot  4.4.0-133-generi Thu Aug 23 12:40 - 13:21 (2+00:41)
One entry more that says "still running" (yesterdayīs entry). Thatīs the only pattern I can see.
What strikes me as odd is the fact that this phenomenon can be seen since the point in time when I updated the system from kernel 4.4.0-133 to 4.4.0-134 .....

Also:
Code:
last -x | grep shutdown
shutdown system down  4.4.0-133-generi Sat Aug 25 13:21 - 13:22  (00:00)
shutdown system down  4.4.0-133-generi Wed Aug 22 19:04 - 12:40  (17:35)
shutdown system down  4.4.0-133-generi Tue Aug 21 18:48 - 12:46  (17:57)
no new entry since the new kernel
 
Old 08-28-2018, 07:12 AM   #4
pan64
LQ Guru
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 13,299

Rep: Reputation: 4212Reputation: 4212Reputation: 4212Reputation: 4212Reputation: 4212Reputation: 4212Reputation: 4212Reputation: 4212Reputation: 4212Reputation: 4212Reputation: 4212
last -x | grep -E '(reboot)|(shutdown)'
probably would be better
 
Old 08-28-2018, 07:23 AM   #5
Rosika
Member
 
Registered: Apr 2017
Distribution: Lubuntu 64 bit
Posts: 253

Original Poster
Rep: Reputation: Disabled
Hi pan64,

Well, I did what you suggested:
Code:
rosika@rosika-Lenovo-H520e ~> last -x | grep -E '(reboot)|(shutdown)'
reboot   system boot  4.4.0-134-generi Tue Aug 28 13:12   still running
reboot   system boot  4.4.0-134-generi Tue Aug 28 12:20   still running
reboot   system boot  4.4.0-134-generi Mon Aug 27 14:57   still running
reboot   system boot  4.4.0-134-generi Mon Aug 27 12:36   still running
reboot   system boot  4.4.0-134-generi Sun Aug 26 12:18   still running
reboot   system boot  4.4.0-134-generi Sat Aug 25 13:22   still running
shutdown system down  4.4.0-133-generi Sat Aug 25 13:21 - 13:22  (00:00)
reboot   system boot  4.4.0-133-generi Sat Aug 25 12:56 - 13:21  (00:25)
reboot   system boot  4.4.0-133-generi Thu Aug 23 12:40 - 13:21 (2+00:41)
shutdown system down  4.4.0-133-generi Wed Aug 22 19:04 - 12:40  (17:35)
reboot   system boot  4.4.0-133-generi Wed Aug 22 12:46 - 19:04  (06:17)
shutdown system down  4.4.0-133-generi Tue Aug 21 18:48 - 12:46  (17:57)
reboot   system boot  4.4.0-133-generi Tue Aug 21 11:37 - 18:48  (07:11)
reboot   system boot  4.4.0-133-generi Mon Aug 20 12:43 - 18:48 (1+06:05)
reboot   system boot  4.4.0-133-generi Sun Aug 19 12:02 - 18:48 (2+06:46)
shutdown system down  4.4.0-133-generi Sat Aug 18 19:02 - 12:02  (16:59)
reboot   system boot  4.4.0-133-generi Sat Aug 18 11:54 - 19:02  (07:08)
shutdown system down  4.4.0-133-generi Fri Aug 17 18:35 - 11:54  (17:18)
reboot   system boot  4.4.0-133-generi Fri Aug 17 12:23 - 18:35  (06:12)
shutdown system down  4.4.0-133-generi Thu Aug 16 19:03 - 12:23  (17:19)
reboot   system boot  4.4.0-133-generi Thu Aug 16 18:27 - 19:03  (00:35)
reboot   system boot  4.4.0-133-generi Thu Aug 16 12:28 - 19:03  (06:34)
shutdown system down  4.4.0-133-generi Wed Aug 15 19:06 - 12:28  (17:21)
reboot   system boot  4.4.0-133-generi Wed Aug 15 13:37 - 19:06  (05:29)
reboot   system boot  4.4.0-131-generi Wed Aug 15 14:51 - 19:06  (04:15)
reboot   system boot  4.4.0-131-generi Tue Aug 14 12:33 - 19:06 (1+06:33)
reboot   system boot  4.4.0-131-generi Mon Aug 13 11:40 - 19:06 (2+07:26)
reboot   system boot  4.4.0-131-generi Sun Aug 12 13:14 - 19:06 (3+05:52)
shutdown system down  4.4.0-131-generi Sun Aug 12 13:13 - 13:14  (00:00)
reboot   system boot  4.4.0-131-generi Sun Aug 12 14:26 - 13:13  (-1:-12)
shutdown system down  4.4.0-131-generi Sat Aug 11 14:31 - 14:26  (23:54)
reboot   system boot  4.4.0-131-generi Sat Aug 11 12:55 - 14:31  (01:35)
shutdown system down  4.4.0-131-generi Thu Aug  9 19:05 - 12:55 (1+17:50)
reboot   system boot  4.4.0-131-generi Thu Aug  9 16:30 - 19:05  (02:35)
shutdown system down  4.4.0-131-generi Thu Aug  9 16:12 - 16:30  (00:17)
reboot   system boot  4.4.0-131-generi Thu Aug  9 12:31 - 16:12  (03:40)
shutdown system down  4.4.0-131-generi Wed Aug  8 19:03 - 12:31  (17:27)
reboot   system boot  4.4.0-131-generi Wed Aug  8 15:29 - 19:03  (03:34)
reboot   system boot  4.4.0-131-generi Wed Aug  8 13:15 - 19:03  (05:48)
shutdown system down  4.4.0-131-generi Mon Aug  6 19:05 - 13:15 (1+18:09)
reboot   system boot  4.4.0-131-generi Mon Aug  6 13:03 - 19:05  (06:02)
shutdown system down  4.4.0-131-generi Sun Aug  5 18:25 - 13:03  (18:38)
reboot   system boot  4.4.0-131-generi Sun Aug  5 12:29 - 18:25  (05:55)
shutdown system down  4.4.0-131-generi Sat Aug  4 19:07 - 12:29  (17:21)
reboot   system boot  4.4.0-131-generi Sat Aug  4 13:52 - 19:07  (05:15)
shutdown system down  4.4.0-131-generi Sat Aug  4 13:51 - 13:52  (00:00)
reboot   system boot  4.4.0-131-generi Sat Aug  4 13:42 - 13:51  (00:08)
shutdown system down  4.4.0-131-generi Sat Aug  4 11:44 - 13:42  (01:58)
reboot   system boot  4.4.0-131-generi Sat Aug  4 11:38 - 11:44  (00:05)
reboot   system boot  4.4.0-131-generi Fri Aug  3 17:43 - 11:44  (18:00)
reboot   system boot  4.4.0-131-generi Fri Aug  3 17:30 - 11:44  (18:14)
reboot   system boot  4.4.0-131-generi Fri Aug  3 12:34 - 11:44  (23:09)
shutdown system down  4.4.0-131-generi Thu Aug  2 18:51 - 12:34  (17:42)
reboot   system boot  4.4.0-131-generi Thu Aug  2 17:05 - 18:51  (01:46)
shutdown system down  4.4.0-131-generi Thu Aug  2 17:05 - 17:05  (00:00)
reboot   system boot  4.4.0-131-generi Thu Aug  2 16:23 - 17:05  (00:41)
shutdown system down  4.4.0-131-generi Thu Aug  2 16:22 - 16:23  (00:00)
reboot   system boot  4.4.0-131-generi Thu Aug  2 12:19 - 16:22  (04:03)
I still think itīs odd that only after the installation of the new kernel the persistent "still running"-message occurs.
 
Old 08-28-2018, 07:25 AM   #6
Rosika
Member
 
Registered: Apr 2017
Distribution: Lubuntu 64 bit
Posts: 253

Original Poster
Rep: Reputation: Disabled
Plus: Why arenīt there any more "shutdown entries" lately?
 
Old 08-28-2018, 07:46 AM   #7
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19.1 MATE
Posts: 8,018
Blog Entries: 5

Rep: Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869
See here: https://unix.stackexchange.com/quest...-still-running

From the reply (my highlighting):

Quote:
Yes, it would be the expected result. last doesn’t know that your system was shut down on December 16, presumably because it wasn’t an orderly shut down (power loss or something like that). Because of the way it displays boots, it considers that the last two boots are still running.

Things will sort themselves out to some extent the next time the system is shut down; last will then use the new shut down time for both December 7 and 16 boots.
Let us know if that is what you experience.

I found the thread in question by searching for "last -x" multiple "still running" - there are quite a few hits.
 
Old 08-28-2018, 08:11 AM   #8
Rosika
Member
 
Registered: Apr 2017
Distribution: Lubuntu 64 bit
Posts: 253

Original Poster
Rep: Reputation: Disabled
Hi hydrurga,

tnx for your suggestion and the link.

Quote:
[...] presumably because it wasn’t an orderly shut down (power loss or something like that).
That might be a nice enough explanation but it doesnīt apply here.
I always perform an orderly shutdown, there wasnīt a power loss or anything like that.

I even performed a shutdown via terminal with
Code:
shutdown -h now
(just in case ....)

But the results remain the same. Next time I look at the logs thereīs one entry more with "still running" together with "reboot". And never a "shutdown" entry any more.

Iīm at my witīs end.
 
Old 08-28-2018, 08:23 AM   #9
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19.1 MATE
Posts: 8,018
Blog Entries: 5

Rep: Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869
Why are you at your wits end for something that doesn't affect the operation of your computer? If you search for that string I mentioned before, you will see that others have commented that the last command does this sometimes.

Experiment. Try shutting down using different methods e.g. GUI shutdown/reboot rather than command line if you're running X. See how the different methods affect the output from that command.

It could well be that shutdown -h now is too quick for the computer - there could be processes running in the background that don't have time to shut down cleanly. Try the softest, highest-level shutdown that you can. Then try the softest, highest-level reboot that you can find. Then try shutting down all key background processes before a shutdown to see if you can determine a process that is not behaving correctly and not shutting down cleanly.
 
Old 08-28-2018, 08:47 AM   #10
Rosika
Member
 
Registered: Apr 2017
Distribution: Lubuntu 64 bit
Posts: 253

Original Poster
Rep: Reputation: Disabled
Hi hydrurga,

Quote:
Try shutting down using different methods e.g. GUI shutdown/reboot rather than command line if you're running X.
Well, normally I use the GUI shutdown-method. It was just now that I tried the command line in order to find out whether this changes anything.
So I tried out two methods of shutting down/rebooting.

I also looked at the entries with zcat /var/log/syslog.[2-7].gz | grep -i shutdown and zcat /var/log/syslog.[2-7].gz | grep -i reboot in order to see if thereīs anything unusual to see (especially with reference to the "Aug 25"-border when the last "shutdown"-entry can be seen:
Code:
Aug 27 12:36:45 rosika-Lenovo-H520e systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Aug 27 12:36:45 rosika-Lenovo-H520e systemd[1]: Started Update UTMP about System Boot/Shutdown.
Aug 27 12:38:19 rosika-Lenovo-H520e systemd[1773]: Reached target Shutdown.
Aug 25 13:21:33 rosika-Lenovo-H520e systemd[2520]: Reached target Shutdown.
Aug 25 13:22:50 rosika-Lenovo-H520e systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Aug 25 13:22:50 rosika-Lenovo-H520e systemd[1]: Started Update UTMP about System Boot/Shutdown.
Aug 25 13:24:24 rosika-Lenovo-H520e systemd[1973]: Reached target Shutdown.
Aug 25 18:59:50 rosika-Lenovo-H520e systemd[5389]: Reached target Shutdown.
Aug 26 12:19:17 rosika-Lenovo-H520e systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Aug 26 12:19:17 rosika-Lenovo-H520e systemd[1]: Started Update UTMP about System Boot/Shutdown.
Aug 26 12:20:41 rosika-Lenovo-H520e systemd[1782]: Reached target Shutdown.
Aug 23 18:20:23 rosika-Lenovo-H520e systemd[2546]: Reached target Shutdown.
Aug 25 12:56:36 rosika-Lenovo-H520e systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Aug 25 12:56:36 rosika-Lenovo-H520e systemd[1]: Started Update UTMP about System Boot/Shutdown.
Aug 25 12:57:49 rosika-Lenovo-H520e systemd[1776]: Reached target Shutdown.
Aug 23 12:40:29 rosika-Lenovo-H520e systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Aug 23 12:40:29 rosika-Lenovo-H520e systemd[1]: Started Update UTMP about System Boot/Shutdown.
Aug 23 12:43:49 rosika-Lenovo-H520e systemd[1802]: Reached target Shutdown.
Aug 22 12:46:35 rosika-Lenovo-H520e systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Aug 22 12:46:35 rosika-Lenovo-H520e systemd[1]: Started Update UTMP about System Boot/Shutdown.
Aug 22 12:47:59 rosika-Lenovo-H520e systemd[1782]: Reached target Shutdown.
Aug 20 19:09:45 rosika-Lenovo-H520e systemd[2539]: Reached target Shutdown.
Aug 21 11:37:46 rosika-Lenovo-H520e systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Aug 21 11:37:46 rosika-Lenovo-H520e systemd[1]: Started Update UTMP about System Boot/Shutdown.
Aug 21 11:39:25 rosika-Lenovo-H520e systemd[1791]: Reached target Shutdown.

&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&


Aug 27 12:36:45 rosika-Lenovo-H520e cron[1363]: (CRON) INFO (Running @reboot jobs)
Aug 25 13:22:50 rosika-Lenovo-H520e cron[1471]: (CRON) INFO (Running @reboot jobs)
Aug 26 12:19:17 rosika-Lenovo-H520e cron[1370]: (CRON) INFO (Running @reboot jobs)
Aug 25 12:56:36 rosika-Lenovo-H520e cron[1403]: (CRON) INFO (Running @reboot jobs)
Aug 23 12:40:29 rosika-Lenovo-H520e cron[1359]: (CRON) INFO (Running @reboot jobs)
Aug 22 12:46:38 rosika-Lenovo-H520e cron[1458]: (CRON) INFO (Running @reboot jobs)
Aug 21 11:37:49 rosika-Lenovo-H520e cron[1422]: (CRON) INFO (Running @reboot jobs)
Yet I canīt find anything unusual.

Quote:
Then try shutting down all key background processes before a shutdown to see if you can determine a process that is not behaving correctly and not shutting down cleanly
This seems a good idea but Iīm not quite sure how to go about doing that.
 
Old 08-28-2018, 09:05 AM   #11
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19.1 MATE
Posts: 8,018
Blog Entries: 5

Rep: Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869
Here's another page, found through wtmp database user reboot that indicates that this can occur if the system changes the time during a session:

https://unix.stackexchange.com/quest...ppeared-twice#

If you look at the original output that you provided, you will see that there a number of occurrences where several reboot logins end at the same time e.g. Wed Aug 15 19:06 (5 reboot logins ended) - these were probably all marked as "still running" until the event that finally closed them.

Worth considering the time-change possibility anyway.
 
Old 08-28-2018, 09:07 AM   #12
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19.1 MATE
Posts: 8,018
Blog Entries: 5

Rep: Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869
Why is the output from your zcat not in strict descending chronological order?
 
Old 08-28-2018, 09:31 AM   #13
Rosika
Member
 
Registered: Apr 2017
Distribution: Lubuntu 64 bit
Posts: 253

Original Poster
Rep: Reputation: Disabled
Hi hydrurga,

tnx for all the effort of yours.
As far as time-change is concerned I can say that it was Aug 15 that this last happened.

I have got a dual-boot system working here (WIN 8.1 and Lubuntu). I last used Windows on Aug 14 for update purposes and booted into Lubuntu only the following day.
Every time I switch from Windows to Lubuntu the clock is 2 hours fast. After internet-connection is established the time is set right again.

But that was, as I said, on Aug 15. And the last "shutdown"-entry was on Aug 25......

Quote:
Why is the output from your zcat not in strict descending chronological order?
I have no idea. I entered the commands as described.
 
Old 08-28-2018, 09:55 AM   #14
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 19.1 MATE
Posts: 8,018
Blog Entries: 5

Rep: Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869Reputation: 2869
The hardware clock may still be set incorrectly.

It might be worth setting both Windows to local or UTC (see https://askubuntu.com/questions/8009...-to-windows-10) and seeing if that resolves the problem.

Also, the battery on your hardware clock, if you have one, may be dead or dying (or perhaps the connection is flaky). You might consider replacing it.
 
Old 08-29-2018, 07:55 AM   #15
Rosika
Member
 
Registered: Apr 2017
Distribution: Lubuntu 64 bit
Posts: 253

Original Poster
Rep: Reputation: Disabled
*****UPDATE*****

Hi again.

Iīm glad to tell that I somehow could get things straight again. But I really donīt know how exactly it worked out.

What I did yesterday was the following:

1.) I booted up WIN. I had a vague feeling that it could have something to do with it......
I realized that the boot process look longer that ususal.

2.) It seemed that a reboot was pending as I got a message from avira (third party software, antivirus) which
told me to reboot. That I did.

3.) After a reboot I used WIN for a while and in the evening I performed a normal shutdown.

4.) The next day (today) I booted up Lubuntu and saw (last -x | grep -E '(reboot)|(shutdown)') that
nothing has changed. Well, I thought, that was to be expected.

5.) So I performed a normal shutdown and the booted up Lubuntu again.
Here are the results:
Code:
last -x | grep -E '(reboot)|(shutdown)'
reboot   system boot  4.4.0-134-generi Wed Aug 29 14:34   still running
shutdown system down  4.4.0-134-generi Wed Aug 29 12:33 - 14:34  (02:01)
reboot   system boot  4.4.0-134-generi Wed Aug 29 14:25 - 12:33  (-1:-51)
reboot   system boot  4.4.0-134-generi Tue Aug 28 13:56 - 12:33  (22:37)
reboot   system boot  4.4.0-134-generi Tue Aug 28 13:12 - 12:33  (23:21)
reboot   system boot  4.4.0-134-generi Tue Aug 28 12:20 - 12:33 (1+00:13)
reboot   system boot  4.4.0-134-generi Mon Aug 27 14:57 - 12:33 (1+21:36)
reboot   system boot  4.4.0-134-generi Mon Aug 27 12:36 - 12:33 (1+23:57)
reboot   system boot  4.4.0-134-generi Sun Aug 26 12:18 - 12:33 (3+00:15)
reboot   system boot  4.4.0-134-generi Sat Aug 25 13:22 - 12:33 (3+23:11)
shutdown system down  4.4.0-133-generi Sat Aug 25 13:21 - 13:22  (00:00)
reboot   system boot  4.4.0-133-generi Sat Aug 25 12:56 - 13:21  (00:25)
reboot   system boot  4.4.0-133-generi Thu Aug 23 12:40 - 13:21 (2+00:41)
shutdown system down  4.4.0-133-generi Wed Aug 22 19:04 - 12:40  (17:35)
reboot   system boot  4.4.0-133-generi Wed Aug 22 12:46 - 19:04  (06:17)
shutdown system down  4.4.0-133-generi Tue Aug 21 18:48 - 12:46  (17:57)
reboot   system boot  4.4.0-133-generi Tue Aug 21 11:37 - 18:48  (07:11)
[...]
As can be seen there is a shutdown entry this time and only one still running entry.
Iīm so delighted.

I really donīt know whether all this really had something to do with WIN and the fact that there was a reboot pending. After all it was just a wild guess.
But somehow it worked out and the Lubuntu logs display the entries as would be expected.

Thanks hydrurga, pan64 and business_kid for all your help.

Greetings
Rosika
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
CentOS 6, server failed to reboot with incorrect entry in /etc/fstab babybear Linux - Newbie 1 08-19-2016 08:25 PM
Back up logs file and create a script showing the backed up logs and the running logs Billy_6052 Programming 5 12-13-2014 03:32 AM
Freeware tool for capture logs if server automatic reboot deepak_message Linux - Server 4 08-17-2013 07:55 AM
[FYI] "last -f <old wtmp> -x reboot shutdown" incorrect for last reboot and shutdown catkin Linux - General 1 03-26-2010 12:52 AM
Shutdown and Reboot Logs annielovesquestions Linux - Newbie 1 07-04-2005 05:13 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 09:28 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration