ImunifyAV failing in newly installed servers
Hello guys, I'm seeing the free ImunifyAV failing in cPanel servers that has been newly deployed. I'm seeing this on cPanel 112 with Almalinux 8.8.
I've tried uninstalling ImunifyAV and reinstalling from command line or from the Security Advisor link, and both end up with a flashy UI saying System Error.
I attached an image so you see how it looks.
Can you tell if it generates any log to check for errors?
Thanks in advance.
-
make sure the service has started run the command 'systemctl status imunify-antivirus' 0 -
If the issue is in the interface, I'd expect something to be logged to /usr/local/cpanel/logs/error_log. You could also try checking /usr/local/cpanel/logs/queueprocd.log to see if there is anything interesting there. 0 -
The service is running apparently... # systemctl status imunify-antivirus ? imunify-antivirus.service - ImunifyAV Loaded: loaded (/usr/lib/systemd/system/imunify-antivirus.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2023-08-23 20:45:20 -03; 1min 24s ago Main PID: 23003 (python3) Tasks: 2 (limit: 49756) Memory: 42.6M CGroup: /system.slice/imunify-antivirus.service ??23003 /opt/imunify360/venv/bin/python3 -m imav.run Aug 23 20:45:20 003226174075.onlinenow.com.ar systemd[1]: Started ImunifyAV.
Also, nothing related to Imunify on /usr/local/cpanel/logs/queueprocd.log nor even on /usr/local/cpanel/logs/error_log. No errors logged on /var/log/imunify360/console.log either. I'm lost and the Imunify team didn't reply to support questions.... Any ideas?0 -
Well, a solution from ImunifyAV team has arrived: simply install alt-python38 and you will be ok. yum install -y alt-python38 I run that and it did the magic. The UI now works. Now.... who's should preinstall that? Imunify or cPanel? both? why is not installed on new servers? Please discuss this internally and assign an internal ticket as this is a bug on both products. 0 -
I checked this on a server that has never had Imunify installed, or CloudLinux, and confirmed that package exists in a default cPanel environment, so I'm wondering if it was actually somehow removed as part of other work. 0 -
Weird thing is that the servers where it failed was just installed that day. Only significant change is that cPanel is installed without WP Toolkit: sh latest --skip-wptoolkit May this impact in a way that alt-python is thereby not installed? 0 -
Let me test and I'll get back to you soon! 0 -
Okay - brand new install of cPanel, on AlmaLInux 8, without CloudLinux - the package isn't there. Ran a "yum update" on the new server - package still isn't there. Installed WordPress Toolkit - package still isn't there. It's also worth noting that the ImunifyAV package was included as part of the base installation. I really don't have a good explanation for why that fix worked on your system. 0 -
Okay - brand new install of cPanel, on AlmaLInux 8, without CloudLinux - the package isn't there. Ran a "yum update" on the new server - package still isn't there. Installed WordPress Toolkit - package still isn't there. It's also worth noting that the ImunifyAV package was included as part of the base installation. I really don't have a good explanation for why that fix worked on your system.
In such scenario, without installing alt-python38, your free ImunifyAV was able to load the UI without issues?0 -
I did some additional testing and confirmed that ImunifyAV installed those packages on my system, although mine are slightly newer than yours it seems as I got 3.11 vs your 3.8: # rpm -qa | grep alt-python alt-python311-setuptools-wheel-65.6.3-1.el8.noarch alt-python27-libs-2.7.16-2.el8.x86_64 alt-python311-pip-wheel-21.3.1-2.el8.noarch alt-python311-3.11.3-1.el8.x86_64 alt-python27-2.7.16-2.el8.x86_64 alt-python311-libs-3.11.3-1.el8.x86_64
These only showed up after the ImunifyAV product was installed.0 -
Then may be a library typo in the installer? This is the outcome in my server: # rpm -qa | grep alt-python alt-python311-pip-wheel-21.3.1-2.el8.noarch alt-python311-setuptools-wheel-65.6.3-1.el8.noarch alt-python38-pip-wheel-20.2.4-1.el8.noarch alt-python27-2.7.16-2.el8.x86_64 alt-python311-libs-3.11.3-1.el8.x86_64 alt-python27-libs-2.7.16-2.el8.x86_64 alt-python38-3.8.12-2.el8.x86_64 alt-python38-setuptools-wheel-57.4.0-1.el8.noarch alt-python38-libs-3.8.12-2.el8.x86_64 alt-python311-3.11.3-1.el8.x86_640 -
It's interesting that the only difference is the 3.8 versions they installed. It would be worth a ticket to our team for sure to clear up the confusion as I can't reproduce that scenario on a test machine, or you could poke the Imunify team again since you're already working with them. 0
Please sign in to leave a comment.
Comments
12 comments