gpg: Signature made Wed Feb 12 15:30:13 2020 UTC
gpg: using DSA key 2099B64CBF15490B
gpg: Good signature from "Andy Smith <andy@strugglers.net>" [unknown]
gpg: aka "Andrew James Smith <andy@strugglers.net>" [unknown]
gpg: aka "Andy Smith (UKUUG) <andy.smith@ukuug.org>" [unknown]
gpg: aka "Andy Smith (BitFolk Ltd.) <andy@bitfolk.com>" [unknown]
gpg: aka "Andy Smith (Linux User Groups UK) <andy@lug.org.uk>" [unknown]
gpg: aka "Andy Smith (Cernio Technology Cooperative) <andy.smith@cernio.com>" [unknown]
Hi Martijn,
On Wed, Feb 12, 2020 at 05:14:15PM +0200, Martijn Grooten wrote:
> "This version of the GNU libc requires kernel version 3.2 or later. Please
> upgrade your kernel before installing glibc."
That is rather worrying. The kernel in buster is 4.19.67-2+deb10u2.
In the previous release (stretch) it is 4.9.210-1 and in the one
before that (jessie) there was 3.16.81-1.
> Is there an easy answer to the obvious question what kernel to upgrade to?
> And would this even solve my issues? I currently appear to be running
> 2.6.32-5-686-bigmem.
That's absolutely ancient and I am amazed that your system works at
all.
Any ideas how you have managed to end up running a Debian 6
(squeeze) era kernel on a Debian 10 user land?
That kernel went end of life for security updates in 2014 by the
way!
> I've had this server for years and I might have added one quick fix for a
> specific problem too many over the years.
>
> Here's the content of /etc/apt/sources.list:
>
> deb http://apt-cacher.lon.bitfolk.com/debian/ftp.uk.debian.org/debian/
> stable main contrib
> deb-src http://apt-cacher.lon.bitfolk.com/debian/ftp.uk.debian.org/debian/
> stable main contrib
> deb http://apt-cacher.lon.bitfolk.com/debian/ftp.uk.debian.org/debian/
> stable-updates main contrib
> deb http://apt-cacher.lon.bitfolk.com/debian/security.debian.org/
> stable/updates main contrib
Are you sure you're actually running Debian stable, i.e. you have
previously done an "apt-get update" and then an "apt-get
dist-upgrade" which all completed okay in the past?
What kernels do you actually have installed right now?
$ dpkg -l | grep linux-image
What is the output of:
$ ls -la /boot/
What happens when you update your grub config:
$ sudo update-grub
I would really hope that it is just a case of there being an old
kernel hanging around that your boot loader keeps selecting but
honestly this is so weird that I would not trust your system to come
back up correctly if you rebooted it right now.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
