On 1/17/2020 1:39 PM, Matus UHLAR - fantomas wrote:
>>> On 17.01.20 12:25, Bowie Bailey wrote:
>>>> I just upgraded from ClamAV 101.4 to 102.1 on CentOS 7.4.  Clam runs fine 
>>>> (through
>>>> avfilter for Courier), but when I run freshclam, I get an error:
>>>>
>>>> # freshclam
>>>> freshclam: error while loading shared libraries: libfreshclam.so.2: cannot 
>>>> open
>>>> shared object file: No such file or directory
>>>>
>>>> # ll /usr/local/lib64/libfreshclam.*
>>>> -rwxr-xr-x. 1 root root   1134 Jan 17 12:01 
>>>> /usr/local/lib64/libfreshclam.la
>>>> lrwxrwxrwx. 1 root root     21 Jan 17 12:01 
>>>> /usr/local/lib64/libfreshclam.so ->
>>>> libfreshclam.so.2.0.0
>>>> lrwxrwxrwx. 1 root root     21 Jan 17 12:01 
>>>> /usr/local/lib64/libfreshclam.so.2 ->
>>>> libfreshclam.so.2.0.0
>>>> -rwxr-xr-x. 1 root root 481680 Jan 17 12:01 
>>>> /usr/local/lib64/libfreshclam.so.2.0.0
>
>> On 1/17/2020 1:03 PM, Matus UHLAR - fantomas wrote:
>>> uninstall system version of clamav.
>>>
>>> or, better, uninstall your version of clamav and get one from repository
>>> that provides current clamav for centos7
>
> On 17.01.20 13:11, Bowie Bailey wrote:
>> I don't have a system version of clamav.
>>
>> I had 101.4 installed and working (compiled from source).  I downloaded 
>> 102.1 from
>> clamav.net and built it using the standard build procedure.  I have 
>> installed clam
>> this way for years without any problems.
>
> was the 0.101.4 installed the same way as 0.102.1 ? Did you uninstall it 
> before
> installing 0.102.1?

It was installed exactly the same way except for an extra --disable-clamonacc 
flag on
./configure.

> there may be problem in the sandard build process of 0.102.1 for centos
> try running ldd `which freshclam` and it should show where it searches for
> libfreshclam

Here are the first several lines:

# ldd `which freshclam`
        linux-vdso.so.1 =>  (0x00007ffed21c6000)
        libssl.so.10 => /lib64/libssl.so.10 (0x00007f9a54ec6000)
        libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f9a54a65000)
        libclamav.so.9 => /usr/local/lib64/libclamav.so.9 (0x00007f9a54689000)
        libfreshclam.so.2 => not found
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f9a54470000)
        libcurl.so.4 => /lib64/libcurl.so.4 (0x00007f9a54206000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f9a53ff0000)
       
It says 'not found', but libfreshclam.so.2 lives in the same directory as the
libclamav.so.9 that it did find.  The dates indicate that the file is part of 
the
build that was installed today (same with the freshclam binary).  Is there 
something
I can change on the build to specify the file location?

> however, I prefer using installing from sane package maintainers.
> I don't know how does the redhat (and thus centos) clamav support work, but
> Debians's usually works perfectly

I have always preferred to build ClamAV and SpamAssassin from source so I don't 
have
to wait on the packages.  I just got a bit behind on ClamAV this time because I 
had
to wait for avfilter to be updated to work with ClamAV 102.

-- 
Bowie


_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to