Skip to main content

042stab127.2 problem

Comments

13 comments

  • Alexandre Parubochyi
    BTW, they were both running the same kcare kernel before the update. The last one released before this meltdown/Spectre one.
    0
  • Alexandre Parubochyi
    So am I the only one having this problem? It is definitely something related to Kernelcare. It happen right after I had a heavy process run that clears out all the cache and causes high load for a few minutes. Right after that, instead of the load subsiding, it skyrocketed. Load average was 200 when it is normally below 4. CPU wait state was hopping around between 50% and 95% which means it's waiting for I/O.

    I disabled the heavy cron job for now but I suspect the problem is still there and could be triggered again when the heavy cron job runs.
    0
  • Alexandre Parubochyi
    I should point out that I have updated other servers with the native 042stab127.2 kernel, not kernelcare, and haven't seen this problem.
    0
  • Alexandre Parubochyi
    Fred, please create a ticket at https://cloudlinux.zendesk.com (KernelCare department) so our support team can help you with the issue.
    0
  • Peter Laws
    Was there any outcome to this? Was it KC? I've been scared to yum update kernelcare for a while now...
    0
  • Alexandre Parubochyi
    A ticket #26416 has been created to investigate the issue.
    BTW, yum update kernelcare shouldn't bring in any problems with binary patches that KC applies.
    0
  • Peter Laws
    I'm stupid, I thought you needed the latest KC to upgrade to stab127.2...... Seems I've had this kernel version for ages.... :o as (_8(|) says..... d'oh
    0
  • Peter Laws
    So far, the high load problem has not re-occurred since the first time where I had restart containers that use vswap.
    0
  • Vladimir Marchuk
    Glad to hear that.

    Feel free to let me know if you have any further questions or concerns.
    0
  • Vladimir Marchuk
    Well it just happened again. I rebooted the 2 containers that seemed to be causing the high load and it went away again. I am going to have to upgrade this node to the real kernel and see if that takes care of it.
    0
  • Vladimir Marchuk
    Hello.

    We would like to check this problem.
    Please submit a ticket to https://cloudlinux.zendesk.com, our techs will check the issue in place.
    0
  • Vladimir Marchuk
    Hello.

    We would like to check this problem.
    Please submit a ticket to https://cloudlinux.zendesk.com, our techs will check the issue in place.


    You guys already did and said you couldn't find anything. It seems to be hard to reproduce. I see there was one race condition that was fixed in the latest OVZ kernel so maybe that took care of it. It started happening as soon as up updated Kernelcare and I haven's seen this on other nodes not running KernelCare but running the exact same real kernel. So I think the best thing is to run the real kernel in this case.
    0
  • Vladimir Marchuk
    I am sorry, but it's hard to help you without a clear understanding what's going on on that server.
    We really would like to check this problem in place. Please submit a ticket to https://cloudlinux.zendesk.com and our techs will investigate it further.
    0

Please sign in to leave a comment.