Sven Welzel — Der Blog

Tag: clamav-milter

  • clamav 0.94 finally reaches end of life

    clamav finally sent the end-of-life payload yesterday evening – 0.96 is the current version, so it’s been a good run 🙂

    Possible symptons you experienced:

    • Repeated notifications:WARNING: getpatch: Can't download daily-
    • All freshclam mirrors are ignored
    • Your mailq fills up with detailed MAILER-DAEMON messages referring to the End-of-Life nature of clamav 0.94
    • (… add your own here…)

    But they warned they’d do this in October 2009:

    Starting from 15 April 2010 our CVD will contain a special signature which disables all clamd installations older than 0.95 – that is to say older than 1 year.

    This move is needed to push more people to upgrade to 0.95 .
    We would like to keep on supporting all old versions of our engine, but unfortunately this is no longer possible without causing a disservice to people running a recent release of ClamAV.
    The traffic generated by a full CVD download, as opposed to an incremental update, cannot be sustained by our mirrors. (more…)

  • Clamav errors on upgrade to 0.96 clamd and clamav-milter

    Some updates to the yum-sent clamav-milter.conf and (to a lesser extent) clamd.conf may be necessary.

    After an automatic yum-update of the clamd family on RHEL, there’s a disparity in the way clamav-milter listens and clamd services the socket or port connection — clamav-milter doesn’t know what to go with (local socket on unix:/tmp/clamav.socket or tcp:127.0.0.1) – so you need to tell it. Otherwise, you get messages such as the below in you clamav-milter.log:

    clamav-milter[5149]: No clamd server appears to be available
    ERROR: Failed to initiate streaming/fdpassing

    So make sure the ClamdSocket in clamav-milter.conf points to the LocalSocket that clamd.conf says it’s broadcasting on. So if clamd.conf is

    LocalSocket /tmp/clamd.socket

    clamav-milter.conf should have

    ClamdSocket unix:/tmp/clamd.socket

    Else, if you’re on LocalSocket on 127.0.0.1 on the default port, just set ClamdSocket as below:

    ClamdSocket tcp:127.0.0.1

    Also, be sure to do an sa-update

    Simple, eh? But you knew that already! 🙂