-
-
Notifications
You must be signed in to change notification settings - Fork 127
aws-s3-virusscan not processing items from ScanQueue #32
Comments
All logs are reported to CloudWatch Logs. Could you check them for potential errors? |
Thanks Michael, Andrew here: This in var/log/cfn-init.log:
This is from var/log/cloud-init-output.log
This from var/log/secure:
|
can you check |
From
|
Hi @echocentral the entry from Your |
Hi Michael. Here you go. To my eye, not a lot there ...
|
oops I see that was the wrong day. new logs incoming. |
There: those are from 12th March
|
"Socket file /var/run/clamd.scan/clamd.sock could not be bound: No such file or directory" was helpful. Expect a fix shortly.. |
Thank you Michael! Getting the queue processed now. |
After working successfully for several months, aws-s3-virusscan stopped processing items from the ScanQueue on 9/3/2018 at around 5:30 UTC.
The text was updated successfully, but these errors were encountered: