Re: [squid-users] Sibling issue
Hi Amos Proxy01 is using version 3.1 and the Proxy02 is using version 2.7 Cheers Chia Wei Notice The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action taken by you in reliance on it, is prohibited and may be unlawful. This email is for communication purposes only. It is not intended to constitute an offer or form a binding agreement. Our company accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided. If you have received this message in error, please delete it and contact the sender immediately. Thank you. Amos Jeffries To squid-users@squid-cache.org 24-11-2011 12:12 cc PM Subject Re: [squid-users] Sibling issue On 22/11/2011 10:43 p.m., Chia Wei LEE wrote: > Hi > > I had an issue when configure the sibling. > below is my configuration in my proxy01 (10.1.1.2) > > cache_peer 10.1.1.8 sibling 3128 0 proxy-only no-query > acl sibling1 src 10.1.1.8 > cache_peer_access 10.1.1.8 deny sibling1 > > > > but when i go to browse Internet, the access.log in my proxy02 (10.1.1.8) > show the below log. > > 22/Nov/2011:17:15:43 +0800248 10.1.1.2 TCP_MISS/404 330 GET > internal://proxy01/squid-internal-periodic/store_digest - NONE/- text/plain > > even my proxy02 already have the related cache, but my proxy01 keep cannot > find the cache and fetch the content from Internet. > > Any idea on this ? Squid version? What do you mean by "have the cache" the storage digest is already finished building by proxy-2? 404 seems a little strange. As does the "://proxy01/" part. AFAIK the request from proxy01 to proxy02 given that above config in any current Squid should be one of: GET internal://10.1.1.8:3128/squid-internal-periodic/store_digest or GET /squid-internal-periodic/store_digest Amos ForwardSourceID:NT976E
Re: [squid-users] Sibling issue
On 22/11/2011 10:43 p.m., Chia Wei LEE wrote: Hi I had an issue when configure the sibling. below is my configuration in my proxy01 (10.1.1.2) cache_peer 10.1.1.8 sibling 3128 0 proxy-only no-query acl sibling1 src 10.1.1.8 cache_peer_access 10.1.1.8 deny sibling1 but when i go to browse Internet, the access.log in my proxy02 (10.1.1.8) show the below log. 22/Nov/2011:17:15:43 +0800248 10.1.1.2 TCP_MISS/404 330 GET internal://proxy01/squid-internal-periodic/store_digest - NONE/- text/plain even my proxy02 already have the related cache, but my proxy01 keep cannot find the cache and fetch the content from Internet. Any idea on this ? Squid version? What do you mean by "have the cache" the storage digest is already finished building by proxy-2? 404 seems a little strange. As does the "://proxy01/" part. AFAIK the request from proxy01 to proxy02 given that above config in any current Squid should be one of: GET internal://10.1.1.8:3128/squid-internal-periodic/store_digest or GET /squid-internal-periodic/store_digest Amos
[squid-users] Sibling issue
Hi I had an issue when configure the sibling. below is my configuration in my proxy01 (10.1.1.2) cache_peer 10.1.1.8 sibling 3128 0 proxy-only no-query acl sibling1 src 10.1.1.8 cache_peer_access 10.1.1.8 deny sibling1 but when i go to browse Internet, the access.log in my proxy02 (10.1.1.8) show the below log. 22/Nov/2011:17:15:43 +0800248 10.1.1.2 TCP_MISS/404 330 GET internal://proxy01/squid-internal-periodic/store_digest - NONE/- text/plain even my proxy02 already have the related cache, but my proxy01 keep cannot find the cache and fetch the content from Internet. Any idea on this ? Cheers Chia Wei Notice The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action taken by you in reliance on it, is prohibited and may be unlawful. This email is for communication purposes only. It is not intended to constitute an offer or form a binding agreement. Our company accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided. If you have received this message in error, please delete it and contact the sender immediately. Thank you.
