[Pkg-clamav-devel] Bug#749027: Bug#749027: Bug#749027: The ClamAV daemon stops working.

[Scott Kitterman]

On June 5, 2014 6:58:07 PM MDT, Jim Barber <jim.barber at ddihealth.com> wrote:
>On 6/06/2014 2:24 AM, Andreas Cadhalpun wrote:
>> Control: tags -1 fixed-upstream pending
>>
>> Hi Jim,
>>
>> upstream fixed the problem and I have backported the fix for Debian,
>so that it will be included in the next upload.
>>
>> Until then just disable ScanOnAccess to work around the problem.
>>
>> Best regards,
>> Andreas
>
>After reading the discussion on the upstream bug report, it looks like
>perhaps these error messages in the logs were relevant after all...
>
>	-> ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted
>	-> ScanOnAccess: clamd must be started by root
>
>Is ScanOnAccess something that is toggled depending on how you answer
>dpkg
>configuration questions?
>Or is it something I manually need to change in the
>/etc/clamav/clamd.conf ?
>I didn't see a question relevant to it at installation time.
>
>I have done a fresh install of clamav-daemon on a virtual machine and
>ScanOnAccess is set to false.
>To my knowledge I never manually set it to true on the system that I
>have the
>issue with.
>So I can only guess that it was enabled in one of the older
>clamav-daemon
>packages and subsequent upgrades have preserved the setting?
>I've been using this Debian system for many years (I think since around
>2009)
>Either that, or I set it so long ago I just can't remember doing it.
>
>Thanks for all your help resolving the issue Andreas.
>I look forward to the fixed packages appearing in the Debian mirror.
>
ScanOnAccess is new.  We did have some significant issues in the Debconf templates in the release that it was introduced. I thought we cleaned it all up correctly, but maybe not.

Scott K