clam

intermittent issues with ClamAV clamd INSTREAM on socket

由 别来无恙 提交于 2019-12-22 04:48:15
问题 I've got an AWS Lambda function running NodeJS code to stream files from S3 to ClamAV running on an EC2 instance. Generally (about 75% of the time) the system works, but often (especially when multiple files are being scanned from different Lambda containers) clamd threads gets stuck on INSTREAM . Once a thread has been in INSTREAM for 25-30 seconds it does not seem to be able to recover. When it has been QUEUEDSINCE 350 seconds it is killed off. I can't figure out how either of these numbers

Azure function host dies with OutOfMemoryException, without triggering

由 Deadly 提交于 2019-12-11 06:06:45
问题 Quick version: Why does my function host kill it self after 5 minutes without doing anything? I have an Azure function which uses nClam to scan blob files for viruses. It seems to work just fine, but suddenly it will kill it self even before triggering on any blob! It will just shutdown after 5 minutes with an OutOfMemoryException: [18/9/2019 10:33:33] Host initialized (405ms) [18/9/2019 10:33:33] Host started (812ms) [18/9/2019 10:33:33] Job host started Hosting environment: Production

intermittent issues with ClamAV clamd INSTREAM on socket

由 泪湿孤枕 提交于 2019-12-05 06:40:43
I've got an AWS Lambda function running NodeJS code to stream files from S3 to ClamAV running on an EC2 instance. Generally (about 75% of the time) the system works, but often (especially when multiple files are being scanned from different Lambda containers) clamd threads gets stuck on INSTREAM . Once a thread has been in INSTREAM for 25-30 seconds it does not seem to be able to recover. When it has been QUEUEDSINCE 350 seconds it is killed off. I can't figure out how either of these numbers relate to any value in my config. I'm struggling to find any sign of an error in the logs - the number
订阅 clam