KernelCare Blog

KernelCare crashes on CloudLinux 7 & CloudLinux 6 Hybrid

KernelCare crashes on CloudLinux 7 & CloudLinux 6 Hybrid

Updated: Dec 7, 2017, 8AM PT

Our previous patch provided the fix of ext4 bug with KernelCare included a bug in unpatch. The bug was triggered by latest patch, and caused some number of servers to crash. The effect of the bug is that servers that use ext4 will crash. If they didn't crash - they will not crash now.

Note that the new patch that triggered the uninstall was delivered in real-time and 12h feeds only. 24h & 48h feeds are not affected. As this patch will not be delivered to 24h & 48h feeds, people on those feeds should not see crashes.

Affected:

  • CloudLinux 7 & CloudLinux 6 Hybrid kernels (3.10 lve version before 1.4.50)
  • Servers that use ext4

Not Affected:

  • Any other kernels & distributions, including CloudLinux 6 kernels;
  • CloudLinux 7 & CloudLinux 6 Hybrid lve1.4.50+ version kernels.

We will make every effort by the asap to have a solution that will automatically update the patches with a minimum risk of repeated crashes.

Due to bug being triggered by unpatching, we strongly advise you - don't run the following commands:

kcarectl --update
kcarectl --unload
uninstall kernelcare

As this can trigger crash (CloudLinux 7 & CloudLinux 6 Hybrid only, all feeds).

Note. More info about different feeds.

Delayed feed ensures that your servers will receive patches 24 hours after the release.
To implement the delayed feed, add PREFIX=’N’h to /etc/sysconfig/kcare/kcare.conf.
We have options for:

  • PREFIX=12h
  • PREFIX=24h
  • PREFIX=48h

Topic: KernelCare Blog

1043 people viewed this

Comments (6)

 
by Guest - Rodrigo Gomes / Thursday, 07 December 2017 20:14

I'm going to migrate to Cloudlinux today from CentOS 7.
I already have KernelCare installed on CentOS with extra symlink protection patches.

Is there any risk of having problems during migration because of this crash?

I'm going to migrate to Cloudlinux today from CentOS 7. I already have KernelCare installed on CentOS with extra symlink protection patches. Is there any risk of having problems during migration because of this crash?
by Guest - Irina / Friday, 08 December 2017 06:33

You should not worry, CentOS kernels are NOT affected.

You should not worry, CentOS kernels are NOT affected.
by Guest - Aleksei / Monday, 11 December 2017 13:51

When you migrate to CloudLinux, you will receive latest kernel, which is not affected. So please proceed with the migration.

When you migrate to CloudLinux, you will receive latest kernel, which is not affected. So please proceed with the migration.
by Guest - Rodrigo Gomes / Monday, 11 December 2017 14:20

I already did the migration, everything worked fine, thanks!

I already did the migration, everything worked fine, thanks!
by Guest - Ryan Smith / Friday, 15 December 2017 15:01

Is there an updated ETA for a fix for affected kernels so we can enable auto-updates again?

Is there an updated ETA for a fix for affected kernels so we can enable auto-updates again?
by Inessa Atmachian / Friday, 15 December 2017 16:35

Hi Ryan,

We expect a solution on our patch server that allows customers with older CloudLinux 7 and CloudLinux 6 Hybrid kernels to safely update their KernelCare patches will be available in the middle of the next week.

Hi Ryan, We expect a solution on our patch server that allows customers with older CloudLinux 7 and CloudLinux 6 Hybrid kernels to safely update their KernelCare patches will be available in the middle of the next week.

Leave your comment

Guest, Sunday, 17 December 2017

Captcha Image