Re: [squid-users] Pegging CPU with epoll_wait

Henrik Nordstrom wrote:
>> restarting squid (maybe a few hours or a few days), it starts pegging
>> the CPU at 100%. Running strace on the squid processes scrolls:
>>
>> epoll_wait(3, {}, 256, 0) = 0
>>
>> as fast as my screen will scroll. Restarting squid makes it settle down
>> again for a while.
>>
>
> ... then file a bug report and attach your cache.log file.
>

It happened again, and bug #2296 has been filed. FYI, squidclient reports:

# squidclient -p 80 mgr:events
HTTP/1.0 200 OK
Server: squid/2.6.STABLE6
Date: Fri, 04 Apr 2008 16:41:22 GMT
Content-Type: text/plain
Expires: Fri, 04 Apr 2008 16:41:22 GMT
Last-Modified: Fri, 04 Apr 2008 16:41:22 GMT
X-Cache: MISS from revproxy.bryanlgh.org
X-Cache-Lookup: MISS from revproxy.bryanlgh.org:80
Via: 1.0 revproxy.bryanlgh.org:80 (squid/2.6.STABLE6)
Connection: close

Last event to run: storeClientCopyEvent

Operation Next Execution Weight Callback Valid?
storeClientCopyEvent 0.000000 seconds 0 yes
storeClientCopyEvent 0.000000 seconds 0 yes
storeClientCopyEvent 0.000000 seconds 0 yes
MaintainSwapSpace 0.449644 seconds 1 N/A
ipcache_purgelru 5.780025 seconds 1 N/A
fqdncache_purgelru 9.699383 seconds 1 N/A
storeDirClean 13.604307 seconds 1 N/A
statAvgTick 43.007845 seconds 1 N/A
peerClearRR 102.739505 seconds 0 yes
peerClearRR 102.739505 seconds 0 yes
peerClearRR 102.739505 seconds 0 yes
peerClearRR 102.739505 seconds 0 yes
peerClearRR 102.739505 seconds 0 yes
peerClearRR 102.739505 seconds 0 yes
peerClearRR 102.739505 seconds 0 yes
peerRefreshDNS 2868.335948 seconds 1 N/A
User Cache Maintenance 3102.819286 seconds 1 N/A
storeDigestRebuildStart 3103.252835 seconds 1 N/A
storeDigestRewriteStart 3103.278672 seconds 1 N/A
peerDigestCheck 141057.508629 seconds 1 yes