Cannot update Plesk with KernelCare extension installed: /lib/modules/3.14.32-xxxx-std-ipv6-64: No such file or directory

Symptoms

1. Cannot update Plesk: update fails on KernelCare extension.

2. Errors in /var/log/plesk/install/autoinstaller3.log:

   CONFIG_TEXT: E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
   E: Unable to lock directory /var/lib/apt/lists/

   CONFIG_TEXT: Setting up kernelcare (2.14-11) ...
   depmod: ERROR: could not open directory /lib/modules/x.xx.xx-xxxx-std-ipv6-64: No such file or directory
   depmod: FATAL: could not search modules: No such file or directory
   dpkg: error processing package kernelcare (--configure):

3. /lib/modules directory is absent

   # ls -ld /lib/modules
   ls: cannot access /lib/modules: No such file or directory

4. KernelCare is half-configured and "apt-get install -f" command fails to complete configuration:

   # dpkg -l kernelcare
   iF  kernelcare       2.14-11 amd64         Tools for KernelCare

5. Repetitive attempts to configure kernelcare package can be found in /var/log/dpkg.log:

   CONFIG_TEXT: 2019-03-13 06:36:40 status unpacked kernelcare:amd64 2.14-11
   2019-03-13 06:36:40 status unpacked kernelcare:amd64 2.14-11
   2019-03-13 06:36:40 status unpacked kernelcare:amd64 2.14-11
   2019-03-13 06:36:40 status half-configured kernelcare:amd64 2.14-11

6. fsmng utility was started several hours or days ago and keeps running:

   # ps auxwww  root    32552  0.0  0.0  33784  9180 ?   S mar21  3:24        \_ /usr/bin/python -Estt /opt/psa/admin/sbin/fsmng --fix-plesk-packages
   root    19004  4.0  0.0  29640  3156 ?        S    11:40  0:00   \_ /usr/bin/apt-get update
   root    19007  0.0  0.0  33100  2144 ?        S    11:40  0:00 \_ /usr/lib/apt/methods/http
   root    19008  0.0  0.0  33096  2148 ?        S    11:40  0:00 \_ /usr/lib/apt/methods/http

Cause

fsmng utility runs "apt-get update" in the loop due to inability to finish KernelCare package configuration. The behavior is Plesk bug PPPM-10348 which will be fixed in future Plesk updates.

Resolution

As a workaround, remove KernelCare extension:

1. Log into Plesk

2. Go to Extensions > My Extensions > KernelCare > Remove

3. Connect to the server via SSH

4. Identify and kill 'fsmng' process

   # killall fsmng

5. Upgrade packages:

   # apt-get upgrade

   If not helped, remove KernelCare package:

   # rm -f /etc/init.d/kcare
   # dpkg --force-all --purge kernelcare

   If KernelCare removal is not acceptable, contact your hosting provider regarding the issue