Cron /usr/bin/kcarectl --auto-update "No updates are needed for this kernel" email arriving every 4 hours

[vespera]

I'm OK when KernelCare sends a notification every now and then about some update, unknown kernel or similar, but for the past 2-3 days I'm getting an email every 4 hours, whenever KernelCare checks for updates, notifying me that I don't need an update:
"Subject: Cron <xyz@xyz> /usr/bin/kcarectl --auto-update"
"Updates already downloaded
No updates are needed for this kernel"
How do I stop these emails? I do want to know if something's wrong, but if everything is OK I really don't need an email every 4 hours telling me that nothing is wrong...
Thank's for any advice!

 

[Twinsvision]

Have same problem since 3 or 4 days ago... Any solution?

 

[James Fu]

I'm observing the same thing. First email on 30th April, 20:49, then it's been every 4 hours since.

 

[Arseni]

Same here. I started getting these just recently. I would reroute these notifications to some separate email account, but not sure what is the proper way to do that

 

[jcpeters]

Exactly the same problem here. Started 2-3 days ago. As mentioned by vespera, any advice would be much appreciated.
Thanks.

 

[CloudLinux Skhristich]

I'm OK when KernelCare sends a notification every now and then about some update, unknown kernel or similar, but for the past 2-3 days I'm getting an email every 4 hours, whenever KernelCare checks for updates, notifying me that I don't need an update:
"Subject: Cron <xyz@xyz> /usr/bin/kcarectl --auto-update"
"Updates already downloaded
No updates are needed for this kernel"
How do I stop these emails? I do want to know if something's wrong, but if everything is OK I really don't need an email every 4 hours telling me that nothing is wrong...
Thank's for any advice!

Hello,
You can configure this using this command:

rm /etc/cron.d/kcare-cron
yum reinstall -y kernelcare

Thank you.

 

[tonino]

Same problem here, started last Friday. I imagine there will be an update to fix this issue.

 

[James Fu]

Hey Skhristich,

Thank you for your reply.

Inspecting my /etc/cron.d/ directory, I found `kcare-cron` and `kcare-cron.rpmnew`(an empty file). After removing both and reinstalling kernelcare, I see that the new `kcare-cron` runs `/usr/bin/kcarectl` with the `-q` flag compared to before. Presumably this is the only thing that needs to be corrected.

I looked up yum history and this appears to be where things went awry:

Updated    kernelcare-2.24-1.el7.x86_64                                    @kernelcare
Update                2.27-1.el7.x86_64                                    @kernelcare

Hope this helps someone else!

 

[vespera]

Thanks, I'll try this

 

[cPanelLauren]

This is a known issue with kernelcare, there's no way for CloudLinux to immediately update the supported kernel as soon as a kernel version is released. There are a ton of other forums threads here that can answer this question as well.

 

[vespera]

Unfortunately, the plain reinstall didn't help, I'm still getting the emails every 4 hours. I'll check my cron...
And, I think cPanelLauren didn't actually understand that this isn't the same issue as the known problem with KernelCare "unknown kernel" emails, that has been discussed all over the forums for some time now - this is a new problem, arised a few days ago, with constant emails telling us that "No updates are needed"...

 

[vespera]

Just checked the etc/cron.d directory: I only have one kcare-cron file, and it contains just the line
14 */4 * * * xyz /usr/bin/kcarectl --auto-update
So, no -q flag... Adding the -q just before --auto-update should mean the task is running silent? But then I also wouldn't get the email if something went wrong (like the unknown kernel emails)?

 

[Kidades]

Doing

rm /etc/cron.d/kcare-cron
yum reinstall -y kernelcare

has fixed it for me.

 

[ffeingol]

@cPanelLauren This is a different issue. It was introduced with 2.27-1. It started sending emails that there were no new patches to download vs the old not supported kernel.

I can also confirm that if you follow KernelCare's process (remove the cron, reinstall) it will fix it. After the reinstall the cron will look like this (your time will be different);

39 */4  * * * root /usr/bin/kcarectl -q --auto-update

I can't tell you what all the re-install does, but it adds the -q parameter to the cron.

It also loos like they released 2.28-1 yesterday, and I'm not sure if that solves it automagically.

 

[CloudLinux Skhristich]

Just checked the etc/cron.d directory: I only have one kcare-cron file, and it contains just the line
14 */4 * * * xyz /usr/bin/kcarectl --auto-update
So, no -q flag... Adding the -q just before --auto-update should mean the task is running silent? But then I also wouldn't get the email if something went wrong (like the unknown kernel emails)?

Hello,
No, -q does not affect warnings. The user will receive messages about unknown kernels even if -q is used. The --quiet option removes informational messages about a successful launch (kernel is safe, no updates are needed, etc). Warnings and mistakes will remain.
Thanks

 

[vespera]

The plain reinstall didn't work for me, but adding the -q flag to kcare-cron did the trick. I'm not getting the emails any more... thanks for all the helpful advices.

 

[James Fu]

Hello,
No, -q does not affect warnings. The user will receive messages about unknown kernels even if -q is used. The --quiet option removes informational messages about a successful launch (kernel is safe, no updates are needed, etc). Warnings and mistakes will remain.
Thanks

Yes, thanks for clarifying. @vespera this is in line with the `kcarectl` help message:

  -q, --quiet           Suppres messages, provide only errors and warnings to
                        stderr

@CloudLinux Skhristich Suppress is missing an 's', just btw.