[squid-users] Squid 3.5 ICAP Problems

Stephen Stark logic4life at gmail.com
Fri Nov 3 21:45:01 UTC 2017


Hello,
I found put my problem.

c-icap service was running fine.
I had a modification on FwdState.cc that was not handling any localhost
request. So it squid could not resolve host.

Thanks for the help! It helped me find where the problem was using debug
options ALL,9.


On Nov 3, 2017 11:41 AM, "Alex Rousskov" <rousskov at measurement-factory.com>
wrote:

On 11/03/2017 08:16 AM, Flashdown wrote:

> So I guess I need to set the right debug options for you guys, but that
> would create a very big log file since it takes days or weeks until this
> issue is happening. Any suggestions on what you think how I can do
> debugging in the best way?

You can turn detailed debugging on when the problem re-appears. Search
Squid wiki for "-k debug" for a related discussion and advice.

However, for performance issues, it is best to try to isolate the
bottleneck _before_ slowing down Squid with detailed debugging. That is
difficult to do and there are no scripted actions to follow, but you can
start by logging (access.log and icap.log) various response times and
the number of open connections (/proc/ or netstat -n) to narrow down
suspects.


HTH,

Alex.
_______________________________________________
squid-users mailing list
squid-users at lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20171103/f6e05ee9/attachment-0001.html>


More information about the squid-users mailing list