Clamav for old kolabd-1.9.4
Tobias Oed
tobias.oed at octant.org
Tue Apr 20 11:54:41 CEST 2010
On Tue, 2010-04-20 at 11:43 +0200, Gelpi Andrea wrote:
> Gelpi Andrea ha scritto:
> > Michael Harnden ha scritto:
> >> On Sunday 18 April 2010 06:45:03 am Gelpi Andrea wrote:
> >>> Johannes Graumann ha scritto:
> >>>> Liutauras Adomaitis wrote:
> >>>>> On Fri, Apr 16, 2010 at 4:43 PM, Vladislav Tchernev
> >>>>>
> >>>>> <vtchernev at gmail.com>wrote:
> >>>>>> Hi All,
> >>>>>> Sorry if this message has been sent twice.
> >>>>>> I have an old kolab 1.9.4 installation and the clamav(0.88.4) stopped
> >>>>>> working
> >>>>>> last nigh complaining that "This version of the ClamAV engine is
> >>>>>>
> >>>>>> outdated" and finally failing with:
> >>>>>> | LibClamAV Error: Problem parsing signature at line 742
> >>>>>> | LibClamAV Error: Problem parsing database at line 742
> >>>>>>
> >>>>>> | LibClamAV Error: Can't load /tmp/clamav-bc1fd1cd6ce0e0d4/daily.ndb:
> >>>>>> Malformed database
> >>>>>>
> >>>>>> | /tmp/rc-20100416084255-22634/rc.tmp: line 200: 23847 Segmentation
> >>>>>>
> >>>>>> fault /kolab/sbin/clamd --config-file=$clamav_cfgfile
> >>>>>>
> >>>>>> I guess upgrading the clamav will fix the issue. My question is can
> >>>>>> Idownload the latest clamav src rpm from kolab's security-updates,
> >>>>>> build and install the package on my old kolab setup.
> >>>>>>
> >>>>>> We' have several old qmail servers and clamav stoped on them as well.
> >>>>> Clamav on Kolab 2.2.2 works. it seems that format of clamdb has changed
> >>>>> and erlder versions of clamav doesn't understands it. It doesn't answer
> >>>>> your question, but it may be a problem for lots of clamav users.
> >>>> According to an ongoing debian security discussion, clamav below 0.95(?)
> >>>> was inactivated by the last signature-update it loaded. This has been
> >>>> announced long ago by the clamav team (http://tinyurl.com/y7rxco8) ...
> >>>> upgrade!
> >>>>
> >>>> Joh
> >>> For Kolab 2.1.0 where is possible to get a clamav 0.95 ?
> >>> I try clamav 0.95.1 but it requires a new openpkg version.
> >>> Upgrading kolab is the only solution?
> >> I used the upgrade instructions on the wiki with no problems to upgrade my clamav
> >> http://wiki.kolab.org/index.php/Upgrading_Clamav
> >> Mike
> >
> > On kolab 2.1.0 the wiki instruction doesn't solve the problem.
> >
> > I suppose a step is missing.
> >
> > cp clamav.spec /kolab/RPM/SRC/clamav
> >
> >
> > Openpkg version don't match.
> >
> > $ /kolab/bin/openpkg rpmbuild -bb ./clamav.spec
> > error: Failed build dependencies:
> > openpkg >= 20060823 is needed by clamav-0.96-20100420
> >
> > From spec file
> >
> > BuildPreReq: OpenPKG, openpkg >= 20060823, gcc, bzip2, pkgconfig, bc
> > PreReq: OpenPKG, openpkg >= 20060823
> >
> > $ /kolab/bin/openpkg -v
> > OpenPKG-2.5-RELEASE (2.5.4)
> >
> > Is it safe to change it in spec cfile?
> > If yes how?
> >
> >
>
> I try with these lines in spec file
>
> BuildPreReq: OpenPKG, openpkg >= 2.5, gcc, bzip2, pkgconfig, bc
> PreReq: OpenPKG, openpkg >= 2.5
>
> but it does not compile.
>
> checking for gcc bug PR28045... configure: error: your compiler has gcc PR28045 bug, use a
> different compiler, see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28045
> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.22250 (%build)
>
> Ideas?
>
On a couple of kolab 2.1.0, I installed the system's clamav (via debian
packages) then I added
clamav_enable="no"
to /kolab/templates/rc.conf.template
and finally did a ln /var/run/clamav/clamd.ctl /kolab/var/clamav.sock
ugly but it works
Tobias
--
Tobias Oed
Octant Informatique tel: 04 76 50 82 38
La région Rhone Alpes soutient Octant dans le cadre du projet OpenERP.
More information about the users
mailing list