ClamAV ERROR: Database update process failed: Up-to-date (1)

[chotaire]

Greetings,

since tonight there are issues updating the clamav database. Even deleting daily.cvd did not fix these issues. Following is an excerpt of syslog:

Feb 10 13:52:11 mail freshclam[3783]: freshclam daemon 0.102.1 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64)
Feb 10 13:52:11 mail freshclam[3783]: ClamAV update process started at Mon Feb 10 13:52:11 2020
Feb 10 13:52:11 mail freshclam[3783]: ClamAV update process started at Mon Feb 10 13:52:11 2020
Feb 10 13:52:11 mail freshclam[3783]: daily database available for update (local version: 25719, remote version: 25720)
Feb 10 13:52:11 mail freshclam[3783]: daily database available for update (local version: 25719, remote version: 25720)
Feb 10 13:52:13 mail freshclam[3783]: WARNING: Mirror https://database.clamav.net is not synchronized.
Feb 10 13:52:13 mail freshclam[3783]: Mirror https://database.clamav.net is not synchronized.
Feb 10 13:52:13 mail freshclam[3783]: ERROR: Unexpected error when attempting to update database: daily
Feb 10 13:52:13 mail freshclam[3783]: Unexpected error when attempting to update database: daily
Feb 10 13:52:13 mail freshclam[3783]: WARNING: fc_update_databases: fc_update_database failed: Up-to-date (1)
Feb 10 13:52:13 mail freshclam[3783]: fc_update_databases: fc_update_database failed: Up-to-date (1)
Feb 10 13:52:13 mail freshclam[3783]: ERROR: Database update process failed: Up-to-date (1)
Feb 10 13:52:13 mail freshclam[3783]: Database update process failed: Up-to-date (1)
Feb 10 13:52:13 mail freshclam[3783]: ERROR: Update failed.
Feb 10 13:52:13 mail freshclam[3783]: Update failed.

# clamd --version
ClamAV 0.102.1/25720/Mon Feb 10 12:53:41 2020

Proxmox staff, please note the following and consider:

- Updating to clamav 0.102.2 would ignore this issue
- Clamav 0.102.2 fixes a security issue, it is recommended that Proxmox releases an upgrade anytime soon
- Setting "ScriptedUpdates yes" in /etc/clamav/freshclam.conf fixes this issue, updates will now work properly again.
- Setting "ScriptedUpdates yes" in /etc/clamav/freshclam.conf also greatly reduces network load by no longer downloading the entire database each time, but just downloading a diff, saving 90% of bandwidth.

Note: This also needs to be set in /var/lib/pmg/templates/freshclam.conf.in and needs to be revisited each time there is an actual update for pmg installed as templates become overwritten.

Is there any reason why ScriptedUpdates ist set to no? ClamAV clearly recommends to change this setting to default value. After setting this value, updates work again:

ClamAV update process started at Mon Feb 10 14:11:25 2020
daily.cld database is up to date (version: 25720, sigs: 2181998, f-level: 63, builder: raynman)
main.cvd database is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
bytecode.cvd database is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg)
safebrowsing.cvd database is up to date (version: 49191, sigs: 2213119, f-level: 63, builder: google)

Cheers
Marc

 

[Stoiko Ivanov]

Thanks for the report!
We noticed the issue as well - and will probably release an updated clamav 0.102.2 package to pmgtest soon (it's currently running through a few internal tests).

In general we use the clamav packages provided by debian and do not package this ourselves - since it suits our purposes and provides a larger test-audience.
Indeed debian already uploaded the 0.102.2 version to unstable.

Is there any reason why ScriptedUpdates ist set to no? ClamAV clearly recommends to change this setting to default value. After setting this value, updates work again:

The template has been like this since it's initial import - my guess from my experience with clamav database updates would be that at some point
the incremental db-updates were not working properly (just like in this instance the full downloads have a problem in certain situations)
If you like open an enhancement request over at https://bugzilla.proxmox.com - if it works well for you (over a longer timeframe) we could consider enabling it.

One reason I could think of is that some users use third-party databases - and I'm not sure that all of them work with ScriptedUpdates enabled
(see https://www.clamav.net/documents/private-local-mirrors)

 

[karnz]

Related to ClamAV daily update error below.
Setting "ScriptedUpdates yes" is fixed this issue as well. After two weeks outdated ClamAV signature without any notice.

# freshclam

ClamAV update process started at Mon Feb 24 23:15:06 2020
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.102.1 Recommended version: 0.102.2
DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
daily database available for update (local version: 25721, remote version: 25733)
WARNING: Download failed (28) WARNING:  Message: Timeout was reached7.66MiB/56.40MiB
WARNING: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd
Trying again in 5 secs...
daily database available for update (local version: 25721, remote version: 25733)
WARNING: Download failed (28) WARNING:  Message: Timeout was reached9.78MiB/56.40MiB
WARNING: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd
Trying again in 5 secs...
daily database available for update (local version: 25721, remote version: 25733)
WARNING: Download failed (28) WARNING:  Message: Timeout was reached9.72MiB/56.40MiB
WARNING: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd
Trying again in 5 secs...
daily database available for update (local version: 25721, remote version: 25733)
WARNING: Download failed (28) WARNING:  Message: Timeout was reached9.72MiB/56.40MiB
WARNING: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd
Trying again in 5 secs...
daily database available for update (local version: 25721, remote version: 25733)
ERROR: Download failed (28) ERROR:  Message: Timeout was reached  ] 3.92MiB/56.40MiB
ERROR: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd
Giving up on https://database.clamav.net...
ERROR: Update failed for database: daily
WARNING: fc_update_databases: fc_update_database failed: Connection failed (5)
ERROR: Database update process failed: Connection failed (5)
ERROR: Update failed.

 

[chotaire]

I've seen the same issue. I logged onto the box and issued "freshclam -v" and the update went fine. So it must be an issue within a Proxmox script.
This happened multiple times to me and I was getting really sick of it so once Proxmox updated clamav to 0.102.2 I reverted this change (and set "ScriptedUpdates no" again). No issues since.

 

[hksit]

hello,
is this the official solution? i get same errors on ClamAV Update