Hi Thomas,
On Dienstag, 14. Juni 2016 23:20:47 CEST Thomas Liske wrote:
> On Mon, Jun 13, 2016 at 09:43:26AM +0200, Martin Steigerwald wrote:
> > Means it thinks the kernel has changed, while it has not. I know for sure
> > I booted exactly this kernel. It seems to be confused detecting the end of
> > the version number in the second case as it appears that it uses the whole
> > output of /proc/version for comparison.
>
> I assume the problem might be triggered by the bpo kernel, but I did
> not verify, yet. The problem should be exist before 2.8 since the
> kernel detection stuff was not changed recently.
>
> > mondschein:~> cat /proc/version
> > Linux version 4.5.0-0.bpo.2-686 (debian-ker...@lists.debian.org) (gcc
> > version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.5.4-1~bpo8+1
> > (2016-05-13)
> >
> >
> > Why doesn´t it just use uname -r and be done with it?
>
> Using `uname -r` would hide ABI compatible (security) updates :-(
Hm, okay. Ubuntu handles this differently I think, but then you more often
need to cleanup previous kernels.
> > On another of my Debian Jessie server VMs I am not seeing this issue, but
> > it uses amd64 as architecture instead of i386.
>
> Could you please provide the output of `needrestart -v -r l`? It would
> be sufficient to provide the kernel related lines ('^[Kernel]' until
> the kernel status message).
Including everything as there are some could not get a source file messages
that might be interesting as well.
I think it doesn´t cut the kernel version string at the place where it should
for comparing.
mondschein:~> LANG=C needrestart -v -r l
[main] eval /etc/needrestart/needrestart.conf
[main] running in root-mode
[Core] Using UI 'NeedRestart::UI::stdio'...
[Core] #2101 is a NeedRestart::Interp::Python
[Core] #2102 is a NeedRestart::Interp::Python
[Core] #2103 is a NeedRestart::Interp::Python
[Core] #2104 is a NeedRestart::Interp::Python
[Core] #2105 is a NeedRestart::Interp::Python
[Core] #2106 is a NeedRestart::Interp::Python
[Core] #2107 is a NeedRestart::Interp::Python
[Core] #2108 is a NeedRestart::Interp::Python
[Core] #2109 is a NeedRestart::Interp::Python
[Core] #2493 is a NeedRestart::Interp::Perl
[Perl] #2493: could not get a source file, skipping
[Core] #2495 is a NeedRestart::Interp::Perl
[Perl] #2495: could not get a source file, skipping
[Core] #2590 is a NeedRestart::Interp::Perl
[Perl] #2590: could not get a source file, skipping
[Core] #2843 is a NeedRestart::Interp::Perl
[Perl] #2843: could not get a source file, skipping
[Core] #2844 is a NeedRestart::Interp::Perl
[Perl] #2844: could not get a source file, skipping
[Core] #7943 is a NeedRestart::Interp::Perl
[Perl] #7943: could not get a source file, skipping
[Core] #9811 is a NeedRestart::Interp::Perl
[Perl] #9811: could not get a source file, skipping
[Kernel] Linux: kernel release 4.5.0-0.bpo.2-686, kernel version #1 SMP Debian
4.5.4-1~bpo8+1 (2016-05-13)
Failed to load NeedRestart::Kernel::kFreeBSD: [Kernel/kFreeBSD] Not running on
GNU/kFreeBSD!
[Kernel/Linux] /boot/vmlinuz-4.5.0-0.bpo.2-686 => 4.5.0-0.bpo.2-686 (debian-
ker...@lists.debian.org) #1 SMP Debian 4.5.4-1~bpo8+1 (2016-05-13)
, [4.5.0-0.bpo.2-686 (debian-ker...@lists.debian.org) #1 SMP Debian
4.5.4-1~bpo8+1 (2016-05-13)]*
[Kernel/Linux] /boot/vmlinuz-4.4.0-0.bpo.1-686 => 4.4.0-0.bpo.1-686 (debian-
ker...@lists.debian.org) #1 SMP Debian 4.4.6-1~bpo8+1 (2016-03-20)
, [4.4.0-0.bpo.1-686 (debian-ker...@lists.debian.org) #1 SMP Debian
4.4.6-1~bpo8+1 (2016-03-20)]
[Kernel/Linux] /boot/vmlinuz-3.16.0-4-686-pae => 3.16.0-4-686-pae (debian-
ker...@lists.debian.org) #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08)
[3.16.0-4-686-pae]
[Kernel/Linux] Expected linux version: 4.5.0-0.bpo.2-686 (debian-
ker...@lists.debian.org) #1 SMP Debian 4.5.4-1~bpo8+1 (2016-05-13)
Pending kernel upgrade!
Running kernel version:
4.5.0-0.bpo.2-686
Diagnostics:
The currently running kernel version is not the expected kernel version
4.5.0-0.bpo.2-686 (debian-ker...@lists.debian.org) #1 SMP Debian
4.5.4-1~bpo8+1 (2016-05-13).
Restarting the system to load the new kernel will not be handled
automatically, so you should consider rebooting. [Return]
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
Thanks,
--
Martin
