After a recent CloudLinux update, Python Selector and other related features stopped working. Attempting to use Python Selector in cPanel or CLI produced this error
CloudLinux Official Doc but it wont help me : https://cloudlinux.zendesk.com/hc/en-us/articles/21103017760540-Error-in-Python-application-IndexError-string-index-out-of-range-Traceback
Error in Python application
IndexError: string index out of range
Traceback (most recent call last):
…
Root Cause
The issue was introduced by a buggy release of lvemanager
— specifically:
lvemanager.noarch 7.11.24-1.el8.cloudlinux
In this version:
- Critical configuration or cache files were missing or mislocated, such as:
/usr/share/l.v.e-manager/lvemanager/cache/users.json
/usr/share/l.v.e-manager/panelless-version/lvemanager/config.json
- The Python Selector could not function due to broken internal state or missing cache.
- Services relying on
lvemanager
logic, like Selector, silently failed or produced Python exceptions.
Diagnosis Steps
- Checked the LVE Manager service:
systemctl status lvemanager
Output showed:inactive (dead)
- Looked for JSON/config files:
ls /usr/share/l.v.e-manager/lvemanager/cache/
Result:No such file or directory
- Checked package availability:
yum --enablerepo=* list lvemanager --showduplicates | grep 7.11.24
Output:lvemanager.noarch 7.11.24-1.el8.cloudlinux cloudlinux-updates-testing
This confirmed that the problematic version came from thecloudlinux-updates-testing
repo.
Solution (Fix)
- Removed broken version:
yum remove lvemanager
2. Installed stable version (from working server or previous release):
yum install lvemanager-7.11.23 --enablerepo=cloudlinux-x86_64-server-8
(You can also download the RPM manually from another server or CloudLinux repo mirror)
3. Restarted related services:
systemctl restart lvemanager
cagefsctl –force-update
4. Python Selector started working again, and the “IndexError” was gone.
Leave a Comment