Hi Alex, I got the issue after trying telnet, there was an iptable rule which was blocking the outbount request to the remote icap server which was causing the error. I removed the rule and now it works fine. Thanks for your time and help Anil ---------- Forwarded message ---------- From: Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> Date: Thu, Dec 12, 2013 at 8:20 PM Subject: Re: Need help on squid configuration with remote icap server To: Anil Kapu <anil.kapu@xxxxxxxxx> On 12/11/2013 11:00 PM, Anil Kapu wrote: > I did try pinging 192.168.10.9, and it was successful. Is there any > other configuration parameter I'm missing on the Squid proxy? Please keep the discussion on the mailing list. Please answer both of my questions (ping and telnet), preferably by pasting commands output. We will go from there. Alex. > On Thu, Dec 12, 2013 at 1:21 AM, Alex Rousskov > <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> wrote: >> On 12/11/2013 04:17 AM, Anil Kapu wrote: >> >>> Following is the setup: >>> I have setup Squid on 192.168.10.8 and ICAP server on 192.168.10.9, on >>> 192.168.10.8 in squid.conf file I have provided "icap_service >>> service_req reqmod_precache routing=on bypass=1 icap://<icap server >>> ip>:1344/url_check_module". >>> >>> When I try to open any URL on the machine where squid is setup I get >>> following error in squid log "optional ICAP service is down after an >>> options fetch failure: icap://192.168.10.9:1344/url_check_module >>> [down,!opt]" (I have setup my iptables to route all the http traffic >>> to squid port 3128) >> >> Your Squid cannot get an ICAP OPTIONS response from the ICAP server. >> What happens when, on the Squid box, you do: >> >> $ ping 192.168.10.9 >> >> and >> >> $ telnet 192.168.10.9 1344 >> >> >> Thank you, >> >> Alex. >> >>> icap_enable on >>> icap_service service_req reqmod_precache routing=on bypass=1 >>> icap://192.168.10.9:1344/url_check_module >>> adaptation_access service_req allow all >>> icap_service_failure_limit -1 >>
