On 2/1/21 8:56 AM, Andrea Venturoli wrote:
It could be a network problem.
However, I think that's unlikely (also given the host is monitored and I
don't see alerts or other signs of such troubles).
While I cannot exclude that completely, I think I should first
investigate in other directions.
On 1/31/21 1:11 AM, Amos Jeffries wrote:
As I said, they live on the same host, so it can't be a network problem.
FYI, that conclusion does not follow. Even on the same host there is a
full TCP/IP networking stack between Squid and ICAP server doing things
to the packets. All localhost remo
On 31/01/21 6:08 am, Andrea Venturoli wrote:
On 1/29/21 8:38 PM, Alex Rousskov wrote:
Packet captures can tell you whether other Squid-ICAP server connections
were active at the time, whether from-Squid SYN packets were able to
reach the ICAP server, etc.
In other words, basic network trouble
On 1/29/21 8:38 PM, Alex Rousskov wrote:
IIRC, you did not disclose timeout suspicions before. This explanation
is news to me, and it eliminates several suspects.
Sorry, I didn't say much in fact.
I gave for granted that it was C-ICAP who stopped answering; I didn't
suspect a Squid bug and ha
On 1/29/21 11:55 AM, Andrea Venturoli wrote:
> I see Squid connections to C-ICAP starting to time out:
> when the number of errors reach 10, Squid marks squidclamav service as
> "suspended".
> No big surprise.
IIRC, you did not disclose timeout suspicions before. This explanation
is news to me,
On 1/27/21 6:11 PM, Alex Rousskov wrote:
Enable ICAP debugging and study cache.log for relevant messages,
especially just before the "suspending ICAP service" message shown above.
debug_options ALL,1 93,7
Thanks a lot.
As expected, I see Squid connections to C-ICAP starting to time out:
On 1/27/21 11:01 AM, Andrea Venturoli wrote:
>> 2021/01/04 14:24:24 kid1| suspending ICAP service for too many failures
>> 2021/01/04 14:24:24 kid1| essential ICAP service is suspended:
>> icap://127.0.0.1:1344/squidclamav [down,susp,fail11]
> This happens usually once a day, always at the same t
Hello.
On a box I manage, Squids occasionally stops for a few minutes, blaming
a communication error with C-ICAP (running SquidClamAV).
In cache.log I see:
2021/01/04 14:24:24 kid1| suspending ICAP service for too many failures
2021/01/04 14:24:24 kid1| essential ICAP service is suspended:
i
