Open ghost opened 11 years ago
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.
clamd.conf: LocalSocket /var/run/clamav/clamd.ctl
clamsmtpd.conf PidFile: /var/run/clamsmtpd.pid User: clamav
One might need to alter the ownership for the logs if it fails to start. I hope that this helps someone else out.
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).