[Pkg-clamav-devel] Bug#785203: clamav-freshclam: ERROR: Can't create temporary directory

[Andreas Cadhalpun]

Control: forcemerge 777219 -1

Hi Rob,

On 13.05.2015 14:56, Rob Mason wrote:
> This error appears against 'freshclam', but I believe its related to
> clamav-base.
> 
> Following a dist-upgrade of clamav, the /var/lib/clamav directory
> ownership is reset to 'clamav'. This behaviour is incorrect if clamav
> has been configured to run under a different UID such as 'defang'.
> 
> My scenario:
> 
> In /etc/clamd.conf, 'User' and 'LocalSocketGroup' are set to 'defang'.
>  'AllowSupplementaryGroups' is set to 'false'

This is OK.

> In /etc/freshclam.conf, 'DatabaseOwner' is set to 'defang'

This should not be necessary.

> Following an 'apt-get dist-upgrade' the output of
> '/var/log/clamav/freshclam.log' shows:
> 
> Wed May 13 13:14:42 2015 -> Update process terminated
> Wed May 13 13:14:46 2015 -> --------------------------------------
> Wed May 13 13:14:46 2015 -> freshclam daemon 0.98.7 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64)
> Wed May 13 13:14:46 2015 -> ERROR: Can't create temporary directory /var/lib/clamav/clamav-9cf028fe3f1d39c22fb44fa7e4f18bdf.tmp
> Wed May 13 13:14:46 2015 -> Hint: The database directory must be writable for UID 112 or GID 114
> Wed May 13 13:14:46 2015 -> --------------------------------------
> 
> Workaround is to manually change ownership back to the actual
> DatabaseOwner following a dist-upgrade.

The short answer is that a DatabaseOwner different than clamav
is not supported by the Debian package, because it requires to
manually chown /var/lib/clamav, which should not be done.

This has already been discussed in bug #777219 [1], so I'm
merging it with this bug.

If you think there is a convincing reason to support changing
DatabaseOwner, please let us know and we can unarchive/reopen
bug #777219.

Best regards,
Andreas


1: https://bugs.debian.org/777219