Hello list,
I have the a problem with my setup:
Two non-transparent caching backend proxies serving users with failover
using proxy.pac
Both backend are forwarding all traffic to dedicated non-caching squid
parents each.
Each parent is hooked to an ADSL-Line.
If the parents die (host or squi
We use a parent proxy at our ISP and we would like to make our proxy a
parent to another proxy on site.
I note that the ISP proxy has a name.
1) how would we give our proxy a name, or does this just resolve to an IP
address?
2) can we replace the name in the tag line with the IP address of our N
Hello list,
I am a bit confused with the cache_peer setting for multiple parents.
If I use a single no-query/default parent (no ICP) everything is fine.
cache_peer parent1parent 8080 7 no-query no-delay default
But now I want to use multiple parents of that kind in round-robin.
cache_peer pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How can I exclude two ip's and localhost and servers hostname from a parent
node?
I want to get statistics and I doesn't let me. I want to avoid forward loops.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFBbTbpm87SXUGUjPsRAr
On Mon, 10 Oct 2005, [ISO-8859-1] Hendrik Voigtländer wrote:
If the parents die (host or squid crash, network failures) fallback ist
provided with direct access via a third line. Parents are marked down.
How is this done?
Should be more or less the same when the parents fails to resolve..
Henrik Nordstrom wrote:
On Mon, 10 Oct 2005, [ISO-8859-1] Hendrik Voigtländer wrote:
If the parents die (host or squid crash, network failures) fallback
ist provided with direct access via a third line. Parents are marked
down.
How is this done?
3th line is reachable by backends via d
On Thu, 13 Oct 2005, [ISO-8859-1] Hendrik Voigtländer wrote:
Should be more or less the same when the parents fails to resolve..
But in this case the child should fetch direct instead of displaying the
error page?
That is the general intention of Squid request forwarding.
Any opinion abou
Henrik Nordstrom wrote:
On Thu, 13 Oct 2005, [ISO-8859-1] Hendrik Voigtländer wrote:
Should be more or less the same when the parents fails to resolve..
But in this case the child should fetch direct instead of displaying
the error page?
That is the general intention of Squid request
On Mon, 17 Oct 2005, [ISO-8859-1] Hendrik Voigtländer wrote:
Hmm, I still dont get why the child displays the error page when the
parents fails to resolve. I think I will use the workaround with the
line monitoring.
Probably the "wrong" status code is returned by the parent in this
situation
Henrik Nordstrom wrote:
On Mon, 17 Oct 2005, [ISO-8859-1] Hendrik Voigtländer wrote:
Hmm, I still dont get why the child displays the error page when the
parents fails to resolve. I think I will use the workaround with the
line monitoring.
Probably the "wrong" status code is returned by the
On Tue, 18 Oct 2005, [ISO-8859-1] Hendrik Voigtländer wrote:
Ah. So if I use exactly the same build with same time out value on all squid
this would explain this behaviour? Should I perhaps reduce timeout values on
the parents?
You could try.
2 child caches serving users, client distribution
Henrik Nordstrom wrote:
On Tue, 18 Oct 2005, [ISO-8859-1] Hendrik Voigtländer wrote:
Ah. So if I use exactly the same build with same time out value on all
squid this would explain this behaviour? Should I perhaps reduce
timeout values on the parents?
You could try.
I'll give it a shot.
On Wed, 19 Oct 2005, [ISO-8859-1] Hendrik Voigtländer wrote:
Is it advisable to use icp/cache digest for the siblings?
digests by default also uses ICP if there was no hit in the digest.
In terms of latency digest-only is most efficient and is set by the
no-query option without disabling dig
1) Add an entry for your proxy to your DNS.
2) I would use the FQDN. You need DNS anyway.
3) You can use any Port but it must be the same as specified in the
child config.
I prefer same Ports and same visibile hostname on all our proxies,
otherwise I had problems with ftp-Listings going through t
>
>
> Hello list,
>
> I am a bit confused with the cache_peer setting for multiple parents.
> If I use a single no-query/default parent (no ICP) everything is fine.
>
> cache_peer parent1parent 8080 7 no-query no-delay default
>
> But now I want to use multiple parents of that kind i
Elsen Marc wrote:
But only the first parent is used. I expected round-robin
should spread
the requests to both parents.
- How did you 'measure' that observation ?
- configured both parents as described
- squid -k reconfigure
- tailing all access-logs (parents/child) - I have access to all t
> >
> > - How did you 'measure' that observation ?
> - configured both parents as described
> - squid -k reconfigure
> - tailing all access-logs (parents/child) - I have access to
> all three
> machines
>
> > - Squid version ?
> - child and one parent is debian linux with the stable squ
On Fri, 6 Aug 2004, [ISO-8859-1] Hendrik Voigtländer wrote:
- How did you 'measure' that observation ?
- configured both parents as described
- squid -k reconfigure
- tailing all access-logs (parents/child) - I have access to all three
machines
Please try restarting the child instead of "-k reconf
Elsen Marc wrote:
- How did you 'measure' that observation ?
- configured both parents as described
- squid -k reconfigure
- tailing all access-logs (parents/child) - I have access to
all three
machines
- Squid version ?
- child and one parent is debian linux with the stable squid
deb-pac
On Fri, 6 Aug 2004, [ISO-8859-1] Hendrik Voigtländer wrote:
I will try restarting instead of reconfigure as suggested by Henrik,
otherwise it is not worth the hassle (yet).
You may want to pay a visit to
http://www.squid-cache.org/Versions/v2/2.5/bugs/. Most of the Squid-2.5
bugs is relevant to
On Wed, 13 Oct 2004, Costas Zacharopoulos wrote:
How can I exclude two ip's and localhost and servers hostname from a parent
node?
cache_peer_access, or always_direct depending on what it is you actually
want to do.
Regards
Henrik
21 matches
Mail list logo
