TQ

Possibly doable. I'd probably have to dig into the scan script and add a progress bar into it.

FYI: Bumped Clam versions this morning. Now is clamav 0.103.0-r1

First post on this page :) ...that's just clamav trying to notify the clamav daemon (not running) about its scan results.

You're welcome, and I'm glad it's been useful. I think I've found something that might be what's occurring in your case. One issue is you might not have enough ram to process this particular file. It's a stretch, but a possible cause. To address the timeout, you should be able to pass a command line variable --bytecode-timeout=[time in ms] I've never had this issue, so let us know if this works and/or is helpful. Source: StackExchange

FYI: Bumped Clam versions last night. Should now be clamav 0.102.4-r1

Probably. ClamAV utilizes only 1 core as to not crush your machine when it's scanning. So for 6500 directories and 69,000 files, it might take a while.

Thanks Dave. I've updated the clamav version as well as added the clamav-unrar libs. 2020-05-23T12:25:05+0000 ClamAV process starting Updating ClamAV scan DB ClamAV update process started at Sat May 23 12:25:06 2020 daily database available for download (remote version: 25820) Time: 1.6s, ETA: 0.0s [=============================>] 63.14MiB/63.14MiB Testing database: '/var/lib/clamav/tmp.319e6/clamav-d7cb4002549b22ae34aa0e790e0def2a.tmp-daily.cvd' ... Database test passed. daily.cvd updated (version: 25820, sigs: 2462534, f-level: 63, builder: raynman) main database available for download (remote version: 59) Time: 2.5s, ETA: 0.0s [=============================>] 112.40MiB/112.40MiB Testing database: '/var/lib/clamav/tmp.319e6/clamav-d10a40146f6be5d2f5a27ad8e3da72d6.tmp-main.cvd' ... Database test passed. main.cvd updated (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr) bytecode database available for download (remote version: 331) Time: 0.2s, ETA: 0.0s [=============================>] 289.44KiB/289.44KiB Testing database: '/var/lib/clamav/tmp.319e6/clamav-40ed796077acdbd8f6d30c39d900f873.tmp-bytecode.cvd' ... Database test passed. bytecode.cvd updated (version: 331, sigs: 94, f-level: 63, builder: anvilleg) WARNING: Clamd was NOT notified: Can't connect to clamd through /run/clamav/clamd.sock: No such file or directory Freshclam updated the DB ClamAV 0.102.3/25820/Fri May 22 12:21:08 2020 Scanning /scan ----------- SCAN SUMMARY ----------- Known viruses: 7016614 Engine version: 0.102.3 Scanned directories: 30 Scanned files: 47 Infected files: 0 Data scanned: 0.54 MB Data read: 0.32 MB (ratio 1.66:1) Time: 35.471 sec (0 m 35 s) Updated on Github and Dockerhub.

The unrar errors: I'll fix in just a moment. The clamd.sock error; no, that's just clamav trying to notify the clamav daemon (not running) about its scan results.

It should pick it up the next time it scans through. Derp. Its actually at 0.102.1-rc0 which is the latest for 3.11 Alpine (not edge) https://pkgs.alpinelinux.org/package/v3.11/main/x86_64/clamav

Just bumped it to clamav (0.101.5-r0) on dockerhub.

It is disabled by default. Logic says yes, but bonding introduces lots of room for problems if its not configured properly. I had to help a friend troubleshoot their UnRAID server the other day and we had to use the unraid-gui boot option to actually be able to login to the web interface and see what network setting was preventing his server from working properly. You might give this a try.

I think the config looks clean (from what I can tell). Maybe its something in the bond0 config that is making the network connection to it unstable or undesirable.

What does the console say? Can you ssh into it? What are the last 100 lines from syslog? Sent from a small phone with phat phingers

Latest version has the option to run UID/GID to address this behavior. I'm not sure if it ever got updated in CA. @Squid can you verify? I should have fixed the invalid xml.

Done.

Unraid version now has UID/GID environment variables in there. Sent from my iPhone using Tapatalk

Just noting that now this image uses Alpine resulting in a much smaller image size. Enjoy and no viruses!

Yes. It will work on any docker install.

Overview: Support for Docker image tquinnelly/clamav-alpine which uses clamav, freshclam, and clamscan to scan your array. Application: ClamAV https://www.clamav.net/ Docker Hub: https://hub.docker.com/r/tquinnelly/clamav-alpine GitHub: https://www.github.com/tquizzle/clamav-alpine Expectations: This container will run when started, scan, then stop. If you want to scan again, just start it again. Notification script from Squid: Logs This container logs to stdout. To see the logs you will have to execute the docker logs command. docker logs ClamAV Buy me a coffee?