I'm not sure but after testing with telnet or\and nc you can try to verify the open files limits on the system which might cause this issue. To identify how many connections are opened to the service you can use netstat or ss tools. netstat -ntp and a similar on ss. Also it's a good practice to put an ICAP periodic(2-20 seconds apparat) with an OPTIONS request to make sure that the service is alive. If you want my testing script let me know. Eliezer ---- Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: eliezer@xxxxxxxxxxxx -----Original Message----- From: squid-users [mailto:squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Alex Rousskov Sent: Thursday, November 2, 2017 19:22 To: Stephen Stark <logic4life@xxxxxxxxx>; squid-users@xxxxxxxxxxxxxxxxxxxxx Subject: Re: Squid 3.5 ICAP Problems On 11/02/2017 10:29 AM, Stephen Stark wrote: > Adaptation::Icap::Xaction::noteCommConnected(local=[::] > remote=127.0.0.1:1344 flags=1, errno=101, ... The logs you have provided do not show where/why exactly the TCP connection to the ICAP service fails, but error number 101 is probably "network unreachable". This is unusual but not impossible for localhost traffic. The next step depends on the failure cause. There are at least two major cases to consider: A) If Squid sends packets to 127.0.0.1:1344, then you can easily reproduce the problem using something like "telnet" or "nc" on the Squid box command line. Just make sure you use the right _source_ IP address for the connection! It has to be the same source IP address that Squid is using. It might not be 127.0.0.1. Running that command as Squid user might also be important if the Squid box have some fancy user-specific networking restrictions. B) If Squid does not send packets to 127.0.0.1:1344, then one can figure out what goes wrong by studying relevant ALL,9 logs. You may also want to address other errors or warnings Squid logs to cache.log (if any). You can determine whether Squid sends packets to 127.0.0.1:1344 by collecting a packet trace (for all Squid box interfaces!) and/or running strace (for the Squid worker process). HTH, Alex. _______________________________________________ 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
