Email notifications are received daily from a Plesk server: /etc/cron.daily/imunify360-firewall exited with return code 127

Symptoms

• Imunify360 is not installed: the extension does not appear in Plesk at Extensions > My Extensions.

• Plesk administrator receives the following email notifications every day:

  CONFIG_TEXT: run-parts: /etc/cron.daily/imunify360-firewall exited with return code 127

  ---

  CONFIG_TEXT: /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

  ---

  CONFIG_TEXT: failed to execute /opt/alt/python38/bin/python3: No such file or directory

Cause

Imunify360 daily tasks have not been removed along with Imunify360 extension.

Resolution

1. Connect to the Plesk server via SSH.

2. Remove the Imunify360 cron tasks:

   • on CentOS/RHEL-based distributions

     # rm -f /etc/cron.daily/imunify360-firewall

     # rm -f /etc/cron.d/waf_configurator

     # rm -f /etc/cron.d/imunify-notifier

     # rm -f /etc/cron.d/imunify_scan_schedule

   • on Debian/Ubuntu-based distributions

     # apt-get purge imunify360*