I think this is because Squid has received at least one bad response from your ICAP server while it was down. As a result it has decided not to talk to your ICAP server for a period of time If you want Squid to ignore outages on your ICAP server and always attempt a request you can set icap_service_failure_limit -1 Setting this to -1 tells Squid to always connect to ICAP, setting a positive number indicates the number of failures allowed before Squid stops communicating with Squid. The period of time that Squid stops talking to ICAP is controlled by 'icap_service_revival_delay', it is a minimum of 30 seconds I think. >I'm using Squid 3.0.STABLE19-1 with c-icap - replacing an existing >"sandwich" setup of squid2-dansguardian-squid2. > >To my great amazement, things seem to work flawlessly. > >But... when I'm restarting c-icap, squid reports: > >--- snip --- >The following error was encountered while trying to retrieve the URL: http://www.google.de/ig?hl=de >ICAP protocol error. >The system returned: [No Error] >This means that some aspect of the ICAP communication failed. >Some possible problems are: >The ICAP server is not reachable. >An Illegal response was received from the ICAP server. >--- snip --- > >And that's although c-icap is already running again. >Issuing an "squid3 -k reconfigure" solves the problem. > >But why? How can I prevent the need to do that? > >-- >Ralf Hildebrandt > Geschäftsbereich IT | Abteilung Netzwerk > Charité - Universitätsmedizin Berlin > Campus Benjamin Franklin > Hindenburgdamm 30 | D-12203 Berlin > Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 > ralf.hildebrandt@xxxxxxxxxx | http://www.charite.de > This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
