Symptoms:
It is possible that after the recent update of CloudLinux OS on a server with Imunify Software you started getting errors from cron similar to these:
/usr/bin/flock -n /var/run/cloudlinux_domains_collector.cronlock /usr/bin/cloudlinux_domains_collector | /opt/alt/php74-imunify/usr/bin/php -d extension=phar.so -d extension=json.so /opt/app-version-detector/app-version-detector.phar --send-stats --scan-depth=2
=============
Configuration error: Target directory is not specified.
Usage example: php app-version-detector.phar OPTIONS SCAN_DIR
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='UTF-8'>
BrokenPipeError: [Errno 32] Broken pipe
Root cause:
This error is a known issue, and our development team has already fixed it since app-version-detector
Resolution:
The best way to fix the problem is to update to the latest version of app-version-detector package. The version should be equal to or greater than 20.0803-1. You can monitor the updates in our blog
To fix the error by yourself without updating, modify the file /etc/cron.d/cloudlinux_domains_collector
and add two additional parameters (--stdin-dirs --paths-in-base64
) to the command. Like this:
# cat /etc/cron.d/cloudlinux_domains_collector
2 1 5 * * root /usr/bin/flock -n /var/run/cloudlinux_domains_collector.cronlock /usr/bin/cloudlinux_domains_collector | /opt/alt/php74-imunify/usr/bin/php -d extension=phar.so -d extension=json.so /opt/app-version-detector/app-version-detector.phar --send-stats --scan-depth=2 --stdin-dirs --paths-in-base64
Comments
0 comments
Please sign in to leave a comment.