Bug #10183

RPMs are not updating virus definitions

Added by Sarah Romkey almost 6 years ago. Updated over 5 years ago.

Status:Won't fixStart date:08/05/2016
Priority:HighDue date:
Assignee:-% Done:

0%

Category:-
Target version:Release 1.5.1
Google Code Legacy ID: Pull Request:
Sponsored:No Requires documentation:

Description

Testing on http://churumelo.qa.archivematica.org:81/, transfers are failing virus scanning with this failure:

Scan failed for file 451d52e0-5aae-4f17-8861-ff080a8863e5 - Landing zone.jpg
Clamscan RC: 2
Clamscan Standard output:
----------- SCAN SUMMARY -----------
Known viruses: 329783
Engine version: 0.99.2
Scanned directories: 0
Scanned files: 0
Infected files: 0
Data scanned: 0.00 MB
Data read: 0.00 MB (ratio 0.00:1)
Time: 13.982 sec (0 m 13 s)

Clamscan Standard error: LibClamAV Warning: ******************************************
LibClamAV Warning: * The virus database is older than 7 days!
LibClamAV Warning:
Please update it as soon as possible.
LibClamAV Warning: *
******************************************
LibClamAV Error: mpool_malloc(): Can't allocate memory (262144 bytes).
LibClamAV Error: cli_mpool_strdup(): Can't allocate memory (25 bytes).
LibClamAV Error: cli_loadhash: Problem parsing database at line 3245508
LibClamAV Error: Can't load main.mdb: Malformed database
LibClamAV Error: cli_tgzload: Can't load main.mdb
LibClamAV Error: Can't load /var/lib/clamav/main.cvd: Malformed database
LibClamAV Error: cli_loaddbdir(): error loading database /var/lib/clamav/main.cvd
ERROR: Malformed database

Justin tried to run freshclam but it didn't work.

History

#1 Updated by Santiago Collazo almost 6 years ago

That seems a memory problem, I was able to run fresclam without problems.

I'm giving the server 4g, instead of two.

#2 Updated by Santiago Collazo almost 6 years ago

  • Assignee changed from Santiago Collazo to Sarah Romkey

#3 Updated by Justin Simpson over 5 years ago

  • Status changed from New to Won't fix
  • Assignee deleted (Sarah Romkey)

There is a deployment issue here (not having enough memory to run all deployment tasks) but this is not a but in the packaging code, so I am closing the ticket.

Also available in: Atom PDF