clamscan issues

4 posts / 0 new
Last post
#1 Mon, 02/16/2009 - 20:56
anwoke8204

clamscan issues

Hi, I just had to re-isntall, we had a power surge and it killed the server, I installed and ran the check utility that comes up in the yellow bar on first login and got the following error on clam av [code:1] The ClamAV program clamscan does not appear to be working properly :

LibClamAV Warning: *********************************************************** LibClamAV Warning: *** This version of the ClamAV engine is outdated. *** LibClamAV Warning: *** DON'T PANIC! Read http://www.clamav.net/support/faq *** LibClamAV Warning: *********************************************************** stdin: OK *** glibc detected *** clamscan: double free or corruption (!prev): 0x0b45fd00 *** ======= Backtrace: ========= /lib/tls/i686/cmov/libc.so.6[0xb7dd1a85] /lib/tls/i686/cmov/libc.so.6(cfree+0x90)[0xb7dd54f0] /usr/lib/libclamav.so.3(cli_bm_free+0x4b)[0xb7eda6db] /usr/lib/libclamav.so.3(cl_free+0x113)[0xb7edda63] clamscan[0x804eba1] clamscan[0x804c5f0] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7d7c450] clamscan[0x8049c41] ======= Memory map: ======== 08048000-08053000 r-xp 00000000 08:01 390112 /usr/bin/clamscan 08053000-08054000 rw-p 0000b000 08:01 390112 /usr/bin/clamscan 08054000-0bc69000 rw-p 08054000 00:00 0 [heap] b7900000-b7921000 rw-p b7900000 00:00 0 b7921000-b7a00000 ---p b7921000 00:00 0 b7aa9000-b7abd000 r-xp 00000000 08:01 2867361 /lib/tls/i686/cmov/libnsl-2.7.so b7abd000-b7abf000 rw-p 00013000 08:01 2867361 /lib/tls/i686/cmov/libnsl-2.7.so b7abf000-b7ac1000 rw-p b7abf000 00:00 0 b7ac1000-b7ae5000 rw-p b7ae3000 00:00 0 b7ae6000-b7aef000 r-xp 00000000 08:01 2867365 /lib/tls/i686/cmov/libnss_files-2.7.so b7aef000-b7af1000 rw-p 00008000 08:01 2867365 /lib/tls/i686/cmov/libnss_files-2.7.so b7af1000-b7af9000 r-xp 00000000 08:01 2867367 /lib/tls/i686/cmov/libnss_nis-2.7.so b7af9000-b7afb000 rw-p 00007000 08:01 2867367 /lib/tls/i686/cmov/libnss_nis-2.7.so b7afb000-b7b02000 r-xp 00000000 08:01 2867362 /lib/tls/i686/cmov/libnss_compat-2.7.so b7b02000-b7b04000 rw-p 00006000 08:01 2867362 /lib/tls/i686/cmov/libnss_compat-2.7.so b7b04000-b7b43000 rw-p b7b04000 00:00 0 b7ced000-b7cf7000 r-xp 00000000 08:01 2867216 /lib/libgcc_s.so.1 b7cf7000-b7cf8000 rw-p 0000a000 08:01 2867216 /lib/libgcc_s.so.1 b7cfc000-b7cfd000 rw-p b7cfc000 00:00 0 b7cfd000-b7d40000 r-xp 00000000 08:01 390102 /usr/lib/libgmp.so.3.4.2 b7d40000-b7d41000 rw-p 00042000 08:01 390102 /usr/lib/libgmp.so.3.4.2 b7d41000-b7d50000 r-xp 00000000 08:01 2867326 /lib/libbz2.so.1.0.4 b7d50000-b7d51000 rw-p 0000f000 08:01 2867326 /lib/libbz2.so.1.0.4 b7d51000-b7d65000 r-xp 00000000 08:01 387020 /usr/lib/libz.so.1.2.3.3 b7d65000-b7d66000 rw-p 00013000 08:01 387020 /usr/lib/libz.so.1.2.3.3 b7d66000-b7eaf000 r-xp 00000000 08:01 2867354 /lib/tls/i686/cmov/libc-2.7.so b7eaf000-b7eb0000 r--p 00149000 08:01 2867354 /lib/tls/i686/cmov/libc-2.7.so b7eb0000-b7eb2000 rw-p 0014a000 08:01 2867354 /lib/tls/i686/cmov/libc-2.7.so b7eb2000-b7eb6000 rw-p b7eb2000 00:00 0 b7eb6000-b7eca000 r-xp 00000000 08:01 2867370 /lib/tls/i686/cmov/libpthread-2.7.so b7eca000-b7ecc000 rw-p 00013000 08:01 2867370 /lib/tls/i686/cmov/libpthread-2.7.so b7ecc000-b7ece000 rw-p b7ecc000 00:00 0 b7ece000-b7f4f000 r-xp 00000000 08:01 390106 /usr/lib/libclamav.so.3.0.4 b7f4f000-b7f58000 rw-p 00080000 08:01 390106 /usr/lib/libclamav.so.3.0.4 b7f58000-b7f59000 rw-p b7f58000 00:00 0 b7f5b000-b7f5f000 rw-p b7f5b000 00:00 0 b7f5f000-b7f60000 r-xp b7f5f000 00:00 0 [vdso] b7f60000-b7f7a000 r-xp 00000000 08:01 2867217 /lib/ld-2.7.so b7f7a000-b7f7c000 rw-p 00019000 08:01 2867217 /lib/ld-2.7.so bfcb5000-bfcc9000 rwxp bffeb000 00:00 0 [stack] bfcc9000-bfcca000 rw-p bffff000 00:00 0

[/code:1] anyone know how I resolve this

many thanks

Mon, 02/16/2009 - 23:03
Joe
Joe's picture

This looks like a memory failure. Is this the same system that crashed? I think maybe we know why. ;-)

I'm working on a new ClamAV package (for CentOS--we don't provide ClamAV on the Debian-based platforms), as we speak, which will correct the version warning...but it won't fix the seg fault that's the real problem.

--

Check out the forum guidelines!

Mon, 02/16/2009 - 23:42 (Reply to #2)
anwoke8204

it could be bad memory, memory could be the cause of the crash, but the same day my router and the wireless side of my modem died as well. could have been due to a power surge, but all of the other machines in the house were fine, so it could have just been that circut as the modem, router, and server that crashed were all on the same line. will get the memory replaced and see if that resolves the issue.

many thanks

Tue, 02/17/2009 - 00:12 (Reply to #3)
Joe
Joe's picture

Try memtest on the system first (several bootable "rescue" CDs have memtest as one of their boot options). It's a great way to be sure you're replacing the right component--it's possible hard disk problems could also lead to this error, if swap memory were in use for any part of the clamav process. Hard disks tend to go bad more often than memory...so it's worth being sure. All Linux systems will have badblocks available for testing the disk(s).

--

Check out the forum guidelines!

Topic locked