On 10/17/2014 8:24 am, daniel.rieken@xxxxxxx wrote:
Hello,
Each of the parents are used for both HTTP & HTTPS in this
configuration, the dead parent detected log message isn't going to be
repeated twice as its one parent, Regardless of which method the
traffic
is passing.
yes, that's correct, I agree, each peer is used for both HTTP & HTTPS.
But when I send only HTTPS traffic, squid is *not* logging "DEAD
Parent detected" or "connection to 10.0.0.101:3128 failed".
The log message *only* appears as soon as squid is passing HTTP
traffic.
In my scenario squid is only passing HTTPS-traffic, so I will never
ever see a log message when a Parent dies.
I would expect squid to log a "DEAD Parent" message *once*, regardless
of squid is currently passing HTTP or HTTPS.
Is this a bug? Or am I doing something wrong?
Ah, I see your dilemma, I spun up the test instance I have installed on
my FreeBSD laptop of Squid 3.4.8, configured it to forward to two parent
proxy servers. Then pointed my browser at it using a wpad.dat script
that pointed HTTP traffic at the secondary parent proxy, and HTTPS
traffic to the local test proxy. I created a bogus route entry to the
primary parent proxy, forcing it to appear as dead. Just as you
reported, traffic changed in the access log to listing ANY_OLD_PARENT
and ran out secondary parent proxy server, with no Detected DEAD Parent
log entry.
I then switch the browser from the script to hard coded so both HTTP &
HTTPS traffic went to the local test proxy, as soon as HTTP traffic hit
it, it logged the Detected DEAD Parent in the cache.log. The issue is
repeatable, and well may be a bug in the logging process, unless someone
else can give a reason that it works this way.
--
Thanks,
Dean E. Weimer
http://www.dweimer.net/
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
