Hi,
clamonacc is still blocking my webapp from loading. I've tried
removing clamd from apparmor and running clamd through strace to find
any obvious errors. Nothing has turned up yet except that maybe
something is odd with the /tmp/ directory. If I "OnAccessExcludePath
/tmp/", then everything
On 9/23/21, G.W. Haywood via clamav-users wrote:
> Hi there,
Hi, and thanks!
>
> I would suggest that if you're investigating problems with scanning by
> clamd, which is what clamonacc uses for the scanning, then clamdscan
> might be better a better choice than clamscan for the investigations.
I'm trying to setup ClamAV on a host running Apache and Phusion Passenger.
After bringing up clamd and clamonacc, connecting to the Passenger app (web
browser on 443) will result in various "Daemon failed to scan" and "Not a
regular file ERROR" messages in the logs. It's not always the same file
On Thu, Sep 9, 2021 at 1:45 PM Maarten Broekman
wrote:
> It depends on the OS, but if you have something like AppArmor or
> GrSecurity, you may need to grant the appropriate permissions there to
> allow access even for root.
>
Thanks for the info.
I disabled apparmor (systemctl disable
I'm trying to configure (ClamAV 0.103.2/26289 on Ubuntu 18.04) `clamonacc`
using the instructions here[1]. I got through the steps and tried starting
with `User clamav` but got a lot of permission errors in the logs when a
file was chmod'd 0600:
"/home/user/eicar-test.txt: Can't open file or
