Issue
It was noticed that the Imunify360 service was on status stopped. However, when trying to bring it back online this is what happened:
service imunify360 restart
Redirecting to /bin/systemctl restart imunify360.service
Job for imunify360.service failed because the control process exited with error code. See "systemctl status imunify360.service" and "journalctl -xe" for details.
So an ImportError appears each time on agent usage or package installation:
imunify360-agent version
Traceback (most recent call last):
File "/usr/bin/imunify360-agent", line 33, in <module>
sys.exit(load_entry_point('imunify360-firewall==6.12.2', 'console_scripts', 'imunify360-agent')())
ImportError: cannot import name 'BackupFailed' from 'restore_infected.backup_backends.acronis'
(/opt/imunify360/venv/lib64/python3.8/site-packages/restore_infected/backup_backends/acronis.py)
Which prevents the package from being installed and boils down to an error in the module restore_infected.backup_backends.acronis
(or its absence) having no BackupFailed
name available for importing.
Environment
- CloudLinux (3.10.0-962.3.2.lve1.5.68.el7.x86_64)
- Imunify 360 6.10.1-1
Solution
If force updating using beta repos doesn't resolve the issue with 6.11.2-2 on rpm systems:
rpm -qf /opt/imunify360/venv/lib64/python3.8/site-packages/restore_infected/backup_backends/acronis.py
cloudlinux-backup-utils-4.0.0-1.el8.noarch
The solution is to remove backup-utils first and update Imunify:
yum remove cloudlinux-backup-utils
bash i360deploy.sh --beta
[root@server ~]# imunify360-agent version
6.12.2-1
Useful links
Comments
0 comments
Please sign in to leave a comment.