|Main Archive Page > Month Archives > clamav-users archives|
On 05/09/2014 04:41 AM, Shawn Webb wrote:
> On Thu, May 8, 2014 at 10:35 PM, Eric Shubert <firstname.lastname@example.org> wrote:
>> Immediately after upgrading from 0.98 to 0.98.3,
>> when "clamdscan --stdout -V" is run (via simscanmk -g),
>> the clamdscan appears to go into a hard loop (eats a lot of cpu endlessly).
>> Here are non-default config settings:
>> [root@qmt-cos5 etc]# grep -v ^# clamd.conf | grep -v ^$
>> LogClean yes
>> LogVerbose yes
>> LocalSocket /tmp/clamd.socket
>> FixStaleSocket yes
>> Foreground yes
>> ScanMail yes
>> Any ideas?
> Hey Eric,
> I'm having a bit of trouble reproducing the issue here. What OS and what
> version of the OS are you using? What architecture (x86, x64)? What happens
> if you run the clamdscan command manually? Can you paste to a pastebin
> service the output of clamconf and your config.log file?
Hey Shawn. Sorry I didn't include more details.
CentOS 5.10, i386.
I get the same result (looping) when I run "clamdscan --stdout -V" manually.
However, if I start clamd, wait for it to load everything, then run
clamdscan, then clamdscan works. When I stop clamd, try clamdscan again,
then it loops again.
So it appears that when clamd is running, clamdscan works. When clamd
isn't running, clamdscan appears to go into a hard loop (presumably
waiting for something that never happens).
clamconf is at http://pastebin.com/dJAJF8T1
I don't appear to have any config.log. How do I get that?