Articles in this section

See more

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

Avatar
Kuzma Ivanov
Updated
Follow
Plesk for Linux kb: technical ABT: Group B

Applicable to:

  • Plesk for Linux

Symptoms

  • 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

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

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*

Comments

6 comments

Sort by Date Votes
  • Avatar
    Bas de Bruin

    Having the same issue here, the suggested solution: apt-get purge imunify360* 

    does not solve it (still receiving daily cron emails)

    0
    Comment actions Permalink
  • Avatar
    Nelson Leiva

    Hi Bas de Bruin

    You can check what other Imunify cron jobs are still running with the following command:

    # grep -ir imunify* /etc/cron*

    Then you can remove the files from the paths mentioned in the output.

    0
    Comment actions Permalink
  • Avatar
    Bas de Bruin

    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

     

    0
    Comment actions Permalink
  • Avatar
    Nelson Leiva

    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.

    0
    Comment actions Permalink
  • Avatar
    DrehPunkt Support

    We had also some zombies of immunify in our cron:

     

    # grep -ir imunify* /etc/cron*
    /etc/cron.d/imunify-notifier:SOURCE=/var/lib/imunify-notifier/imunify-notifier.c ron
    /etc/cron.d/imunify-notifier:TARGET=/etc/cron.d/imunify-notifier
    /etc/cron.d/imunify_scan_schedule:0 3 27 * * root /usr/bin/imunify360-agent malw are user scan --background >/dev/null 2>&1
    /etc/cron.d/waf_configurator:# DO NOT EDIT. AUTOMATICALLY GENERATED BY IMUNIFY36 0.
    /etc/cron.d/waf_configurator:48 4 * * * root /opt/alt/python35/share/imunify360/ scripts/update_components_versions.py

     

    So I deleted these cron jobs (like mentioned above in the KB article):

    # rm /etc/cron.d/waf_configurator
    # rm /etc/cron.d/imunify_scan_schedule
    # rm /etc/cron.d/imunify-notifier
    0
    Comment actions Permalink
  • Avatar
    Kuzma Ivanov

    Hi DrehPunkt Support

    Thanks for sharing the information with us, we've added these cron tasks to the article.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles