clamdscan exits with status code 127 about aws-s3-virusscan HOT 8 CLOSED

hi! When you say you looked at /var/log/messages you where on the EC2 machine? If yes, can you run the following command clamdscan /path/to/some.file and see if this works?

from aws-s3-virusscan.

Hi,

No, I viewed the messages file in CloudWatch Logs. I didn't deploy the template with SSH access but I'll try to change that now.

from aws-s3-virusscan.

Looks like clamdscan isn't present:

[ec2-user@ip-10-100-38-224 ~]$ clamdscan /tmp/hi.txt
-bash: clamdscan: command not found

from aws-s3-virusscan.

I released a new version. Can you check if this works for you?

from aws-s3-virusscan.

That works! Thanks very much! Looking forward to using this solution.

from aws-s3-virusscan.

@michaelwittig I am having the same issue with an installation that has been working fine for 6 months, then when autoscaling replaced an unhealthy instance this error has been occuring. I can also see
bash: clamdscan: command not found

How do i perform an update without using the cloudformation script?

from aws-s3-virusscan.

The only supported way is to use the CloudFormation template.

from aws-s3-virusscan.

@michaelwittig We are running into the same issue - initial deployment was months ago with everything working fine. As of the last autoscale, the new ec2 instance is throwing the same error: clamdscan: command not found with error code 127.

Is it possible to fix this on our current deployments/ec2 instances without updating our cloudformation template? Would we be able to do a yum update or config update for clam.d-conf for example?

What is the root cause of the new autoscaled instances not finding clamd?

Thanks in advance for your advice.

from aws-s3-virusscan.