LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
Reload this Page seeking how to find a fresh boot in the system log files
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
Page 1 of 2 1 2
  Search this Thread
Old 12-21-2018, 12:54 PM   #1
SaintDanBert
Senior Member
 
Registered: Jan 2009
Location: "North Shore" Louisiana USA
Distribution: Mint-20.1 with Cinnamon
Posts: 1,771
Blog Entries: 3

Rep: Reputation: 108Reputation: 108
seeking how to find a fresh boot in the system log files

Consider that a workstation re-boots several times over the course of an hour. A single copy of /var/log/syslog will contain entries for each of these system start events.

Which log file entry always appears as the very first record of a fresh system start?

Is there some way to force the use of a fresh copy of
/var/log/syslog for each system boot?
(I would enable this when working a boot-time issue, then disable for routine running.)

Thanks in advance,
~~~ 0;-Dan
 
Old 12-21-2018, 12:55 PM   #2
pan64
LQ Addict
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 21,840

Rep: Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308
did you try the command last ?
 
1 members found this post helpful.
Old 12-21-2018, 01:11 PM   #3
dc.901
Senior Member
 
Registered: Aug 2018
Location: Atlanta, GA - USA
Distribution: CentOS/RHEL, openSuSE/SLES, Ubuntu
Posts: 1,005

Rep: Reputation: 370Reputation: 370Reputation: 370Reputation: 370
Are you looking for boot log? Which OS? For SuSE and CentOS (RH), there is /var/log/boot.log, and previous boot logs with boot.log-<date> in CentOS.
 
2 members found this post helpful.
Old 12-21-2018, 08:50 PM   #4
frankbell
LQ Guru
Contributing Member
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,323
Blog Entries: 28

Rep: Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141
The next time this happens, after a reboot, you can use tail to check the most recent x number of lines in the log file. https://www.linode.com/docs/quick-an...w-to-use-tail/

I did a short gig with a hosting provider several years ago and that was the technique they recommended in situations like this.
 
1 members found this post helpful.
Old 12-21-2018, 08:55 PM   #5
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,126

Rep: Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120
Code:
journalctl -b 0
 
3 members found this post helpful.
Old 12-21-2018, 09:16 PM   #6
frankbell
LQ Guru
Contributing Member
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,323
Blog Entries: 28

Rep: Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141Reputation: 6141
Thanks, syg00. You taught me something.
 
Old 12-21-2018, 10:07 PM   #7
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,126

Rep: Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120
Happy to help. In the past when I have posted similar it usually resulted in a mindless anti-systemd flamefest.
 
Old 12-22-2018, 02:52 PM   #8
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874
You might check /var/log/kern.log for it's date/time stamp. Not really a test of a reboot, but if it's days old, you probably have NOT rebooted in days old. Or booted to a read-only filesystem where logging would be mostly pointless, or checking them. Something which you could check as a lowly user, versus needing groups like systemd-journal in your permissions, or admin access(root). Or having to resort to a variety of other methods depending on the init system of the week.
 
Old 12-23-2018, 02:00 AM   #9
ehartman
Senior Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 1,674

Rep: Reputation: 888Reputation: 888Reputation: 888Reputation: 888Reputation: 888Reputation: 888Reputation: 888
Quote:
Originally Posted by SaintDanBert View Post
Which log file entry always appears as the very first record of a fresh system start?[/CODE]
None, as the syslog facility isn't active yet. A lot of systems will make a copy of the kernel diagnostic mesgs in a file (in MY system /var/log/dmesg) and that then is the first info about the reboot.
[CODE]Is there some way to force the use of a fresh copy of
/var/log/syslog for each system boot?
That would have to be done in the startup of the syslogd (and klogd) daemons, which is highly distro dependant (and especially on your startup system, like init, runit, upstart or systemd).
Essentially init does it with some kind of startup script, which you would have to modify. I'm always been more of a Unix person so am not familiar with other startup systems.

The whole of logging can only be started after the disks have been checked (for which they're either readonly or unmounted) and optionally have been decrypted (with a LUKS filesystem), so it comes rather late in the bootup sequence.
 
Old 12-26-2018, 05:25 PM   #10
SaintDanBert
Senior Member
 
Registered: Jan 2009
Location: "North Shore" Louisiana USA
Distribution: Mint-20.1 with Cinnamon
Posts: 1,771

Original Poster
Blog Entries: 3

Rep: Reputation: 108Reputation: 108
Quote:
Originally Posted by dc.901 View Post
Are you looking for boot log? Which OS? For SuSE and CentOS (RH), there is /var/log/boot.log, and previous boot logs with boot.log-<date> in CentOS.
I've looked there, but the messages I'm seeing do not appear in /var/log/boot.log.
I'm also looking at dmesg without success.
Is there some way to enhance the contents of this /var/log/boot.log?

The messages blink by so fast, I've no idea which component is reporting.
Can someone tell me how to watch boot on a non-graphical console with CTRL-ALT-F1 or such?

Thanks in advance,
~~~ 0;-Dan
 
Old 12-28-2018, 03:06 AM   #11
pan64
LQ Addict
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 21,840

Rep: Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308
I still do not understand what do you want to achieve.
 
Old 12-28-2018, 12:58 PM   #12
SaintDanBert
Senior Member
 
Registered: Jan 2009
Location: "North Shore" Louisiana USA
Distribution: Mint-20.1 with Cinnamon
Posts: 1,771

Original Poster
Blog Entries: 3

Rep: Reputation: 108Reputation: 108
Quote:
Originally Posted by pan64 View Post
I still do not understand what do you want to achieve.
Over there on disk is /var/log/* with all of its log files and folders.

I shutdown and restart my workstation. During boot, various components write into these log files and folders.
When I look at the contents of these logs, other than a time stamp in the log content, which entry(s) tell me
"A system restart begins here?"

Is there some way that I can cause a log file entry using logger or similar?

Thanks in advance,
~~~ 0;-Dan
 
Old 12-28-2018, 01:19 PM   #13
pan64
LQ Addict
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 21,840

Rep: Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308Reputation: 7308
see post #2. Did you try the command last ?
 
1 members found this post helpful.
Old 12-28-2018, 02:41 PM   #14
Soadyheid
Senior Member
 
Registered: Aug 2010
Location: Near Edinburgh, Scotland
Distribution: Cinnamon Mint 20.1 (Laptop) and 20.2 (Desktop)
Posts: 1,672

Rep: Reputation: 486Reputation: 486Reputation: 486Reputation: 486Reputation: 486
Hi, I'm running Mint 18.3 at present. This is what I get from /var/log/syslog when I did a restart:

Code:
Dec 28 13:26:29 HP-Z400-Workstation kernel: [  543.810423] [UFW BLOCK] IN=enp1s0 OUT= MAC=01:00:5e:00:00:fb:00:d0:b8:1
9:94:51:08:00 SRC=192.168.0.26 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
Dec 28 13:26:46 HP-Z400-Workstation cinnamon-session[2253]: WARNING: t+511.93396s: Playing logout sound '/usr/share/mi
nt-artwork-cinnamon/sounds/logout.ogg'
Dec 28 13:26:46 HP-Z400-Workstation cinnamon-session[2253]: WARNING: t+512.03512s: Finished playing logout sound
Dec 28 13:26:46 HP-Z400-Workstation cinnamon-session[2253]: WARNING: t+512.03516s: Resuming logout sequence...
Dec 28 13:26:47 HP-Z400-Workstation cinnamon-session[2253]: GLib-GIO-CRITICAL: t+512.98112s: g_dbus_connection_call_sy
nc_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Dec 28 13:26:47 HP-Z400-Workstation cinnamon-session[2253]: WARNING: t+512.98130s: Requesting system restart...
Dec 28 13:26:47 HP-Z400-Workstation cinnamon-session[2253]: WARNING: t+512.98165s: Attempting to restart using systemd
...
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopped target Sound Card.
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping User Manager for UID 1000...
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping ACPI event daemon...
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopped target Bluetooth.
Dec 28 13:26:47 HP-Z400-Workstation bluetoothd[1195]: Terminating
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping Bluetooth service...
Dec 28 13:26:47 HP-Z400-Workstation bluetoothd[1195]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/A2DPSour
ce
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks...
Dec 28 13:26:47 HP-Z400-Workstation bluetoothd[1195]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/A2DPSink
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping Console Manager...
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopped target Timers.
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopped Daily apt upgrade and clean activities.
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopped Daily apt download activities.
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopped target System Time Synchronized.
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping Disk Manager...
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping Daemon for power management...
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Dec 28 13:26:47 HP-Z400-Workstation nvidia-persistenced: Received signal 15
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping flatpak system helper...
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping NVIDIA Persistence Daemon...
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopping Save/Restore Sound Card State...
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup.
Dec 28 13:26:47 HP-Z400-Workstation systemd[1]: Stopped target Graphical Interface.
Dec 28 13:26:47 HP-Z400-Workstation rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1130" x-info="http
://www.rsyslog.com"] exiting on signal 15.   <--- SYSTEM STOPPED AT THIS POINT
Dec 28 13:27:55 HP-Z400-Workstation rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1164" x-info="http
://www.rsyslog.com"] start  <--- SYSTEM RESTARTS FROM HERE
Dec 28 13:27:55 HP-Z400-Workstation rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - 
did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Dec 28 13:27:55 HP-Z400-Workstation rsyslogd: rsyslogd's groupid changed to 108
Dec 28 13:27:55 HP-Z400-Workstation rsyslogd: rsyslogd's userid changed to 104
Dec 28 13:27:55 HP-Z400-Workstation systemd-modules-load[420]: Inserted module 'lp'
Dec 28 13:27:55 HP-Z400-Workstation systemd-modules-load[420]: Inserted module 'ppdev'
Dec 28 13:27:55 HP-Z400-Workstation systemd-modules-load[420]: Inserted module 'parport_pc'
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Started Create list of required static device nodes for the current ke
rnel.
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Starting Create Static Device Nodes in /dev...
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Started Apply Kernel Variables.
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] microcode: microcode updated early to revision 0x1d, date =
 2018-05-11
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] Linux version 4.15.0-43-generic (buildd@lcy01-amd64-007) (g
cc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10)) #46~16.04.1-Ubuntu SMP Fri Dec 7 13:31:08 UTC 2018 (Ubuntu 4.15
.0-43.46~16.04.1-generic 4.15.18)
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic ro
ot=UUID=a37d1251-ba0e-42de-81c1-5c62e58f1e38 ro quiet splash vt.handoff=7
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] KERNEL supported cpus:
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   Intel GenuineIntel
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Mounted FUSE Control File System.
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   AMD AuthenticAMD
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   Centaur CentaurHauls
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] x86/fpu: x87 FPU will use FXSAVE
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x00000000000957ff] usab
le
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Mounted Debug File System.
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Mounted POSIX Message Queue File System.
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Mounted Configuration File System.
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Mounted Huge Pages File System.
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BIOS-e820: [mem 0x0000000000095800-0x000000000009ffff] rese
rved
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e8000-0x00000000000fffff] rese
rved
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Started Remount Root and Kernel File Systems.
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000defa57ff] usab
le
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BIOS-e820: [mem 0x00000000defa5800-0x00000000dfffffff] rese
rved
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BIOS-e820: [mem 0x00000000f0000000-0x00000000f3ffffff] rese
rved
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fed3ffff] rese
rved
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Started Create Static Device Nodes in /dev.
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed45000-0x00000000ffffffff] rese
rved
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000041fffffff] usab
le
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] NX (Execute Disable) protection: active
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] SMBIOS 2.6 present.
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Starting udev Kernel Device Manager...
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] DMI: Hewlett-Packard HP Z400 Workstation/0B4Ch, BIOS 786G3 
v03.60 02/24/2016
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserve
d
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Starting Flush Journal to Persistent Storage...
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] e820: last_pfn = 0x420000 max_arch_pfn = 0x400000000
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] MTRR default type: write-back
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] MTRR fixed ranges enabled:
Dec 28 13:27:55 HP-Z400-Workstation rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or direct
ory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   00000-9FFFF write-back
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Starting udev Coldplug all Devices...
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   A0000-BFFFF uncachable
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Starting Load/Save Random Seed...
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   C0000-E7FFF write-protect
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   E8000-EFFFF write-back
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   F0000-FFFFF write-protect
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] MTRR variable ranges enabled:
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   0 base 0E0000000 mask FE0000000 uncachable
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   1 base 420000000 mask FE0000000 uncachable
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Started LVM2 metadata daemon.
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   2 disabled
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   3 disabled
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   4 disabled
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   5 disabled
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Started Load/Save Random Seed.
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   6 disabled
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000]   7 disabled
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Started Flush Journal to Persistent Storage.
Dec 28 13:27:55 HP-Z400-Workstation rsyslogd-2007: action 'action 10' suspended, next retry is Fri Dec 28 13:28:25 201
8 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- W
T  
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] e820: last_pfn = 0xdefa5 max_arch_pfn = 0x400000000
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] found SMP MP-table at [mem 0x000f9bf0-0x000f9bff] mapped at
 [        (ptrval)]
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] Scanning 1 areas for low memory corruption
Dec 28 13:27:55 HP-Z400-Workstation loadkeys[419]: Loading /etc/console-setup/cached.kmap.gz
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] Base memory trampoline at [        (ptrval)] 8f000 size 245
76
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Started Set console keymap.
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BRK [0x33b93f000, 0x33b93ffff] PGTABLE
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BRK [0x33b940000, 0x33b940fff] PGTABLE
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BRK [0x33b941000, 0x33b941fff] PGTABLE
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BRK [0x33b942000, 0x33b942fff] PGTABLE
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BRK [0x33b943000, 0x33b943fff] PGTABLE
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BRK [0x33b944000, 0x33b944fff] PGTABLE
Dec 28 13:27:55 HP-Z400-Workstation systemd[1]: Started udev Coldplug all Devices.
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BRK [0x33b945000, 0x33b945fff] PGTABLE
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BRK [0x33b946000, 0x33b946fff] PGTABLE
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] BRK [0x33b947000, 0x33b947fff] PGTABLE
Dec 28 13:27:55 HP-Z400-Workstation kernel: [    0.000000] RAMDISK: [mem 0x314d2000-0x34a60fff]

... Loadsmore startup messages...
Nope! I don't profess to know what it all means. If you had a crash and a restart and want to see if you can find out what happened I'd be inclined to trawl through the syslog file to see when the timestamp changes and the reboot starts. (Note there are really only two timestamps mentioned in my file section above; 13:26:47 and 13:27:55) In a crash, the messages prior to the restart are the interesting ones which may highlight the problem (Assuming you can decode what they're trying to tell you!)
Note that my reboot messages appear at some random point within the syslog file.

No idea if that'll be of any assistance to you but good luck!

Play Bonny!
 
Old 12-28-2018, 02:52 PM   #15
scasey
LQ Veteran
 
Registered: Feb 2013
Location: Tucson, AZ, USA
Distribution: CentOS 7.9.2009
Posts: 5,727

Rep: Reputation: 2211Reputation: 2211Reputation: 2211Reputation: 2211Reputation: 2211Reputation: 2211Reputation: 2211Reputation: 2211Reputation: 2211Reputation: 2211Reputation: 2211
As pan64 has said a couple of times,
Code:
last | more
gives me
Code:
scasey   pts/3        ip<connecting IP>. Sun Dec 16 17:53 - 23:10  (05:16)    
scaseywe pts/2        ip<connecting IP>. Sun Dec 16 13:31 - 23:10  (09:38)    
scasey   pts/2        ip<connecting IP>. Fri Dec  7 08:25 - 11:31  (03:05)    
scasey   pts/2        ip<connecting IP>. Wed Dec  5 14:30 - 15:07  (00:37)    
root     pts/2        ip<connecting IP>. Wed Dec  5 12:25 - 12:26  (00:00)    
root     pts/1        ip<connecting IP>. Sun Dec  2 08:46   still logged in   
root     pts/0        ip<connecting IP>. Sun Dec  2 08:45   still logged in   
reboot   system boot  3.10.0-862.14.4. Sun Dec  2 08:45 - 13:44 (26+04:59)  
root     pts/0        ip<connecting IP>. Wed Nov 21 13:54 - 23:33  (09:39)    
root     pts/0        ip<connecting IP>. Wed Nov 21 13:47 - 13:50  (00:02)    
scasey   pts/2        ip<connecting IP>. Wed Nov 21 10:58 - 12:43 (5+01:44)   
scasey   pts/2        ip<connecting IP>. Mon Nov 19 09:16 - 12:11 (1+02:54)   
root     pts/1        ip<connecting IP>. Sun Nov 18 14:43 - 13:44 (2+23:00)   
root     pts/0        ip<connecting IP>. Sun Nov 18 14:42 - 13:44 (2+23:01)   
root     pts/1        ip<connecting IP>. Sat Nov 17 22:31 - 14:36  (16:05)    
root     pts/0        ip<connecting IP>. Sat Nov 17 21:25 - 14:36  (17:11)    
reboot   system boot  3.10.0-862.14.4. Sat Nov 17 21:19 - 20:19 (13+23:00)
where I've highlighted the last two boots of the server.
Is that not what you're asking?
 
  


Reply
Page 1 of 2 1 2



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
How to log internal-sftp chroot jailed users access log to /var/log/sftp.log file LittleMaster Linux - Server 0 09-04-2018 03:45 PM
[SOLVED] Won't boot: /etc/rc.d/init.d/rc: line 193: /var/log/boot.log: Read-only file system liquidkaleidoscopes Linux From Scratch 6 11-11-2011 08:53 PM
Multi-disk, multi-boot system does not boot after fresh install anth0ny5 Linux - Software 8 08-17-2011 02:02 AM
[SOLVED] /var/log/boot.log is empty in RHEL5.5. How to enable the boot log? rajivdp Linux - Newbie 1 08-12-2010 08:11 AM
fresh install (fresh headache) powadha Slackware 2 03-06-2004 01:03 PM

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

All times are GMT -5. The time now is 05:18 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
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
Open Source Consulting | Domain Registration