Results 1 to 7 of 7

Thread: Incomplete journalctl log after system upgrade and reboot

  1. #1

    Default Incomplete journalctl log after system upgrade and reboot

    log starts with:
    Code:
    Apr 19 15:03:27 lin systemd[1]: Started User Manager for UID 1000.
    Apr 19 15:03:27 lin systemd[3819]: Startup finished in 95ms.
    Apr 19 15:03:27 lin systemd[3819]: Reached target Default.
    Apr 19 15:03:27 lin systemd[3819]: Reached target Basic System.
    Apr 19 15:03:27 lin systemd[3819]: Reached target Sockets.
    Apr 19 15:03:27 lin systemd[3819]: Listening on D-Bus User Message Bus Socket.
    Apr 19 15:03:27 lin systemd[3819]: Listening on Sound System.
    Apr 19 15:03:27 lin systemd[3819]: Reached target Timers.
    Apr 19 15:03:27 lin systemd[3819]: Starting D-Bus User Message Bus Socket.
    Apr 19 15:03:27 lin gdm-password][3275]: pam_unix(gdm-password:session): session opened for user hh by (uid=0)
    Apr 19 15:03:27 lin systemd[3819]: Listening on Multimedia System.
    Apr 19 15:03:27 lin kernel: rfkill: input handler enabled
    Apr 19 15:03:27 lin systemd[3819]: Reached target Paths.
    Apr 19 15:03:27 lin systemd[3819]: pam_unix(systemd-user:session): session opened for user hh by (uid=0)
    Apr 19 15:03:27 lin systemd[1]: Starting User Manager for UID 1000...
    Apr 19 15:03:27 lin systemd[1]: Started User Runtime Directory /run/user/1000.
    Apr 19 15:03:27 lin systemd-logind[1093]: New session 1 of user hh.
    Apr 19 15:03:27 lin systemd[1]: Starting User Runtime Directory /run/user/1000...
    Apr 19 15:03:27 lin systemd[1]: Created slice User Slice of UID 1000.
    Apr 19 15:03:26 lin gdm-password][3275]: gkr-pam: unable to locate daemon control file
    Apr 19 15:03:22 lin systemd[1]: Started One time sync configured by YaST.
    Apr 19 15:03:22 lin yast-timesync[3140]: 2021-04-19T13:03:22Z chronyd exiting
    Apr 19 15:03:22 lin yast-timesync[3140]: 2021-04-19T11:03:22Z System clock wrong by 7199.958484 seconds (step)
    Is it please possible to have a complete log ? (on next reboot for example)

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,285
    Blog Entries
    15

    Default Re: Incomplete journalctl log after system upgrade and reboot

    Hi
    What does journalctl -b show? Might need to check your CMOS battery, or sync chrony time with the hardware clock, what does timedatectl show?
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3

    Default Re: Incomplete journalctl log after system upgrade and reboot

    Quote Originally Posted by malcolmlewis View Post
    Hi
    What does journalctl -b show?
    Hi, it looks correctly - complete (I can post here log if needed)


    Code:
    timedatectl
          Local time: Mon 2021-04-19 17:00:50 CEST
      Universal time: Mon 2021-04-19 15:00:50 UTC
            RTC time: Mon 2021-04-19 15:00:50
           Time zone: xxxxxxxx
     Network time on: no
    NTP synchronized: no
     RTC in local TZ: yes
    
    Warning: The system is configured to read the RTC time in the local time zone.
             This mode can not be fully supported. It will create various problems
             with time zone changes and daylight saving time adjustments. The RTC
             time is never updated, it relies on external facilities to maintain it.
             If at all possible, use RTC in UTC by calling
             'timedatectl set-local-rtc 0'.

  4. #4
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,285
    Blog Entries
    15

    Default Re: Incomplete journalctl log after system upgrade and reboot

    Hi
    Not using ntp? I would recommend setting the BIOS (RTC) time to UTC.

    Anyway, you should see full logs with;

    Code:
    journalctl --no-pager | less
    So what exactly are you not seeing?
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  5. #5

    Default Re: Incomplete journalctl log after system upgrade and reboot

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Not using ntp? I would recommend setting the BIOS (RTC) time to UTC.

    Anyway, you should see full logs with;

    Code:
    journalctl --no-pager | less
    So what exactly are you not seeing?
    No but time is correct

    This is missing in journalctl -r:
    Code:
    Apr 19 15:02:21 lin kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13
    Apr 19 15:02:21 lin kernel: Linux version 5.3.18-lp152.69-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP Tue Apr 6 11:41:13>
    Apr 19 15:02:21 lin kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-lp152.69-default root=UUID=xxxxxx ro
    Apr 19 15:02:21 lin kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
    Apr 19 15:02:21 lin kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
    Apr 19 15:02:21 lin kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
    Apr 19 15:02:21 lin kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
    Apr 19 15:02:21 lin kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
    Apr 19 15:02:21 lin kernel: BIOS-provided physical RAM map:
    Apr 19 15:02:21 lin kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
    .....

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,285
    Blog Entries
    15

    Default Re: Incomplete journalctl log after system upgrade and reboot

    Hi
    I wonder if the journal rolled over, check in /var/log/journal/
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #7

    Default Re: Incomplete journalctl log after system upgrade and reboot

    Quote Originally Posted by malcolmlewis View Post
    Hi
    I wonder if the journal rolled over, check in /var/log/journal/
    Hi,

    Yes it has rolled over.

    It seems to be correct and solved now.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •