Forum
  1. Forums
  2. KernelCare
  3. KernelCare General Discussion
  1. Mitch
  2. Friday, October 26, 2018
  3.  Subscribe via email
Got this today with subject: Cron <[email protected]> /usr/bin/kcarectl --auto-update --gradual-rollout=auto


Unknown Kernel (CloudLinux 3.10.0-714.10.2.lve1.5.19.8.el7.x86_64)
_______________________

I have Cloudlinux 7.5 and Kernel Care

How can I fix this?

Mitch
Rate this post:
  1. 26.10.2018 21:10:01
  2. # 1
Attila Petranyi Accepted Answer
Posts: 0
Joined: 13.12.2018
0
Votes
Undo
You need wait for the KernelCare Team to add this kernel to KernelCare.
  1. 27.10.2018 02:10:46
  2. # 2
Mitch Accepted Answer
Posts: 3
Joined: 13.05.2018
0
Votes
Undo
OK Thanks
  1. 19.11.2018 21:11:36
  2. # 3
Shaun Accepted Answer
When do you guys plan on getting around to adding this kernel to your list? My customers are getting extremely irritated that they've been getting this warning for almost a month now. You keep saying it will take a few days to be added to your repo but still nothing? Whats going on?


[[email protected] ~]# kcarectl --update
> Updates already downloaded
> Unable to apply patch
> (/var/cache/kcare/patches/none-21ee07ae625aba9696cae235a6276254e05c8aaf-17-default/kpatch.bin
> 17 255 CloudLinux 3.10.0-714.10.2.lve1.5.12.el7.x86_64, default, , , False)
  1. 20.11.2018 12:11:08
  2. # 4
Vladimir Accepted Answer
Posts: 87
Joined: 04.07.2017
0
Votes
Undo
Hello,

Please provide the output of the following commands:
# uname -r
# kcare-uname -r
# kcarectl -i
  1. 20.11.2018 21:11:04
  2. # 5
shaun Accepted Answer
[[email protected] ~]# uname -r
3.10.0-714.10.2.lve1.5.19.8.el7.x86_64

[[email protected] ~]# kcare-uname -r
3.10.0-714.10.2.lve1.5.19.8.el7.x86_64

[[email protected] ~]# kcarectl -i
No patches applied, but some are available, run 'kcarectl --update'.

[[email protected] ~]# kcarectl -u
Updates already downloaded
Unable to apply patch (/var/cache/kcare/patches/test-0e568b17a0a299aaeb0548b6e3874e7754a63408-2-default/kpatch.bin 2 255 CloudLinux 3.10.0-714.10.2.lve1.5.19.8.el7.x86_64, default, , , False)

[[email protected] ~]# dmesg
[2240177.405473] kcare: allocated 354768 bytes for patch at ffffc90008b3c000
[2240177.405616] kcare: verifying patch...
[2240177.405618] kcare: verified successfully
[2240177.405620] kcare: allocating memory in module space...
[2240177.405668] kcare: allocated 354768 bytes at ffffffffa115f000
[2240177.405728] kcare: 1429 relocations to fixup...
[2240177.405736] kcare: fixed 1429 relocations
[2240177.405738] kcare: 0 extra relocations to fixup...
[2240177.405740] kcare: fixed 0 extra relocations
[2240177.405741] kcare: jumping to ffffffffa116a580
[2240177.405745] kpatch: starting at ffffffffa115f000 (Linux version 3.10.0-714.10.2.lve1.5.19.8.el7.x86_64 ([email protected]) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Wed Oct 24 08:54:57 EDT 2018, ts 1541414098)...
[2240187.321317] kpatch: safety check failed for 'load_module.kpatch' ffffffff811101f0/ffffffffa116b760 (task 720:systemd-udevd)
[2240187.323981] Call Trace:
[2240187.323990] [<ffffffff810c7e75>] ? check_preempt_curr+0x75/0xa0
[2240187.323995] [<ffffffff816a1f99>] schedule+0x29/0x70
[2240187.324006] [<ffffffffa03f495d>] get_guid+0x13d/0x180 [ipmi_msghandler]
[2240187.324010] [<ffffffff810b5f50>] ? wake_up_atomic_t+0x30/0x30
[2240187.324017] [<ffffffffa03f4fa9>] ipmi_register_smi+0x429/0x963 [ipmi_msghandler]
[2240187.324026] [<ffffffffa01ca727>] ? start_kcs_transaction+0x67/0x100 [ipmi_si]
[2240187.324034] [<ffffffffa01c7ac8>] try_smi_init+0x568/0x9e0 [ipmi_si]
[2240187.324042] [<ffffffffa01c9f0e>] init_ipmi_si+0x56e/0xbb0 [ipmi_si]
[2240187.324049] [<ffffffffa01c99a0>] ? cleanup_ipmi_si+0xc0/0xc0 [ipmi_si]
[2240187.324054] [<ffffffff810020e8>] do_one_initcall+0xb8/0x230
[2240187.324061] [<ffffffff811124b7>] load_module+0x22c7/0x2960
[2240187.324066] [<ffffffff813471a0>] ? ddebug_proc_write+0xf0/0xf0
[2240187.324074] [<ffffffff8110e203>] ? copy_module_from_fd.isra.43+0x53/0x150
[2240187.324078] [<ffffffff81112d06>] SyS_finit_module+0xa6/0xd0
[2240187.324082] [<ffffffff816ae4bd>] system_call_fastpath+0x16/0x1b
[2240187.324086] [<ffffffff816ae35d>] ? system_call_after_swapgs+0xca/0x214
[2240187.327732] Freezing user space processes ...
[2240207.331708] Freezing of tasks failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
[2240207.333462] systemd-udevd D ffff88042ee2cfb0 0 720 672 0 0x00000004
[2240207.333466] Call Trace:
[2240207.333475] [<ffffffff810c7e75>] ? check_preempt_curr+0x75/0xa0
[2240207.333479] [<ffffffff816a1f99>] schedule+0x29/0x70
[2240207.333490] [<ffffffffa03f495d>] get_guid+0x13d/0x180 [ipmi_msghandler]
[2240207.333494] [<ffffffff810b5f50>] ? wake_up_atomic_t+0x30/0x30
[2240207.333500] [<ffffffffa03f4fa9>] ipmi_register_smi+0x429/0x963 [ipmi_msghandler]
[2240207.333509] [<ffffffffa01ca727>] ? start_kcs_transaction+0x67/0x100 [ipmi_si]
[2240207.333515] [<ffffffffa01c7ac8>] try_smi_init+0x568/0x9e0 [ipmi_si]
[2240207.333522] [<ffffffffa01c9f0e>] init_ipmi_si+0x56e/0xbb0 [ipmi_si]
[2240207.333528] [<ffffffffa01c99a0>] ? cleanup_ipmi_si+0xc0/0xc0 [ipmi_si]
[2240207.333533] [<ffffffff810020e8>] do_one_initcall+0xb8/0x230
[2240207.333540] [<ffffffff811124b7>] load_module+0x22c7/0x2960
[2240207.333544] [<ffffffff813471a0>] ? ddebug_proc_write+0xf0/0xf0
[2240207.333551] [<ffffffff8110e203>] ? copy_module_from_fd.isra.43+0x53/0x150
[2240207.333554] [<ffffffff81112d06>] SyS_finit_module+0xa6/0xd0
[2240207.333558] [<ffffffff816ae4bd>] system_call_fastpath+0x16/0x1b
[2240207.333561] [<ffffffff816ae35d>] ? system_call_after_swapgs+0xca/0x214

[2240207.333608] Restarting tasks ... done.
[2240207.341421] device-mapper: thin: Deletion of thin device 17 failed.
[2240208.153190] device-mapper: thin: Deletion of thin device 17 failed.
[[email protected] ~]#
  1. 21.11.2018 13:11:11
  2. # 6
Vladimir Accepted Answer
Posts: 87
Joined: 04.07.2017
0
Votes
Undo
Thank you for your reply.

It appears that this kernel already supported by KernelCare:
https://patches.kernelcare.com/0e568b17a0a299aaeb0548b6e3874e7754a63408/2/kpatch.html

But apparently, there were some problems during the update on your server. Could you please submit support ticket
to https://cloudlinux.zendesk.com, our techs will check the issue in place.

Kind regards,
  • Page :
  • 1


There are no replies made for this post yet.
Be one of the first to reply to this post!
Guest
Submit Your Response
Upload files or images for this discussion by clicking on the upload button below. Supports gif,jpg,png,zip,rar,pdf
• Remove Upload Files (Maximum File Size: 2 MB)
You may insert polls into your post. The poll would then appear in the post.
Vote Options
Captcha
To protect the site from bots and unauthorized scripts, we require that you enter the captcha codes below before posting your question.