Symptoms
You may experience issues with LVE-related features and may see errors similar to the following.
Error: current running kernel is NOT supported.
[Sat Jul 10 07:23:07.237759 2021] [lsapi:error] [pid 1212322] [client 198.51.100.2:38836] mod_lsapi: [host domain.tld] [req GET / HTTP/1.1] Connect to backend failed: connect to lsphp failed: 110
(lvestats) [ERROR] Can't detect LVE version; [Errno 2] No such file or directory: '/proc/lve/list'
Description
This can be caused by a non-LVE kernel being used. You can check this with the following command.
grep "Kernel command line: BOOT_IMAGE=" /var/log/messages
This will list the kernels used for recent reboots and will look similar to the following.
Jul 10 11:18:18 hostname kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.10.0-1062.1.2.el7.x86_64 root=UUID=ef0ca717-b580-42e8-b609-e929b5234713 ro crashkernel=auto rhgb net.ifnames=0 biosdevname=0
Jul 10 11:35:54 hostname kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.10.0-1062.1.2.el7.x86_64 root=UUID=ef0ca717-b580-42e8-b609-e929b5234713 ro crashkernel=auto rhgb net.ifnames=0 biosdevname=0
Jul 10 11:53:37 hostname kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.10.0-962.3.2.lve1.5.56.el7.x86_64 root=LABEL=root ro crashkernel=auto rhgb net.ifnames=0 biosdevname=0 LANG=en_US.UTF-8
If the most recent kernel used (the bottom line) Does not show "lve", then a non-LVE kernel is in use and LVE-related features will not function properly.
Workaround
The boot kernel will need to be changed to use an LVE kernel. The article below describes how to do this.
Configure the boot Kernel CentOS7