[squid-users] Could not connect to ICAP server

From: Florian Effenberger <floeff@dont-contact.us>
Date: Wed, 22 Sep 2004 18:24:11 +0200

Hello there,

recently, I experience a lot of problems with the ICAP patch. From time
to time, clients receive the Squid error page telling that ICAP is
unavailable. The ICAP server is ISS Proventia Web Filter.

Here is what the log file says:

2004/09/22 07:35:11| Ready to serve requests.
2004/09/22 09:17:47| icapReqModBodyHandler: (104) Connection reset by peer
2004/09/22 09:17:47| icapLineLength: warning lineLen (8) > len (7)
2004/09/22 09:17:47| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/22 09:27:04| icapReqModBodyHandler: (104) Connection reset by peer
2004/09/22 09:53:38| urlParse: Illegal character in hostname
'www.motorrad-pĆ¼schel.de'
2004/09/22 10:51:15| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/22 10:51:16| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/22 11:17:12| icapReqModBodyHandler: (104) Connection reset by peer
2004/09/22 11:18:41| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/22 12:35:58| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/22 12:36:05| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/22 13:15:59| icapReadHeader: FD 12 recv EOF

2004/09/21 07:35:13| Ready to serve requests.
2004/09/21 09:36:55| icapReqModBodyHandler: (104) Connection reset by peer
2004/09/21 09:49:19| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 09:49:26| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 09:54:58| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 09:54:59| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 09:54:59| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 10:08:00| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 10:08:00| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 10:23:56| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 10:24:04| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 11:01:27| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 11:01:28| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 11:14:41| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 11:14:46| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 11:27:28| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 11:27:28| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 11:42:51| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 11:42:52| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 11:49:36| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 11:49:39| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 12:20:52| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 12:20:53| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 12:33:27| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 12:33:27| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 12:45:10| icapReadHeader: FD 12 recv EOF
2004/09/21 12:45:25| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 16:39:49| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/21 16:39:50| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/22 07:28:25| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/22 07:28:25| icapReadHeader: FD 14 recv EOF
2004/09/22 07:28:26| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/22 07:28:26| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/22 07:35:11| Reconfiguring Squid Cache (version 2.5.STABLE6)...
2004/09/22 07:35:11| FD 8 Closing HTTP connection

2004/09/20 07:35:13| Ready to serve requests.
2004/09/20 09:33:24| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/20 09:33:24| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/20 10:07:30| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/20 10:07:31| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/20 11:14:37| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/20 11:14:39| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/20 11:23:50| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/20 11:23:53| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/20 11:35:04| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/20 11:35:07| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/20 11:43:27| icapReadHeader: FD 14 recv EOF
2004/09/20 11:43:29| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/20 11:48:52| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/20 11:48:52| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/20 11:57:21| icapReqModBodyHandler: (104) Connection reset by peer
2004/09/20 11:58:10| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/20 12:00:33| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/20 12:07:45| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/20 12:07:45| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/20 12:31:29| icapParseChunkSize: WARNING in mid-line, ret 0
2004/09/20 12:31:29| Could not connect to ICAP server
192.168.10.254:1344: (111) Connection refused
2004/09/21 07:35:13| Reconfiguring Squid Cache (version 2.5.STABLE6)...
2004/09/21 07:35:13| FD 8 Closing HTTP connection

Any idea what could be wrong? The ICAP server is on the same machine as
Squid is, so network connectivity problems cannot be the cause.

Thanks
Florian
Received on Wed Sep 22 2004 - 10:24:24 MDT

This archive was generated by hypermail pre-2.1.9 : Fri Oct 01 2004 - 12:00:02 MDT