Introduction
Maintaining a CloudLinux server with cPanel requires regular checks and updates to ensure optimal performance and security. This guide delves into advanced troubleshooting steps, common errors, and their resolutions. It also includes critical commands for system management, kernel updates, and service statuses.
Common Errors and Fixes
1. Incorrect Kernel Version
Ensuring your server is using the correct CloudLinux kernel is crucial for stability and performance.
Steps to verify and update the kernel:
1. Check the current kernel version:
uname -r
The output should match the CloudLinux kernel format, e.g., `4.18.0-425.10.1.lve.el8.x86_64`.
2. List installed kernels:
rpm -qa | grep kernel | sort
3. Check default kernel:
grubby --default-kernel
grubby --grub2 --default-title
grubby --default-index
4. Update the kernel if necessary:
yum update kernel
5. Reboot the server to use the new kernel:
reboot
6. Verify the new kernel version after reboot:
uname -r
2. Lvemanager Service Failure
The `lvemanager` service might fail due to missing dependencies or configuration issues. Note that if you are using a control panel like cPanel, the `lvemanager` service is intended for a no-panel server and should be disabled.
Common error message:
ModuleNotFoundError: No module named 'aiohttp_jinja2'
Steps to resolve:
1. Install the required Python modules:
pip install aiohttp_jinja2 aiohttp_session aiohttp_security
2. Reload systemd manager configuration:
systemctl daemon-reload
3. Restart the `lvemanager` service:
systemctl restart lvemanager
4. Check the status of the `lvemanager` service:
systemctl status lvemanager
5. If errors persist, review the configuration file:
cat /usr/share/l.v.e-manager/lvemanager-config.json
6. Reinstall `lvemanager` if necessary:
yum reinstall lvemanager
Important Note:
If you are operating a server with a cPanel control panel, the `lvemanager` service should be disabled:
It appears that `lvemanager` is designed for systems without a control panel, and since your server uses cPanel, it should be disabled. Instead, you should check the status of other LVE services that are relevant for a server with a control panel.
Step 1: Disable the `lvemanager` Service
Disable and stop the `lvemanager` service:
systemctl disable lvemanager
systemctl stop lvemanager
systemctl status lvemanager
Step 2: Check the Status of Other LVE Services
Check the status of the relevant LVE services:
systemctl status lve
systemctl status lvectl
systemctl status lvestats
Additional Steps if Needed
If you find that any of the LVE services are not running or are having issues, you can try restarting them:
systemctl restart lve
systemctl restart lvectl
systemctl restart lvestats
By following these steps, you can ensure that the appropriate LVE services are running correctly on your cPanel server.
This service should be disabled on all servers using control panels.
3. CloudLinux Repository Issues
Incorrect repository configurations can lead to update and installation errors.
Steps to resolve:
1. Reinstall the CloudLinux release package:
dnf reinstall --disablerepo=* --enablerepo=cloudlinux-x86_64-server-9 cloudlinux-release
2. Ensure the repository configuration is correct:
cat /etc/yum.repos.d/cloudlinux.repo
Correct repository configuration:
[cloudlinux]
name=CloudLinux $releasever - Base
baseurl=https://repo.cloudlinux.com/cloudlinux/$releasever/BaseOS/$basearch/os/
enabled=1
gpgcheck=1
gpgkey=https://repo.cloudlinux.com/cloudlinux/RPM-GPG-KEY-CloudLinux
[cloudlinux-updates]
name=CloudLinux $releasever - Updates
baseurl=https://repo.cloudlinux.com/cloudlinux/$releasever/updates/$basearch/
enabled=1
gpgcheck=1
gpgkey=https://repo.cloudlinux.com/cloudlinux/RPM-GPG-KEY-CloudLinux
[cloudlinux-updates-testing]
name=CloudLinux $releasever - Updates Testing
baseurl=https://repo.cloudlinux.com/cloudlinux/$releasever/updates-testing/$basearch/
enabled=0
gpgcheck=1
gpgkey=https://repo.cloudlinux.com/cloudlinux/RPM-GPG-KEY-CloudLinux
3. Clean the YUM cache and update:
yum clean all
yum update
Example Configurations
CloudLinux 9.4 Configuration
cat /etc/os-release
NAME="CloudLinux"
VERSION="9.4 (Vladimir Vasyutin)"
ID="cloudlinux"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.4"
PLATFORM_ID="platform:el9"
PRETTY_NAME="CloudLinux 9.4 (Vladimir Vasyutin)"
ANSI_COLOR="0;34"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:cloudlinux:cloudlinux:9::baseos"
HOME_URL="https://www.cloudlinux.com"
DOCUMENTATION_URL="https://docs.cloudlinux.com"
BUG_REPORT_URL="https://cloudlinux.zendesk.com"
REDHAT_SUPPORT_PRODUCT="CloudLinux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.4"
Kernel Information:
uname -r
5.14.0-427.20.1.el9_4.x86_64
Installed Kernels:
rpm -qa | grep kernel | sort
kernel-5.14.0-362.24.2.el9_3.x86_64
kernel-5.14.0-427.16.1.el9_4.x86_64
kernel-5.14.0-427.20.1.el9_4.x86_64
kernel-core-5.14.0-362.24.2.el9_3.x86_64
kernel-core-5.14.0-427.16.1.el9_4.x86_64
kernel-core-5.14.0-427.20.1.el9_4.x86_64
kernel-headers-5.14.0-427.20.1.el9_4.x86_64
kernel-modules-5.14.0-362.24.2.el9_3.x86_64
kernel-modules-5.14.0-427.16.1.el9_4.x86_64
kernel-modules-5.14.0-427.20.1.el9_4.x86_64
kernel-modules-core-5.14.0-362.24.2.el9_3.x86_64
kernel-modules-core-5.14.0-427.16.1.el9_4.x86_64
kernel-modules-core-5.14.0-427.20.1.el9_4.x86_64
kernel-tools-5.14.0-427.20.1.el9_4.x86_64
kernel-tools-libs-5.14.0-427.20.1.el9_4.x86_64
Default Kernel:
grubby --default-kernel
/boot/vmlinuz-5.14.0-427.20.1.el9_4.x86_64
#### CloudLinux 8.10 Configuration
cat /etc/os-release
NAME="CloudLinux"
VERSION="8.10 (Vladimir Aksyonov)"
ID="cloudlinux"
ID_LIKE="rhel fedora centos"
VERSION_ID="8.10"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CloudLinux 8.10 (Vladimir Aksyonov)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:cloudlinux:cloudlinux:8.10:GA:server"
HOME_URL="https://www.cloudlinux.com/"
BUG_REPORT_URL="https://www.cloudlinux.com/support"
VARIANT_ID="cloudlinux"
```
Kernel Information:
uname -r
4.18.0-425.13.1.lve.el8.x86_64
nstalled Kernels:
rpm -qa | grep kernel | sort
kernel-4.18.0-425.13.1.lve.el8.x86_64
kernel-4.18.0-513.18.1.lve.el8.x86_64
kernel-4.18.0-513.9.1.lve.el8.x86_64
kernelcare-2.88-1.el8.x86_64
kernel-core-4.18.0-425.13.1.lve.el8.x86_64
kernel-core-4.18.0-513.18.1.lve.el8.x86_64
kernel-core-4.18.0-513.9.1.lve.el8.x86_64
kernel-headers-4.18.0-553.lve.el8.x86_64
kernel-modules-4.18.0-425.13.1.lve.el8.x86_64
kernel-modules-4.18.0-513.18.1.lve.el8.x86_64
kernel-modules-4.18.0-513.9.1.lve.el8.x86_64
kernel-tools-4.18.0-553.lve.el8.x86_64
kernel-tools-libs-4.18.0-553.lve.el8.x86_64
```
Default Kernel:
grubby --default-kernel
/boot/vmlinuz-4.18.0-513.18.1.lve.el8.x86_64
Essential Commands for System Management
1. Reload systemd manager configuration:
systemctl daemon-reload
2. Restart and check status of `lvemanager`:
systemctl restart lvemanager
systemctl status lvemanager
3. Enable, start, and check status of `cagefs`:
systemctl enable cagefs
systemctl start cagefs
systemctl status cagefs
4. Check CloudLinux detection and license:
cldetect --detect
cldetect --check-license
5. Check system release information:
cat /etc/os-release
Conclusion
Regular checks and updates are essential for maintaining a stable and secure CloudLinux server with cPanel. This guide provides a comprehensive approach to troubleshooting common issues, ensuring your server remains in optimal condition.
For further assistance, consult the official CloudLinux documentation or contact cPanel support.
