You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am seeing segmentation faults under Ubuntu Lucid 10.04 server when scanning with the ClamAV gem. I created a fresh virtual machine fully patched as of today, with a fresh RVM install, fresh Ruby 1.9.3 install and a fresh minimal gemset. Last known working version for me is 0.96.5+dfsg-1ubuntu1.10.04.4
Ubuntu 12.04 does not exhibit the same behavior with the same ClamAV version, but the command line executables for scanning appear to work in both instances.
Kernel Version
Linux lucid64 2.6.32-46-server #108-Ubuntu SMP Thu Apr 11 16:11:15 UTC 2013 x86_64 GNU/Linux
Package Versions
vagrant@lucid64:~$ dpkg -l | grep clamav
ii clamav 0.97.8+dfsg-1ubuntu1.10.04.1 anti-virus utility for Unix - command-line i
ii clamav-base 0.97.8+dfsg-1ubuntu1.10.04.1 anti-virus utility for Unix - base package
ii clamav-freshclam 0.97.8+dfsg-1ubuntu1.10.04.1 anti-virus utility for Unix - virus database
ii libclamav-dev 0.97.8+dfsg-1ubuntu1.10.04.1 anti-virus utility for Unix - development fi
ii libclamav6 0.97.8+dfsg-1ubuntu1.10.04.1 anti-virus utility for Unix - library
Signature Versions
vagrant@lucid64:~$ sudo freshclam
ClamAV update process started at Fri May 3 21:01:17 2013
main.cvd is up to date (version: 54, sigs: 1044387, f-level: 60, builder: sven)
daily.cvd is up to date (version: 17137, sigs: 1208176, f-level: 63, builder: neo)
bytecode.cvd is up to date (version: 214, sigs: 41, f-level: 63, builder: neo)
Gem Versions
vagrant@lucid64:~$ gem list
*** LOCAL GEMS ***
bundler (1.3.5)
clamav (0.4.1)
rake (10.0.4)
rubygems-bundler (1.1.1)
rvm (1.11.3.7)
Executable Versions
vagrant@lucid64:~$ clamscan ~/.profile
/home/vagrant/.profile: OK
----------- SCAN SUMMARY -----------
Known viruses: 2247191
Engine version: 0.97.8
Scanned directories: 0
Scanned files: 1
Infected files: 0
Data scanned: 0.00 MB
Data read: 0.00 MB (ratio 0.00:1)
Time: 9.299 sec (0 m 9 s)
vagrant@lucid64:~$ clamscan --version
ClamAV 0.97.8/17137/Fri May 3 18:39:10 2013
I'm happy to provide any other information needed to debug. Just let me know what you need. I've seen this on a an interim release too (ClamAV 0.97.5) and across a couple other environments as well (VMWare and AWS).
The text was updated successfully, but these errors were encountered:
I was having trouble with segfaults in clamsmtpd. What I discovered is that calmd was running under the user clamav and clamsmtpd was running under a different user. Make sure that they are both running under the same account. In addition, the ctl file is critical, make sure that it matches in both clamd and clamsmtp's configuration.
I am seeing segmentation faults under Ubuntu Lucid 10.04 server when scanning with the ClamAV gem. I created a fresh virtual machine fully patched as of today, with a fresh RVM install, fresh Ruby 1.9.3 install and a fresh minimal gemset. Last known working version for me is 0.96.5+dfsg-1ubuntu1.10.04.4
Ubuntu 12.04 does not exhibit the same behavior with the same ClamAV version, but the command line executables for scanning appear to work in both instances.
Kernel Version
Package Versions
Signature Versions
Gem Versions
Executable Versions
Repro Steps/Stack Trace
I'm happy to provide any other information needed to debug. Just let me know what you need. I've seen this on a an interim release too (ClamAV 0.97.5) and across a couple other environments as well (VMWare and AWS).
The text was updated successfully, but these errors were encountered: