Applicable to:
- Plesk for Linux
Symptoms
-
Email notifications are received daily:
CONFIG_TEXT: run-parts: /etc/cron.daily/imunify360-firewall exited with return code 127
CONFIG_TEXT: Cron root@example.com /usr/bin/flock -n /var/run/shrinker.lock /opt/alt/python35/bin/python3 /opt/alt/modsec-sdbm-util/bin/shrinker.py > /dev/null
flock: failed to execute /opt/alt/python35/bin/python3: No such file or directory
CONFIG_TEXT: /bin/sh: /opt/alt/python35/share/imunify360/scripts/update_components_versions.py: No such file or directory
-
Imunify360 is not installed: the extension does not appear in Plesk at Extensions > My Extensions.
Cause
The daily task from previously installed Imunify360 was not removed.
Resolution
-
Connect to the Plesk server via SSH.
-
Remove the Imunify360 cron tasks:
-
on CentOS/RHEL-based distributions
# rm -f /etc/cron.daily/imunify360-firewall
# rm -f /etc/cron.d/waf_configurator
-
on Debian/Ubuntu-based distributions
# apt-get purge imunify360*
-
Comments
4 comments
Having the same issue here, the suggested solution: apt-get purge imunify360*
does not solve it (still receiving daily cron emails)
Hi Bas de Bruin
You can check what other Imunify cron jobs are still running with the following command:
Then you can remove the files from the paths mentioned in the output.
Hi @...
Thank you. My UNIX knowledge is a little rusty si that why I am using Plesk. Apparently:
- un-installing Imunify doesn't delete these cron entries
- Plesk will not show these cron entries in the Scheduled tasks
Hi Bas de Bruin
>- un-installing Imunify doesn't delete these cron entries
Yes. Removing the extension does not remove the cron tasks. It is needed to remove them manually.
>- Plesk will not show these cron entries in the Scheduled tasks
Some of the package files are installed on the OS directly and thus not managed by Plesk, such as the cron jobs.
Please sign in to leave a comment.