Bug 164904 - clamav-milter uses 100% cpu
clamav-milter uses 100% cpu
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: clamav (Show other bugs)
3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Enrico Scholz
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-08-02 10:57 EDT by Orion Poplawski
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-02 11:09:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Orion Poplawski 2005-08-02 10:57:12 EDT
Description of problem:
After one of the recent clamav updates I see that clamav-milter uses 100% cpu. 
strace shows a tight loop of:

22272 gettimeofday({1122994371, 371311}, NULL) = 0
22272 clock_gettime(CLOCK_REALTIME, {1122994371, 371339000}) = 0
22272 futex(0x805c958, FUTEX_WAKE, 1)   = 0
22272 open("/var/lib/clamav", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 4
22272 fstat64(4, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
22272 fcntl64(4, F_SETFD, FD_CLOEXEC)   = 0
22272 getdents64(4, /* 6 entries */, 4096) = 192
22272 stat64("/var/lib/clamav/daily.cvd", {st_mode=S_IFREG|0644, st_size=147768,
...}) =
0
22272 stat64("/var/lib/clamav/main.cvd", {st_mode=S_IFREG|0644, st_size=2337370,
...}) =
0
22272 getdents64(4, /* 0 entries */, 4096) = 0
22272 close(4)                          = 0


Version-Release number of selected component (if applicable):
clamav-milter-0.86.2-4.fc3

How reproducible:
everytime

Additional Info:

sysconfig/clamav-milter:
CLAMAV_FLAGS='--max-children=2 -c /etc/clamd.d/milter.conf
local:/var/run/clamav-milter/clamav.sock'
CLAMAV_USER='clamilt'
Comment 1 Orion Poplawski 2005-08-02 11:09:00 EDT
Sorry, my bad.  In attempting to fix the timeout issue with recent updates I
foolishly set ReadTimeout to 0 in the config file.

Note You need to log in before you can comment on or make changes to this bug.