Re: [squid-users] ICAP Error
On 24/07/2014 10:46 a.m., Roman Gelfand wrote: > I am getting an error, below, when when attempting to bring up > http://ads.adfox.ru/173362/goLink?. > > How can I troubleshoot this? > > > 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. > > > > > Generated Wed, 23 Jul 2014 22:53:21 GMT by websap.masmid.com (squid) > The ICAP server has bugs. If "websap.masmid.com" is your Squid server look at the ICAP protocol coming back from the ICAP server on these requests. That will require either "debug_options ALL,1 93,9" in squid.conf or a "tcdump -s0" traffic trace. Otherwise there is nothing you can do except report it to the administrator of "websap.masmid.com". Amos
[squid-users] ICAP Error
I am getting an error, below, when when attempting to bring up http://ads.adfox.ru/173362/goLink?. How can I troubleshoot this? ERROR The requested URL could not be retrieved The following error was encountered while trying to retrieve the URL: http://ads.adfox.ru/173362/goLink? 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. Generated Wed, 23 Jul 2014 22:53:21 GMT by websap.masmid.com (squid)
Re: [squid-users] ICAP Error
Hey Roman, Can you get the output for ICAP debug sections and access.log output? use "debug_options ALL,1 93,6" this will give more information on the ICAP issue. in a case of HTTPS requests there is no way to use ICAP on these requests else then the basic "CONNECT" request which is either IP+port or DOMAIN+port. Are you bumping the SSL traffic on this squid instance? Eliezer On 10/27/2013 04:28 PM, Roman Gelfand wrote: For 99.9% of the sites, my icap services are working, There instances where I am getting the following icap error. Not sure as to how to start debugging it. I am using the latest squid and icap versions. The following error was encountered while trying to retrieve the URL: https://www.flowroute.com/accounts/login/ 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. Thanks in advance
[squid-users] ICAP Error
For 99.9% of the sites, my icap services are working, There instances where I am getting the following icap error. Not sure as to how to start debugging it. I am using the latest squid and icap versions. The following error was encountered while trying to retrieve the URL: https://www.flowroute.com/accounts/login/ 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. Thanks in advance
Re: [squid-users] ICAP-Error: ICAP_ERR_GONE (noteInitiatorAborted: Initiator gone before ICAP transaction ended)
Hi Alex With your explanation, I was able to reproduce the behaviour: -> I opened a website within the browser -> Before the site was loaded completely, I closed the browser -> This causes squid to close the current icap-transaction (as you described) (-> ABORT-entries in the access.log) -> In the icap-log, I have the icap-error mentioned in my first post. So, this behaviour makes now sense. Probably the icap-daemon (third-party software) could be advised, not to throw an error but rather an informational message. Thanks a lot for your help and hints. Kind regards, Tom On Fri, Jun 21, 2013 at 5:13 PM, Alex Rousskov wrote: > On 06/21/2013 02:05 AM, Tom Tom wrote: >> Hi >> >> Running squid 3.3.4 as an icap-client: >> >> Sometimes, I got on our ICAP-server (runs on the same box as squid) >> errors like: "ERROR write error: Connection reset by peer" > ... >> For me, the following lines seems curious: >> 2013/06/21 09:46:31.756 kid4| Xaction.cc(488) noteInitiatorAborted: >> Initiator gone before ICAP transaction ended >> 2013/06/21 09:46:31.756 kid4| Xaction.cc(503) setOutcome: ICAP_ERR_GONE > >> In the access.log, the error behaves like this: >> [Fri Jun 21 09:46:31 2013].756 0 10.xx.xx.xx NONE_ABORTED/000 0 >> GET http://www9.dict.cc/img/amtop1.gif USER HIER_NONE/- - >> >> The behaviour seems not to be reproducable. But it occurs n-times a >> hour. I also tried with set "icap_persistent_connections off". But >> this results in the same manner. > > Sounds like the HTTP client disconnected from Squid, forcing Squid to > abort related ICAP (and possibly server-side HTTP) transactions. This is > normal, but your ICAP server decided to complain about it. Ignore this > unless something does not appear to work for your HTTP clients. > > > HTH, > > Alex. >
Re: [squid-users] ICAP-Error: ICAP_ERR_GONE (noteInitiatorAborted: Initiator gone before ICAP transaction ended)
On 06/21/2013 02:05 AM, Tom Tom wrote: > Hi > > Running squid 3.3.4 as an icap-client: > > Sometimes, I got on our ICAP-server (runs on the same box as squid) > errors like: "ERROR write error: Connection reset by peer" ... > For me, the following lines seems curious: > 2013/06/21 09:46:31.756 kid4| Xaction.cc(488) noteInitiatorAborted: > Initiator gone before ICAP transaction ended > 2013/06/21 09:46:31.756 kid4| Xaction.cc(503) setOutcome: ICAP_ERR_GONE > In the access.log, the error behaves like this: > [Fri Jun 21 09:46:31 2013].756 0 10.xx.xx.xx NONE_ABORTED/000 0 > GET http://www9.dict.cc/img/amtop1.gif USER HIER_NONE/- - > > The behaviour seems not to be reproducable. But it occurs n-times a > hour. I also tried with set "icap_persistent_connections off". But > this results in the same manner. Sounds like the HTTP client disconnected from Squid, forcing Squid to abort related ICAP (and possibly server-side HTTP) transactions. This is normal, but your ICAP server decided to complain about it. Ignore this unless something does not appear to work for your HTTP clients. HTH, Alex.
[squid-users] ICAP-Error: ICAP_ERR_GONE (noteInitiatorAborted: Initiator gone before ICAP transaction ended)
Hi Running squid 3.3.4 as an icap-client: Sometimes, I got on our ICAP-server (runs on the same box as squid) errors like: "ERROR write error: Connection reset by peer" On the squid-side, I enabled "debug_options 93,4". In case of the error above, I have the following output in the cache.log: 2013/06/21 09:46:31.755 kid4| AccessCheck.cc(96) check: start checking 2013/06/21 09:46:31.755 kid4| AccessCheck.cc(118) checkCandidates: has 1 rules 2013/06/21 09:46:31.755 kid4| AccessCheck.cc(184) callBack: 0xaf35a0*2 2013/06/21 09:46:31.755 kid4| client_side_request.cc(865) noteAdaptationAclCheckDone: 0xf34848 adaptationAclCheckDone called 2013/06/21 09:46:31.755 kid4| Launcher.cc(43) launchXaction: launching first xaction #1 2013/06/21 09:46:31.755 kid4| Xaction.cc(52) Xaction: Adaptation::Icap::ModXact constructed, this=0x75e51b8 [icapxjob69293] 2013/06/21 09:46:31.755 kid4| ServiceRep.cc(116) getConnection: got connection: local=127.0.0.1:50493 remote=127.0.0.1:1344 FD 25 flags=1 2013/06/21 09:46:31.755 kid4| AsyncCall.cc(18) AsyncCall: The AsyncCall Adaptation::Icap::Xaction::noteCommConnected constructed, this=0x79495e0 [call649456] 2013/06/21 09:46:31.755 kid4| AsyncCall.cc(85) ScheduleCall: Xaction.cc(127) will call Adaptation::Icap::Xaction::noteCommConnected(local=127.0.0.1:50493 remote=127.0.0.1:1344 FD 25 flags=1, data=0x75e51b8) [call649456] 2013/06/21 09:46:31.755 kid4| AsyncCallQueue.cc(51) fireNext: entering Adaptation::Icap::Xaction::noteCommConnected(local=127.0.0.1:50493 remote=127.0.0.1:1344 FD 25 flags=1, data=0x75e51b8) 2013/06/21 09:46:31.755 kid4| AsyncCall.cc(30) make: make call Adaptation::Icap::Xaction::noteCommConnected [call649456] 2013/06/21 09:46:31.755 kid4| AsyncJob.cc(117) callStart: Adaptation::Icap::ModXact status in: [FD 25;rw(1)P(0)G/R job69293] 2013/06/21 09:46:31.755 kid4| AsyncCall.cc(18) AsyncCall: The AsyncCall Adaptation::Icap::Xaction::noteCommRead constructed, this=0xc23770 [call649459] 2013/06/21 09:46:31.755 kid4| AsyncCall.cc(18) AsyncCall: The AsyncCall Adaptation::Icap::Xaction::noteCommWrote constructed, this=0x790be70 [call649461] 2013/06/21 09:46:31.755 kid4| AsyncJob.cc(146) callEnd: Adaptation::Icap::ModXact status out: [FD 25wr;rw(2)G/RP(ieof) job69293] 2013/06/21 09:46:31.755 kid4| AsyncCallQueue.cc(53) fireNext: leaving Adaptation::Icap::Xaction::noteCommConnected(local=127.0.0.1:50493 remote=127.0.0.1:1344 FD 25 flags=1, data=0x75e51b8) 2013/06/21 09:46:31.756 kid4| AsyncCall.cc(85) ScheduleCall: IoCallback.cc(127) will call Adaptation::Icap::Xaction::noteCommWrote(local=127.0.0.1:50493 remote=127.0.0.1:1344 FD 25 flags=1, data=0x75e51b8) [call649461] 2013/06/21 09:46:31.756 kid4| AsyncCallQueue.cc(51) fireNext: entering Adaptation::Icap::Xaction::noteCommWrote(local=127.0.0.1:50493 remote=127.0.0.1:1344 FD 25 flags=1, data=0x75e51b8) 2013/06/21 09:46:31.756 kid4| AsyncCall.cc(30) make: make call Adaptation::Icap::Xaction::noteCommWrote [call649461] 2013/06/21 09:46:31.756 kid4| AsyncJob.cc(117) callStart: Adaptation::Icap::ModXact status in: [FD 25wr;rw(2)G/RP(ieof) job69293] 2013/06/21 09:46:31.756 kid4| AsyncJob.cc(146) callEnd: Adaptation::Icap::ModXact status out: [FD 25r;rG/RwP(ieof) job69293] 2013/06/21 09:46:31.756 kid4| AsyncCallQueue.cc(53) fireNext: leaving Adaptation::Icap::Xaction::noteCommWrote(local=127.0.0.1:50493 remote=127.0.0.1:1344 FD 25 flags=1, data=0x75e51b8) 2013/06/21 09:46:31.756 kid4| AsyncJob.cc(49) deleteThis: ConnStateData will NOT delete in-call job, reason: ConnStateData::connStateClosed 2013/06/21 09:46:31.756 kid4| Xaction.cc(488) noteInitiatorAborted: Initiator gone before ICAP transaction ended 2013/06/21 09:46:31.756 kid4| Xaction.cc(503) setOutcome: ICAP_ERR_GONE 2013/06/21 09:46:31.756 kid4| AsyncCall.cc(48) cancel: will not call Adaptation::Icap::Xaction::noteCommRead [call649459] because comm_read_cancel 2013/06/21 09:46:31.756 kid4| AsyncCall.cc(48) cancel: will not call Adaptation::Icap::Xaction::noteCommRead [call649459] also because comm_read_cancel 2013/06/21 09:46:31.756 kid4| ServiceRep.cc(131) putConnection: RST-closing [FD 25;rG/RwP(ieof)S job69293] 2013/06/21 09:46:31.756 kid4| Xaction.cc(60) ~Xaction: Adaptation::Icap::ModXact destructed, this=0x75e51b8 [icapxjob69293] For me, the following lines seems curious: 2013/06/21 09:46:31.756 kid4| Xaction.cc(488) noteInitiatorAborted: Initiator gone before ICAP transaction ended 2013/06/21 09:46:31.756 kid4| Xaction.cc(503) setOutcome: ICAP_ERR_GONE In the access.log, the error behaves like this: [Fri Jun 21 09:46:31 2013].756 0 10.xx.xx.xx NONE_ABORTED/000 0 GET http://www9.dict.cc/img/amtop1.gif USER HIER_NONE/- - The behaviour seems not to be reproducable. But it occurs n-times a hour. I also tried with set "icap_persistent_connections off". But this results in the same manner. Any hints/solutions for this? Kind regards, Tom
[squid-users] icap error
Hello, i have activated icap but now i always have this error: (i use symantec antivirus) [EMAIL PROTECTED] local]# squid/sbin/squid -d -s -N -f squid/etc/squid.conf 2004/07/06 16:34:59| Starting Squid Cache version 2.5.STABLE5-CVS for i686-pc-linux-gnu... 2004/07/06 16:35:23| assertion failed: icap_respmod.c:843: "icapHttpReplyHdrState(icap) == 2" Aborted Schweizer Laurent
