louis gonzales wrote:
I need help understanding what the following cache.log information
means? Please.
2009/04/09 00:35:08| The request GET
http://unified1.abstract.net:80/tc/fms/513901874/mygroup/FSC_unified1_Administrator
is ALLOWED, because it matched 'FMS'
2009/04/09 00:35:08| peerSourceHashSelectParent: Calculating hash for
192.168.0.1
A request came in, was allowed, and then passed on to a cache_peer.
2009/04/09 00:35:08| The reply for GET
http://unified1.abstract.net/tc/fms/513901874/mygroup/FSC_unified1_Administrator
is ALLOWED, because it matched 'all'
The reply came back ...
2009/04/09 00:35:08| clientReadRequest: FD 12: no data to process
((10035) WSAEWOULDBLOCK, Resource temporarily unavailable.)
.. then something goes wrong before the reply body was finished
transferring. Possibly the peer disconnected or aborted the link.
I don't know of the top of my head what "(10035) WSAEWOULDBLOCK"
indicates. A search should tell you.
Two minutes later a cache index exchange is done with that same peer...
2009/04/09 00:36:59| peerDigestRequest:
http://192.168.0.1/squid-internal-periodic/store_digest key:
53E0FFBD42B9AFDF6F0027179BE8F121
2009/04/09 00:36:59| peerDigestFetchAbort: peer 192.168.0.1, reason: Bad Request
... but fails.
2009/04/09 00:36:59| temporary disabling (Bad Request) digest from 192.168.0.1
2009/04/09 00:36:59| fwdAbort:
http://192.168.0.1/squid-internal-periodic/store_digest
Ten minutes later another attempt is made at cache index exchange ...
2009/04/09 00:46:59| peerDigestRequest:
http://192.168.0.1/squid-internal-periodic/store_digest key:
53E0FFBD42B9AFDF6F0027179BE8F121
2009/04/09 00:46:59| peerDigestFetchAbort: peer 192.168.0.1, reason: Bad Request
2009/04/09 00:46:59| temporary disabling (Bad Request) digest from 192.168.0.1
2009/04/09 00:46:59| fwdAbort:
http://192.168.0.1/squid-internal-periodic/store_digest
... it fails again.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
Current Beta Squid 3.1.0.6
