CloudLinux OS Blog

CloudLinux 7 kernel updated

CloudLinux 7 kernel updated

The new updated CloudLinux 7 kernel version 3.10.0-614.10.2.lve1.4.50 is available for download from our production repository.

Changelog since kernel-3.10.0-427.36.1.lve1.4.47:

  • improved fix for CVE-2017-7895;
  • rebased kernel to OpevVZ rh7-3.10.0-514.10.2.vz7.29.2;
  • fixed a deadlock with hpc backup solution;
  • CLKRN-92: megaraid driver panic fixes;
  • CLKRN-94: improved symlink attack protection by checking nested symlinks;
  • CLKRN-95: reduced high-order allocation impact in filesystem mount code;
  • CLKRN-97: fixed kernel panic on netlink_lookup;
  • CLKRN-104: fixed crashes around rhashtable as part of rebase;
  • CLKRN-105, CLKRN-115: fixed NULL pointer dereferencing in task scheduler;
  • CLKRN-106: avoiding kernel crash when setting vm.vfs_cache_min_ratio to zero in runtime;
  • CLKRN-117: avoiding running out of container ID's;
  • KMODLVE-66: fixed panic while waiting for LVE to be initialized.

To install new kernel please run the following command:

CloudLinux 7:

yum clean all --enablerepo=* && yum install kernel-3.10.0-614.10.2.lve1.4.50.el7 kmod-lve-1.4-50.el7

CloudLinux 6 Hybrid:

yum clean all --enablerepo=* && yum install kernel-3.10.0-614.10.2.lve1.4.50.el6h kmod-lve-1.4-50.el6h

Topic: CloudLinux OS Blog , Tags: #kernel-cl7,

1245 people viewed this

Comments (9)

 
by Guest - Ryan Smith / Friday, 26 May 2017 15:52

I rebooted a server into this kernel and Apache (EA4) stopped working afterwards and wouldn't load any sites.

I booted back into the previous production kernel and everything worked again.

Anyone else having similar issues?

I rebooted a server into this kernel and Apache (EA4) stopped working afterwards and wouldn't load any sites. I booted back into the previous production kernel and everything worked again. Anyone else having similar issues?
by Guest - Tom Risager / Sunday, 28 May 2017 15:50

Similar issue here. See https://forums.cpanel.net/threads/508-virtual-memory-errors-but-no-memory-limits.601943/

Similar issue here. See https://forums.cpanel.net/threads/508-virtual-memory-errors-but-no-memory-limits.601943/
by Bogdan / Monday, 29 May 2017 13:13

We were able to identify that the issue happens only when physical memory limit is set to 0 (unlimited), this is being investigated by our kernel developers now.

As a temporary workaround please set pmem limit to 1G.

We were able to identify that the issue happens only when physical memory limit is set to 0 (unlimited), this is being investigated by our kernel developers now. As a temporary workaround please set pmem limit to 1G.
by Guest - Tom Risager / Monday, 29 May 2017 13:28

Well, we did try setting hard limits, but that just gave us 503 errors instead (we are using Litespeed). So there must be more to the story ...

Well, we did try setting hard limits, but that just gave us 503 errors instead (we are using Litespeed). So there must be more to the story ...
by Bogdan / Monday, 29 May 2017 18:13

Then the issue is somewhere else, please create support ticket with us and we will help pretty fast.

Then the issue is somewhere else, please create support ticket with us and we will help pretty fast.
by Guest - Lucas Rolff / Sunday, 28 May 2017 10:10

I had an issue with the kernel that rendered the system not being able to boot.
This only happens on EFI systems, the fix:
grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg

Just if anyone else experience the same thing.

I had an issue with the kernel that rendered the system not being able to boot. This only happens on EFI systems, the fix: grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg Just if anyone else experience the same thing.
by Bogdan / Monday, 29 May 2017 13:14

I believe there were some errors during the initial kernel update procedure, the grub2-mkconfig should not be launched manually. This all should be done by dracut during the update.

I believe there were some errors during the initial kernel update procedure, the grub2-mkconfig should not be launched manually. This all should be done by dracut during the update.
by Guest - Vekoh Pardo / Tuesday, 13 June 2017 15:44

Hi I had the same issue after the kernel upgrade, only the accts with 0 PMEM limit were affected, it was fixed by setting those to 2GB PMEM.
Pls advise as soon as there is a permanent fixed for this issue.

thank you

Hi I had the same issue after the kernel upgrade, only the accts with 0 PMEM limit were affected, it was fixed by setting those to 2GB PMEM. Pls advise as soon as there is a permanent fixed for this issue. thank you
by Bogdan / Wednesday, 14 June 2017 10:24

The permanent fix is to update to latest beta where issue is fixed: https://www.cloudlinux.com/cloudlinux-os-blog/entry/beta-cloudlinux-7-kernel-updated-1-6

The permanent fix is to update to latest beta where issue is fixed: https://www.cloudlinux.com/cloudlinux-os-blog/entry/beta-cloudlinux-7-kernel-updated-1-6

Leave your comment

Guest, Friday, 24 November 2017

Captcha Image