Why are you using an intercept port?
IF you don't need it you dont't.
Every time any direct conneciton is done to the proxy port 3128 it will
show this line since the connection is a regular TCP one while the
"intercept" directive instructs squid to fetch information which exists
only on NATTED\REDIRECT traffic.
Pretty simple and straight forward and this is the way squid works..
You should verify if you need a http_port 1111 or http_port 1111 accel
or http_port 1111 intercept.
I will be glad to help you in about 20 hours.
Eliezer
On 29/10/2015 02:06, John Smith wrote:
Hi Eliezer,
I've added a single line to my squid.conf:
http_port 3130
And I've modified my AWS ELB healthcheck to monitor port 3130 instead of
3128.
Now my instances are still in the ELB, and the proxy still works as
expected, AND the amount of garbage errors in the cache.log has been
significantly reduced.
Unfortunately I'm seeing a single a single line in cache.log every time I
hit the proxy on port 3128:
2015/10/28 23:53:32| IpIntercept.cc(137) NetfilterInterception: NF
getsockopt(SO_ORIGINAL_DST) failed on FD 61: (92) Protocol not available
From other posts, it appears this warning message related to NAT. I'm not
doing NAT on the squid proxies, the load balancer takes care of that.
Any ideas how to remove the rest of the noise from my logs?
Thanks again for the help!
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
