[lee@yun.yagibdah.de: squid: idnsCheckQueue: ID 5: giving up after 1 tries and 4295.4 seconds]
Hi,
nobody on that?
----- Forwarded message from Hans Wilmer <lee@yun.yagibdah.de> -----
Hi!
>From time to time, in unregular intervals, squid seems to be unable to
access remote http servers. I can try to reload a page, but at best
the page is loaded partly, but mott not at all.
When this happens, there's a message in syslog:
squid[26681]: idnsCheckQueue: ID 5: giving up after 1 tries and 4295.4 seconds
There's no timeout before that message appears and the requested page
cannot be loaded. After the message appears the first time, squid
produces a CPU load of up to 20%, even when no clients are connected
and squid seems to do nothing. Restarting squid doesn't help; I have
to reboot the server to get it running again. For some time it runs
just fine then until that error message appears.
The best hint I've found so far is that there could be some problem
with DNS, but it was to no avail because DNS just works fine, doing
all name lookups and reverse lokups without any problem or delay.
Has anybody any idea what might cause this strange behaviour and how I
could solve the problem? Some obscure timing problem maybe?
squid Version 2.4.STABLE6, on Woody, kernel 2.4.18
GH
----- End forwarded message -----
Reply to: