Page 1 of 3

libclamav.so error after New ClamAV v0.93

Posted: 15 Apr 2008, 13:11
by fransonline
Hi,

I upgraded in MSFE ClamAV to 0.93 af information on the blog.

After this, ClamAV refuses to start and reports:
error while loading shared libraries: libclamav.so.4: cannot open shared object file: No such file or directory
In /usr/local/lib I see:
lrwxrwxrwx 1 root root 18 Apr 15 13:36 libclamav.so.4 -> libclamav.so.4.0.1*
-rwxr-xr-x 1 root root 1421764 Apr 15 13:36 libclamav.so.4.0.1*
Further information:
ldd `which freshclam`
linux-gate.so.1 => (0x00beb000)
libclamav.so.4 => not found
libresolv.so.2 => /lib/libresolv.so.2 (0x00d40000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00c6c000)
libc.so.6 => /lib/libc.so.6 (0x00110000)
libz.so.1 => /usr/lib/libz.so.1 (0x00c82000)
/lib/ld-linux.so.2 (0x00aed000)
My system: Fedora 5, cPanel/WHM and latest MSFE

Don't know what is wrong.:confused:

Thanks in advance.

Frans

Posted: 15 Apr 2008, 14:12
by Sarah
Hi Frans,

Try running the following commands in ssh:

ldconfig
freshclam
service clamd restart

Regards,
Sarah

Posted: 16 Apr 2008, 09:21
by fransonline
Hi Sarah,

Thanks for your help.
ClamAV is working again now!:)

Frans

Posted: 16 Apr 2008, 13:03
by gtgeorge
We were having a similar error and just tried the same commands found here which now shows ClamAV is upgraded but fails to start with

Code: Select all

Stopping clamd: [FAILED]
Starting clamd: ERROR: Please define server type (local and/or TCP).
[FAILED]
Also tailing the mail log shows

Code: Select all

Apr 16 07:59:28 pph MailScanner[7687]: Virus and Content Scanning: Starting 
Apr 16 07:59:28 pph MailScanner[8507]: Cannot find Socket (/tmp/clamd) Exiting! 

Posted: 16 Apr 2008, 14:07
by Sarah
Are you running the latest version of the MSFE? What OS and version of cPanel?

Posted: 16 Apr 2008, 14:39
by gtgeorge
Yes running the latest MSFE and using WHM 11.15.0 cPanel 11.18.3-R21703
CENTOS Enterprise 4.6 i686 on standard - WHM X v3.1.0 and Apache/2.2.8

Reading other posts I checked /tmp and there is no clamd I restarted Exim and Mailscanner with the same results which is not creating the temp dir.

Posted: 17 Apr 2008, 07:04
by ccccanada
I tried running those commands and received the following

root@ns10 [/home/admin]# ldconfig
bash: ldconfig: command not found
root@ns10 [/home/admin]# freshclam
freshclam: error while loading shared libraries: libclamav.so.4: cannot open shared object file: No such file or directory
root@ns10 [/home/admin]# service clamd restart
bash: service: command not found

Posted: 17 Apr 2008, 07:29
by gtgeorge
gtgeorge wrote:Yes running the latest MSFE and using WHM 11.15.0 cPanel 11.18.3-R21703
CENTOS Enterprise 4.6 i686 on standard - WHM X v3.1.0 and Apache/2.2.8

Reading other posts I checked /tmp and there is no clamd I restarted Exim and Mailscanner with the same results which is not creating the temp dir.
Found an empty clamd.conf and empty clamd.conf.old.

I edited in the stock .conf file from a download package and changed Mailscanner config to use the new /tmp/clamd.socket and it is now working. Sure would be nice to know exactly what happened though :confused:

Posted: 17 Apr 2008, 08:45
by Sarah
ccccanada wrote:I tried running those commands and received the following

root@ns10 [/home/admin]# ldconfig
bash: ldconfig: command not found
root@ns10 [/home/admin]# freshclam
freshclam: error while loading shared libraries: libclamav.so.4: cannot open shared object file: No such file or directory
root@ns10 [/home/admin]# service clamd restart
bash: service: command not found
Were you logged in as root? Looks like you may have logged in as admin and su'd to root. If you do this you need to be sure to use "su -" and not just "su" in order to set up the root environment correctly.

Posted: 17 Apr 2008, 08:46
by Sarah
gtgeorge wrote:Found an empty clamd.conf and empty clamd.conf.old.

I edited in the stock .conf file from a download package and changed Mailscanner config to use the new /tmp/clamd.socket and it is now working. Sure would be nice to know exactly what happened though :confused:
That's interesting. Thanks for reporting what you found, it gives folks another thing to look for when they run into this problem.