Problems with SpamSnake ClamAV (Sanesecurity Signatures)

Discussion in 'HOWTO-Related Questions' started by tmaleshafske, Sep 21, 2010.

  1. tmaleshafske

    tmaleshafske New Member

    Poking around today I found this set of messages regarding ClamAV

    Code:
    Mon Sep 20 23:35:01 UTC 2010 - Pausing database file updates for 564 seconds...
    
    Mon Sep 20 23:44:25 UTC 2010 - Pause complete, checking for new database files...
    
    ======================================================================
    Sanesecurity Database & GPG Signature File Updates
    ======================================================================
    
    Sanesecurity mirror site used: ws10.freeformit.com 199.231.58.65
    
    Number of files: 18
    Number of files transferred: 0
    Total file size: 11742810 bytes
    Total transferred file size: 0 bytes
    Literal data: 0 bytes
    Matched data: 0 bytes
    File list size: 571
    File list generation time: 0.179 seconds
    File list transfer time: 0.000 seconds
    Total bytes sent: 34
    Total bytes received: 606
    
    sent 34 bytes  received 606 bytes  426.67 bytes/sec
    total size is 11742810  speedup is 18348.14
    
    Testing updated Sanesecurity database file: junk.ndb
    Sanesecurity GPG Signature tested good on junk.ndb database
    Clamscan reports Sanesecurity junk.ndb database integrity tested BAD - SKIPPING
    
    Testing updated Sanesecurity database file: jurlbl.ndb
    Sanesecurity GPG Signature tested good on jurlbl.ndb database
    Clamscan reports Sanesecurity jurlbl.ndb database integrity tested BAD - SKIPPING
    
    Testing updated Sanesecurity database file: phish.ndb
    Sanesecurity GPG Signature tested good on phish.ndb database
    Clamscan reports Sanesecurity phish.ndb database integrity tested BAD - SKIPPING
    
    Testing updated Sanesecurity database file: rogue.hdb
    Sanesecurity GPG Signature tested good on rogue.hdb database
    Clamscan reports Sanesecurity rogue.hdb database integrity tested BAD - SKIPPING
    
    Testing updated Sanesecurity database file: sanesecurity.ftm
    Sanesecurity GPG Signature tested good on sanesecurity.ftm database
    Clamscan reports Sanesecurity sanesecurity.ftm database integrity tested BAD - SKIPPING
    
    Testing updated Sanesecurity database file: scam.ndb
    Sanesecurity GPG Signature tested good on scam.ndb database
    Clamscan reports Sanesecurity scam.ndb database integrity tested BAD - SKIPPING
    
    Testing updated Sanesecurity database file: spamimg.hdb
    Sanesecurity GPG Signature tested good on spamimg.hdb database
    Clamscan reports Sanesecurity spamimg.hdb database integrity tested BAD - SKIPPING
    
    Testing updated Sanesecurity database file: winnow_malware.hdb
    Sanesecurity GPG Signature tested good on winnow_malware.hdb database
    Clamscan reports Sanesecurity winnow_malware.hdb database integrity tested BAD - SKIPPING
    
    Testing updated Sanesecurity database file: winnow_malware_links.ndb
    Sanesecurity GPG Signature tested good on winnow_malware_links.ndb database
    Clamscan reports Sanesecurity winnow_malware_links.ndb database integrity tested BAD - SKIPPING
    
    No Sanesecurity database file updates found
    
    ======================================================================
    SecuriteInfo Database File Updates
    ======================================================================
    
    4 hours have not yet elapsed since the last SecuriteInfo update check
    
         --- No update check was performed at this time ---
    
    Next check will be performed in approximately 3 hour(s), 18 minute(s)
    
    ======================================================================
    MalwarePatrol Database File Update
    ======================================================================
    
    6 hours have not yet elapsed since the last MalwarePatrol download
    
         --- No database download was performed at this time ---
    
    Next download will be performed in approximately 5 hour(s), 18 minute(s)
    
    ======================================================================
    
    =============================================================
    = No update(s) detected, ClamAV databases were not reloaded =
    =============================================================
    Now I have double checked all configuration files and everything is inline with the tutorial. Anybody have any ideas in regard to the failures of the integrity tests.
     

Share This Page