[squid-users] While using icap_service squid working when ip is used and failing when domain name is provided

[prudhvisagar]

*Thanks a lot for replying back* 

*"From the cache logs i see that its failing:" *

2019/08/13 01:08:02.809| 14,3| Address.cc(389) lookupHostIP: Given Non-IP
'domainnameofvirusscanner': Name or service not known
Address.cc(389) lookupHostIP: Given Non-IP 'domainnameofvirusscanner': Name
or service not known
essential ICAP service is down after an options fetch failure:
icap://domainnameofvirusscanner:1344/SYMCScanReq-AV [down,!opt]

*"At a diffrent location i can also see that internal dns was able to
resolve the addresses. "
"this domain name is a alb in aws, I am able to connect to the instance IP
under the ALB through squid"*

2019/08/13 01:08:02.852| 78,6| dns_internal.cc(1053) idnsCallback: Merging
DNS results domainnameofvirusscanner A has 3 RR, AAAA has 1 RR
2019/08/13 01:08:02.852| 45,9| cbdata.cc(321) cbdataInternalFree:
0x55a43f8b7218
2019/08/13 01:08:02.852| 45,9| cbdata.cc(338) cbdataInternalFree: Freeing
0x55a43f8b7218
2019/08/13 01:08:02.852| 78,6| dns_internal.cc(1086) idnsCallback: Sending 4
(OK) DNS results to caller.
2019/08/13 01:08:02.852| 45,9| cbdata.cc(492) cbdataReferenceValid:
0x55a43f85aaf8
2019/08/13 01:08:02.852| 45,9| cbdata.cc(426) cbdataInternalUnlock:
0x55a43f85aaf8=0
2019/08/13 01:08:02.852| 45,9| cbdata.cc(321) cbdataInternalFree:
0x55a43f85aaf8
2019/08/13 01:08:02.852| 45,9| cbdata.cc(338) cbdataInternalFree: Freeing
0x55a43f85aaf8
2019/08/13 01:08:02.852| 14,3| ipcache.cc(362) ipcacheParse: 4 answers for
'domainnameofvirusscanner'
2019/08/13 01:08:02.852| 14,3| ipcache.cc(420) ipcacheParse:
domainnameofvirusscanner #0 10.55.10.2
2019/08/13 01:08:02.852| 14,3| ipcache.cc(420) ipcacheParse:
domainnameofvirusscanner #1 10.55.10.3

----------

Squid error messages: 

One more error i found was 
2019/08/13 01:08:02.812| 20,3| store.cc(499) setReleaseFlag:
StoreEntry::setReleaseFlag: '[null_store_key]'
----------
2019/08/13 01:08:02.810| 93,5| AsyncJob.cc(123) callStart:
Adaptation::Icap::ServiceRep status in:[down,!opt,fetch]
2019/08/13 01:08:02.810| 45,9| cbdata.cc(492) cbdataReferenceValid:
0x5534xa43f8b9324ddb8
2019/08/13 01:08:02.810| 45,9| cbdata.cc(492) cbdataReferenceValid:
0x5534xa43f8b9324ddb8
2019/08/13 01:08:02.810| 45,9| cbdata.cc(426) cbdataInternalUnlock:
0x5534xa43f8b9324ddb8=0
2019/08/13 01:08:02.810| 45,9| cbdata.cc(449) cbdataInternalUnlock: Freeing
0x5534xa43f8b9324ddb8
2019/08/13 01:08:02.810| 93,3| ServiceRep.cc(534) noteAdaptationAnswer:
failed to fetch options [down,!opt]
2019/08/13 01:08:02.810| 93,8| ServiceRep.cc(448) changeOptions: changes
options from 0 to 0 [down,!opt]
2019/08/13 01:08:02.810| essential ICAP service is down after an options
fetch failure: icap://domainnameofvirusscanner:1344/SYMCScanReq-AV
[down,!opt]
----------

HTTP/1.1 500 Internal Server Error
Server: squid/3.5.20
Mime-Version: 1.0
Date: Tue, 13 Aug 2019 01:08:02 GMT
Content-Type: text/html;charset=utf-8
Content-Length: 3271
X-Squid-Error: ERR_ICAP_FAILURE 0
Vary: Accept-Language
Content-Language: en
X-Cache: MISS from 5e1c4b7853860819
X-Cache-Lookup: NONE from 5e1c4b7854860819:8443
Via: 1.1 5ec4b7886089 (squid/3.5.20)
Connection: keep-alive

----------
2019/08/13 01:08:02.810| 93,5| Xaction.cc(92) disableRepeats:
Adaptation::Icap::ModXact still cannot be repeated because ICAP service is
unusable [G/R job8]
2019/08/13 01:08:02.810| 93,3| ../../../src/base/AsyncJobCalls.h(177) dial:
Adaptation::Icap::ModXact::noteServiceReady threw exception: ICAP service is
unusable


----------



--
Sent from: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html