What are you meaning here? A small training hangout about templates-custom?
If I’m not mistaken @nas can also lend a hand
Well, that doesn’t seem to be what’s happening.
None of the kernels in my yumdb have the installonly key set, the installonly_limit in /etc/yum.conf is set to 5. But after installing the latest updates today, which included a new kernel, I now have 8 kernels installed in /boot.
Cheers.
I just checked the first NethServer I’ve installed, running since 3.5 years: there are only 5 kernels in /boot.
-rwxr-xr-x 1 root root 4269008 Oct 5 02:41 /boot/vmlinuz-2.6.32-642.6.1.el6.x86_64
-rwxr-xr-x. 1 root root 4268880 Aug 23 22:04 /boot/vmlinuz-2.6.32-642.4.2.el6.x86_64
-rwxr-xr-x. 1 root root 4265936 Jul 12 20:39 /boot/vmlinuz-2.6.32-642.3.1.el6.x86_64
-rwxr-xr-x. 1 root root 4264432 Jun 1 00:02 /boot/vmlinuz-2.6.32-642.1.1.el6.x86_64
-rwxr-xr-x. 1 root root 4264528 May 10 19:32 /boot/vmlinuz-2.6.32-642.el6.x86_64
-rwxr-xr-x. 1 root root 4221232 Dec 15 2015 /boot/vmlinuz-2.6.32-573.12.1.el6.x86_64
-rwxr-xr-x. 1 root root 4221968 Feb 9 2016 /boot/vmlinuz-2.6.32-573.18.1.el6.x86_64
-rwxr-xr-x. 1 root root 4222448 Mar 22 2016 /boot/vmlinuz-2.6.32-573.22.1.el6.x86_64
-rwxr-xr-x. 1 root root 4222832 May 3 18:27 /boot/vmlinuz-2.6.32-573.26.1.el6.x86_64
-rwxr-xr-x. 1 root root 4264432 May 31 15:02 /boot/vmlinuz-2.6.32-642.1.1.el6.x86_64
-rwxr-xr-x 1 root root 4265936 Jul 12 11:39 /boot/vmlinuz-2.6.32-642.3.1.el6.x86_64
-rwxr-xr-x 1 root root 4268880 Aug 23 13:04 /boot/vmlinuz-2.6.32-642.4.2.el6.x86_64
-rwxr-xr-x 1 root root 4269008 Oct 4 17:41 /boot/vmlinuz-2.6.32-642.6.1.el6.x86_64
Cheers.
Just look out of insterest. I’ve installed 9 in total.
In yum.conf is installonly_limit=5
. Didn’t change anything from original.
-rwxr-xr-x. 1 root root 4221968 Feb 10 2016 /boot/vmlinuz-2.6.32-573.18.1.el6.x86_64
-rwxr-xr-x. 1 root root 4222448 Mar 23 2016 /boot/vmlinuz-2.6.32-573.22.1.el6.x86_64
-rwxr-xr-x. 1 root root 4222832 May 4 03:27 /boot/vmlinuz-2.6.32-573.26.1.el6.x86_64
-rwxr-xr-x. 1 root root 4220560 Jul 23 2015 /boot/vmlinuz-2.6.32-573.el6.x86_64
-rwxr-xr-x. 1 root root 4264432 Jun 1 00:02 /boot/vmlinuz-2.6.32-642.1.1.el6.x86_64
-rwxr-xr-x 1 root root 4265936 Jul 12 20:39 /boot/vmlinuz-2.6.32-642.3.1.el6.x86_64
-rwxr-xr-x 1 root root 4268880 Aug 23 22:04 /boot/vmlinuz-2.6.32-642.4.2.el6.x86_64
-rwxr-xr-x 1 root root 4269008 Oct 5 02:41 /boot/vmlinuz-2.6.32-642.6.1.el6.x86_64
-rwxr-xr-x. 1 root root 4264528 May 10 19:32 /boot/vmlinuz-2.6.32-642.el6.x86_64
I checked all my servers and I found only one that has 10 kernels installed.
Now I have to discover what differences it has from the rest.
Just identified my problem I think: virtualbox.
-------- Uninstall Beginning --------
Module: vboxhost
Version: 5.0.20
Kernel: 2.6.32-573.26.1.el6.x86_64 (x86_64)
Status: Before uninstall, this module version was ACTIVE on this kernel.
Removing any linked weak-modules
It’s certainly not VirtualBOX…
My Microserver NethServer instance has 7 old kernel
And my installonly_limit in /etc/yum.conf is set to 2
And it’s not the presence of weak-updates, I have some systems with weak-updates modules that have 5 kernels.
I’ve discovered the problem: that lone server had kernel-debug installed, doubling the count of kernels. So it really has 5 kernels installed.
We’re back to start: I can’t reproduce the problem, all servers have 5 kernels installed.
Is it a contest?
Let’s resurrect this zombie thread.
Now running NS7 and this is in /etc/yum.conf:
installonly_limit=5
But, here’s the relevant part of an ls from boot after the last couple of updates:
[root@Nethserver ~]# cd /boot
[root@Nethserver boot]# ls -lrt vmlinuz-*
-rwxr-xr-x. 1 root root 5392080 Nov 22 2016 vmlinuz-3.10.0-514.el7.x86_64
-rwxr-xr-x 1 root root 5392752 Feb 22 19:16 vmlinuz-3.10.0-514.6.2.el7.x86_64
-rwxr-xr-x. 1 root root 5392080 Mar 1 16:56 vmlinuz-0-rescue-13ad7b333d3e4171a17342c53d60c4c0
-rwxr-xr-x 1 root root 5393008 Mar 2 16:15 vmlinuz-3.10.0-514.10.2.el7.x86_64
-rwxr-xr-x 1 root root 5396240 Apr 12 08:15 vmlinuz-3.10.0-514.16.1.el7.x86_64
-rwxr-xr-x 1 root root 5397552 May 25 10:16 vmlinuz-3.10.0-514.21.1.el7.x86_64
-rwxr-xr-x 1 root root 5397520 Jun 20 05:36 vmlinuz-3.10.0-514.21.2.el7.x86_64
-rwxr-xr-x 1 root root 5397328 Jun 29 09:16 vmlinuz-3.10.0-514.26.1.el7.x86_64
-rwxr-xr-x 1 root root 5397008 Jul 4 08:15 vmlinuz-3.10.0-514.26.2.el7.x86_64
[root@Nethserver boot]#
Guess it still isn’t working as designed.
Cheers.
[root@server9b ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
22G 13G 7.8G 62% /
tmpfs 939M 0 939M 0% /dev/shm
/dev/sda1 504M 465M 14M 98% /boot
I have 18 kernels on this bone default production mail server and now any update attempts from the gui fail.
Removed:
kernel.x86_64 0:2.6.32-504.el6 kernel.x86_64 0:2.6.32-504.23.4.el6 kernel.x86_64 0:2.6.32-504.30.3.el6
kernel.x86_64 0:2.6.32-573.7.1.el6 kernel.x86_64 0:2.6.32-573.8.1.el6 kernel.x86_64 0:2.6.32-573.12.1.el6
kernel.x86_64 0:2.6.32-573.18.1.el6 kernel.x86_64 0:2.6.32-573.22.1.el6 kernel.x86_64 0:2.6.32-573.26.1.el6
kernel.x86_64 0:2.6.32-642.1.1.el6 kernel.x86_64 0:2.6.32-642.3.1.el6 kernel.x86_64 0:2.6.32-642.4.2.el6
kernel.x86_64 0:2.6.32-642.6.2.el6 kernel.x86_64 0:2.6.32-642.11.1.el6
Complete!
[root@server9b boot]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
22G 11G 9.3G 54% /
tmpfs 939M 0 939M 0% /dev/shm
/dev/sda1 504M 115M 364M 25% /boot
I think you desserve a new badge for this
Hallo,
some years ago I found this for CentOS:
root#> yum install yum-utils
…
root#> package-cleanup --oldkernels --count=2
–count=[number of kernels to stay]
I created a 2kernel.sh including the last line.
Today i installed kernel 3.10.957.10.1; after the update…
rpm -qa kernel
kernel-3.10.0-862.11.6.el7.x86_64
kernel-3.10.0-957.5.1.el7.x86_64
kernel-3.10.0-957.1.3.el7.x86_64
kernel-3.10.0-862.14.4.el7.x86_64
kernel-3.10.0-957.10.1.el7.x86_64
now installed on my ritual-murder box
Current versions of Neth should limit themselves to five installed kernels. It’s probably more than are needed, but there still should be cleanup going on.