Re: [squid-users] After upgrade from squid6.6 to 6.8 we have a lot of ICAP_ERR_OTHER and ICAP_ERR_GONE messages in icap logfiles

2024-03-14 Thread Dieter Bloms 
Hello Amos,

thank you for your answer!
I opened a bugreport https://bugs.squid-cache.org/show_bug.cgi?id=5353
with some debug infos attached.

On Thu, Mar 14, Amos Jeffries wrote:

> 
> On 12/03/24 04:31, Dieter Bloms wrote:
> > Hello,
> > 
> > after an upgrade from squid6.6 to squid6.8 on a debian bookworm we have a 
> > lot
> > of messages from type:
> > 
> > ICAP_ERR_GONE/000
> > ICAP_ERR_OTHER/200
> > ICAP_ERR_OTHER/408
> > ICAP_ERR_OTHER/204
> > 
> > and some of our users claim about bad performance and some get "empty
> > pages".
> > Unfortunately it is not deterministic, the page will appear the next
> > time it is called up. I can't see anything conspicuous in the cache.log.
> > 
> 
> Hmm, there was 
> 
> changing message I/O in particular. The behavioural changes from that might
> have impacted ICAP in some unexpected way.
> 
> Also, if you are using SSL-Bump to enable virus scanning then 
> 
> might also be having effects.
> 
> HTH
> Amos
> ___
> squid-users mailing list
> squid-users@lists.squid-cache.org
> https://lists.squid-cache.org/listinfo/squid-users

-- 
Gruß

  Dieter

--
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
>From field.
___
squid-users mailing list
squid-users@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] After upgrade from squid6.6 to 6.8 we have a lot of ICAP_ERR_OTHER and ICAP_ERR_GONE messages in icap logfiles

2024-03-14 Thread Alex Rousskov 

On 2024-03-11 11:31, Dieter Bloms wrote:

Hello,

after an upgrade from squid6.6 to squid6.8 on a debian bookworm we have a lot
of messages from type:

ICAP_ERR_GONE/000
ICAP_ERR_OTHER/200
ICAP_ERR_OTHER/408
ICAP_ERR_OTHER/204

and some of our users claim about bad performance and some get "empty
pages".


Please see Squid Bug 5352 for a work-in-progress fix that needs testing:
https://bugs.squid-cache.org/show_bug.cgi?id=5352

Thank you,

Alex.



Unfortunately it is not deterministic, the page will appear the next
time it is called up. I can't see anything conspicuous in the cache.log.

There was no change to the virus scanner nor any change to the squid
config during the upgrade.

Here the icap spefific config lines from squid:

--snip--
acl CONNECT method CONNECT
acl withoutvirusscanner.dstnames dstdomain 
"/etc/squid/withoutvirusscanner.dstnames"
acl audio rep_mime_type ^audio/
acl audio rep_mime_type ^video/

icap_enable on
icap_preview_enable on
icap_preview_size 128
icap_persistent_connections on
icap_send_client_ip on
icap_send_client_username on
icap_service_failure_limit -1
icap_service_revival_delay 30
logformat icap_debug %ts.%03tu %6icap::tr %>a %icap::to/%03icap::Hs %icap::

___
squid-users mailing list
squid-users@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] After upgrade from squid6.6 to 6.8 we have a lot of ICAP_ERR_OTHER and ICAP_ERR_GONE messages in icap logfiles

2024-03-13 Thread Amos Jeffries 



On 12/03/24 04:31, Dieter Bloms wrote:

Hello,

after an upgrade from squid6.6 to squid6.8 on a debian bookworm we have a lot
of messages from type:

ICAP_ERR_GONE/000
ICAP_ERR_OTHER/200
ICAP_ERR_OTHER/408
ICAP_ERR_OTHER/204

and some of our users claim about bad performance and some get "empty
pages".
Unfortunately it is not deterministic, the page will appear the next
time it is called up. I can't see anything conspicuous in the cache.log.



Hmm, there was 
 
changing message I/O in particular. The behavioural changes from that 
might have impacted ICAP in some unexpected way.


Also, if you are using SSL-Bump to enable virus scanning then 
 
might also be having effects.


HTH
Amos
___
squid-users mailing list
squid-users@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-users

[squid-users] After upgrade from squid6.6 to 6.8 we have a lot of ICAP_ERR_OTHER and ICAP_ERR_GONE messages in icap logfiles

2024-03-11 Thread Dieter Bloms 
Hello,

after an upgrade from squid6.6 to squid6.8 on a debian bookworm we have a lot
of messages from type:

ICAP_ERR_GONE/000
ICAP_ERR_OTHER/200
ICAP_ERR_OTHER/408
ICAP_ERR_OTHER/204

and some of our users claim about bad performance and some get "empty
pages". 
Unfortunately it is not deterministic, the page will appear the next
time it is called up. I can't see anything conspicuous in the cache.log.

There was no change to the virus scanner nor any change to the squid
config during the upgrade.

Here the icap spefific config lines from squid:

--snip--
acl CONNECT method CONNECT
acl withoutvirusscanner.dstnames dstdomain 
"/etc/squid/withoutvirusscanner.dstnames"
acl audio rep_mime_type ^audio/
acl audio rep_mime_type ^video/

icap_enable on
icap_preview_enable on
icap_preview_size 128
icap_persistent_connections on
icap_send_client_ip on
icap_send_client_username on
icap_service_failure_limit -1
icap_service_revival_delay 30
logformat icap_debug %ts.%03tu %6icap::tr %>a %icap::to/%03icap::Hs %icap::From field.
___
squid-users mailing list
squid-users@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-users