Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED] Seeing weird differences with journalctl on 2 Debian 11 systems

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
road hazard
Posts: 40
Joined: 2017-06-21 19:36

[SOLVED] Seeing weird differences with journalctl on 2 Debian 11 systems

#1 Post by road hazard »

Both PCs were upgraded from Debian 10 to 11 recently.

System A:

Code: Select all

sudo journalctl
-- Journal begins at Thu 2021-08-19 06:45:42 EDT, ends at Tue 2021-09-07 20:07:38 EDT. --
Aug 19 06:45:42 server-pc kernel: Linux version 4.19.0-17-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.194-3 (2021-07-18)
Aug 19 06:45:42 server-pc kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-17-amd64 root=UUID=5f106fd3-99e0-4e9b-8061-c379048e9863 ro quiet

uname -a
Linux server-pc 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) x86_64 GNU/Linux
System B:

Code: Select all

sudo journalctl
- Journal begins at Wed 2021-08-18 23:37:50 EDT, ends at Tue 2021-09-07 20:11:17 EDT. --
Aug 18 23:37:50 rosewill kernel: Linux version 5.10.0-8-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.46-4 (2021-0>
Aug 18 23:37:50 rosewill kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 root=UUID=f49ee6f5-0009-4faa-a974-3a580de2163e ro quiet

uname -a
Linux rosewill 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) x86_64 GNU/Linux

It looks like system A is indeed running the 5.10 kernel but why is journalctl reporting old versions of the kernel and gcc on that first line and why does it say the boot_image is 4.19?
Last edited by road hazard on 2021-09-08 21:32, edited 1 time in total.

road hazard
Posts: 40
Joined: 2017-06-21 19:36

Re: Seeing weird differences with journalctl on 2 Debian 11 systems

#2 Post by road hazard »

Checking cat /proc/cmdline on system A, I get this:

Code: Select all

BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 root=UUID=5f106fd3-99e0-4e9b-8061-c379048e9863 ro quiet
And gcc version is coming back as:

Code: Select all

gcc (Debian 10.2.1-6) 10.2.1 20210110
....and those line up with system B. I'm sure this is a nothing burger but the small OCD part of me is wondering if this can be fixed (not that there's anything wrong I guess?!)

Aki
Global Moderator
Global Moderator
Posts: 2816
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 68 times
Been thanked: 382 times

Re: Seeing weird differences with journalctl on 2 Debian 11 systems

#3 Post by Aki »

Hello,

The journal entry with kernel 4.19 could be related to the boot before the upgrade from Debian Buster to Debian Bullseye.

Can you compare the output of the following command in the two installations after operation system reboot ?

Code: Select all

cat  /proc/version
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: Seeing weird differences with journalctl on 2 Debian 11 systems

#4 Post by p.H »

Aki wrote: 2021-09-08 07:43 The journal entry with kernel 4.19 could be related to the boot before the upgrade from Debian Buster to Debian Bullseye.
Of course it is. At least before the kernel was upgraded. The journal entry is dated back to last month.

road hazard
Posts: 40
Joined: 2017-06-21 19:36

Re: Seeing weird differences with journalctl on 2 Debian 11 systems

#5 Post by road hazard »

p.H wrote: 2021-09-08 10:12
Aki wrote: 2021-09-08 07:43 The journal entry with kernel 4.19 could be related to the boot before the upgrade from Debian Buster to Debian Bullseye.
Of course it is. At least before the kernel was upgraded. The journal entry is dated back to last month.
DING DING DING!

Wow, aren't I the dumb n00b. I checked further into the journal and do indeed see the updated kernel info for system A. What threw me is I updated both of these systems on the same day to Debian 11 so it was confusing why one showed the newer kernel info at the beginning and the other didn't. But all is well, thanks for helping!

Post Reply