Search squid archive

Re: "NF getsockopt(SO_ORIGINAL_DST)" filling cache.log due to AWS ELB healthchecks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux