Ok, thanks - that works and i see that a sibling becomes some request
for caches.
But if i stop the local apache on a server and ask over the server the
website - squid sad
2007/05/10 08:10:30| Detected DEAD Parent: 127.0.0.1
2007/05/10 08:10:30| TCP connection to 127.0.0.1/80 failed
Thats ok
add no-query to cache_peer line !
i think this 'solve' ...
On 5/10/07, Marcel Alburg [EMAIL PROTECTED] wrote:
Ok, thanks - that works and i see that a sibling becomes some request
for caches.
But if i stop the local apache on a server and ask over the server the
website - squid sad
My cache peer lines look like this
On first server:
cache_peer 127.0.0.1parent 80 0 originserverno-query default
cache_peer server2sibling 80 3130 proxy-only no-delay allow-miss
name=server2
On second server:
cache_peer 127.0.0.1parent 80 0 originserverno-query
My cache peer lines look like this
On first server:
cache_peer 127.0.0.1parent 80 0 originserverno-query default
cache_peer server2sibling 80 3130 proxy-only no-delay allow-miss
name=server2
On second server:
cache_peer 127.0.0.1parent 80 0 originserverno-query
tor 2007-05-10 klockan 10:11 +0200 skrev Marcel Alburg:
But if i stop the local apache on a server and ask over the server the
website - squid sad
2007/05/10 08:10:30| Detected DEAD Parent: 127.0.0.1
2007/05/10 08:10:30| TCP connection to 127.0.0.1/80 failed
Thats ok
but the result is
Hello,
my Networks looks like
Internet
|
[LB] -ha- [LB]
| |
+-+
| |
| |
[Squid +
1. your cache sibling configuration is wrong; you're not contacting
any of the sibling.
2. use the proxy-only flag if you don't want squid to store cache
hits from the siblings.
try something like
cache_peer sibling1 sibling 80 3130 proxy-only no-delay allow-miss
name=sibling1
mike
At
