Re: [squid-users] Squid freeze each hour.

2016-12-20 Thread David Touzeau
Thanks, 

I'm test it now

-Message d'origine-
De : squid-users [mailto:squid-users-boun...@lists.squid-cache.org] De la part 
de Garri Djavadyan
Envoyé : mardi 20 décembre 2016 18:58
À : squid-users@lists.squid-cache.org
Objet : Re: [squid-users] Squid freeze each hour.

On 2016-12-20 21:42, David Touzeau wrote:
> Is there any way to disabling Cache digest without need to recompile 
> squid ?

Hi,

Use "digest_generation off".

http://www.squid-cache.org/Doc/config/digest_generation/


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

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


Re: [squid-users] Squid freeze each hour.

2016-12-20 Thread Garri Djavadyan

On 2016-12-20 21:42, David Touzeau wrote:
Is there any way to disabling Cache digest without need to recompile 
squid ?


Hi,

Use "digest_generation off".

http://www.squid-cache.org/Doc/config/digest_generation/


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


Re: [squid-users] Squid freeze each hour.

2016-12-20 Thread David Touzeau
Hi Alex,

Is there any way to disabling Cache digest without need to recompile squid ?

-Message d'origine-
De : Alex Rousskov [mailto:rouss...@measurement-factory.com] 
Envoyé : mardi 20 décembre 2016 17:21
À : squid-users@lists.squid-cache.org
Cc : David Touzeau <da...@articatech.com>
Objet : Re: [squid-users] Squid freeze each hour.

On 12/20/2016 04:53 AM, David Touzeau wrote:

> I'm using the 3.5.23, each hour, the proxy port did not respond for 3 
> to 10 minutes.

Do you have Cache Digests enabled (either implicitly or explicitly)? If yes, 
try disabling them. Others on the list can help you with that if you cannot 
figure it out.

If disabling Cache Digests solves the problem, keep them disabled unless your 
Squids actually need/use them.


HTH,

Alex.


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


Re: [squid-users] Squid freeze each hour.

2016-12-20 Thread Alex Rousskov
On 12/20/2016 04:53 AM, David Touzeau wrote:

> I'm using the 3.5.23, each hour, the proxy port did not respond for 3 to 10
> minutes.

Do you have Cache Digests enabled (either implicitly or explicitly)? If
yes, try disabling them. Others on the list can help you with that if
you cannot figure it out.

If disabling Cache Digests solves the problem, keep them disabled unless
your Squids actually need/use them.


HTH,

Alex.

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


Re: [squid-users] Squid freeze each hour.

2016-12-20 Thread David Touzeau
le: checking entry, key: A1F5E4243AA2BD14C147D180CBD5022F
2016/12/20 15:27:41.532 kid1| 22,3| refresh.cc(291) refreshCheck: checking 
freshness of 'http://cdn.embedly.com/js/all.c353026a.js'
2016/12/20 15:27:41.533 kid1| 22,3| refresh.cc(312) refreshCheck: Matched 
'\.js$ 84000 80%% 604800'
2016/12/20 15:27:41.533 kid1| 22,3| refresh.cc(314) refreshCheck:   age:
11727
2016/12/20 15:27:41.533 kid1| 22,3| refresh.cc(316) refreshCheck:   
check_time: Tue, 20 Dec 2016 15:27:41 GMT
2016/12/20 15:27:41.533 kid1| 22,3| refresh.cc(318) refreshCheck:   
entry->timestamp:   Tue, 20 Dec 2016 12:12:14 GMT
2016/12/20 15:27:41.533 kid1| 22,3| refresh.cc(168) refreshStaleness: FRESH: 
expires 1545307934 >= check_time 1482247661 
2016/12/20 15:27:41.533 kid1| 22,3| refresh.cc(338) refreshCheck: Staleness = -1
2016/12/20 15:27:41.533 kid1| 22,3| refresh.cc(461) refreshCheck: Object isn't 
stale..
2016/12/20 15:27:41.533 kid1| 22,3| refresh.cc(463) refreshCheck: returning 
FRESH_EXPIRES
2016/12/20 15:27:41.533 kid1| 71,6| store_digest.cc(288) storeDigestAdd: 
storeDigestAdd: added entry, key: A1F5E4243AA2BD14C147D180CBD5022F


-Message d'origine-
De : Eliezer Croitoru [mailto:elie...@ngtech.co.il] 
Envoyé : mardi 20 décembre 2016 14:30
À : 'David Touzeau' <da...@articatech.com>; squid-users@lists.squid-cache.org
Objet : RE: [squid-users] Squid freeze each hour.

Hey David,

Some things are missing and we need you to fill the picture for us.
What OS are you running squid ontop?
Are you running it in intercept or tproxy mode?
Are you using ssl-bump?
Are you using it with multiple cores?
Can you attach the squid.conf( removing the confidential details) to this email?

Thanks,
Eliezer


Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il


-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf 
Of David Touzeau
Sent: Tuesday, December 20, 2016 1:53 PM
To: squid-users@lists.squid-cache.org
Subject: [squid-users] Squid freeze each hour.

Hi

I'm using the 3.5.23, each hour, the proxy port did not respond for 3 to 10 
minutes.
During the freeze have made a -k debug to see whats happening.
Here a piece of log of the log during the freeze:

Is there something relevant ?:

2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(226) storeDigestAddable:
storeDigestAddable: checking entry, key: 877FE61D1641BCA926338890AF1478D2
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(291) refreshCheck: checking 
freshness of ''
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(312) refreshCheck: Matched '.
0 75%% 2592000'
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(314) refreshCheck:   age:
1024129
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(316) refreshCheck:
check_time: Tue, 20 Dec 2016 12:09:09 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(318) refreshCheck:
entry->timestamp:   Thu, 08 Dec 2016 15:40:20 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(168) refreshStaleness: FRESH:
expires 1486393228 >= check_time 1482235749
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(338) refreshCheck: Staleness = -1
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(461) refreshCheck: Object isn't 
stale..
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(463) refreshCheck: returning 
FRESH_EXPIRES
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(288) storeDigestAdd:
storeDigestAdd: added entry, key: 877FE61D1641BCA926338890AF1478D2
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(226) storeDigestAddable:
storeDigestAddable: checking entry, key: 87BF2568F0A7D71F1E567579CCC216F7
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(291) refreshCheck: checking 
freshness of ''
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(312) refreshCheck: Matched '.
0 75%% 2592000'
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(314) refreshCheck:   age:
1019863
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(316) refreshCheck:
check_time: Tue, 20 Dec 2016 12:09:09 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(318) refreshCheck:
entry->timestamp:   Thu, 08 Dec 2016 16:51:26 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(173) refreshStaleness: STALE:
expires 1481215886 < check_time 1482235749
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(338) refreshCheck: Staleness = 
1019863
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(362) refreshCheck: YES: Must 
revalidate stale object (origin set no-cache or private)
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(259) storeDigestAddable:
storeDigestAdd: entry expires within 3600 secs, ignoring
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(226) storeDigestAddable:
storeDigestAddable: checking entry, key: 873F5089579B6B7E351555B77F98259A
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(291) refreshCheck: checking 
freshness of ''
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(312) refreshCheck: Matched '.
0 75%% 2592000'
2016/12/20 12:09:09.07

Re: [squid-users] Squid freeze each hour.

2016-12-20 Thread David Touzeau

Thanks Elizer, i will send you squid configuration and cache.log in a separate 
message

Some things are missing and we need you to fill the picture for us.

What OS are you running squid ontop? --> Debian 7 64 bits
Are you running it in intercept or tproxy mode? --> connected mode.
Are you using ssl-bump? --> No
Are you using it with multiple cores? --> Only one core
Can you attach the squid.conf( removing the confidential details) to this
email?

-Message d'origine-
De : Eliezer Croitoru [mailto:elie...@ngtech.co.il]
Envoyé : mardi 20 décembre 2016 14:30
À : 'David Touzeau' <da...@articatech.com>;
squid-users@lists.squid-cache.org
Objet : RE: [squid-users] Squid freeze each hour.

Hey David,

Some things are missing and we need you to fill the picture for us.
What OS are you running squid ontop?
Are you running it in intercept or tproxy mode?
Are you using ssl-bump?
Are you using it with multiple cores?
Can you attach the squid.conf( removing the confidential details) to this
email?

Thanks,
Eliezer


Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il


-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On
Behalf Of David Touzeau
Sent: Tuesday, December 20, 2016 1:53 PM
To: squid-users@lists.squid-cache.org
Subject: [squid-users] Squid freeze each hour.

Hi

I'm using the 3.5.23, each hour, the proxy port did not respond for 3 to 10
minutes.
During the freeze have made a -k debug to see whats happening.
Here a piece of log of the log during the freeze:

Is there something relevant ?:

2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(226) storeDigestAddable:
storeDigestAddable: checking entry, key: 877FE61D1641BCA926338890AF1478D2
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(291) refreshCheck: checking
freshness of ''
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(312) refreshCheck: Matched '.
0 75%% 2592000'
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(314) refreshCheck:   age:
1024129
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(316) refreshCheck:
check_time: Tue, 20 Dec 2016 12:09:09 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(318) refreshCheck:
entry->timestamp:   Thu, 08 Dec 2016 15:40:20 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(168) refreshStaleness: FRESH:
expires 1486393228 >= check_time 1482235749
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(338) refreshCheck: Staleness
= -1
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(461) refreshCheck: Object
isn't stale..
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(463) refreshCheck: returning
FRESH_EXPIRES
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(288) storeDigestAdd:
storeDigestAdd: added entry, key: 877FE61D1641BCA926338890AF1478D2
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(226) storeDigestAddable:
storeDigestAddable: checking entry, key: 87BF2568F0A7D71F1E567579CCC216F7
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(291) refreshCheck: checking
freshness of ''
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(312) refreshCheck: Matched '.
0 75%% 2592000'
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(314) refreshCheck:   age:
1019863
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(316) refreshCheck:
check_time: Tue, 20 Dec 2016 12:09:09 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(318) refreshCheck:
entry->timestamp:   Thu, 08 Dec 2016 16:51:26 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(173) refreshStaleness: STALE:
expires 1481215886 < check_time 1482235749
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(338) refreshCheck: Staleness
= 1019863
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(362) refreshCheck: YES: Must
revalidate stale object (origin set no-cache or private)
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(259) storeDigestAddable:
storeDigestAdd: entry expires within 3600 secs, ignoring
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(226) storeDigestAddable:
storeDigestAddable: checking entry, key: 873F5089579B6B7E351555B77F98259A
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(291) refreshCheck: checking
freshness of ''
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(312) refreshCheck: Matched '.
0 75%% 2592000'
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(314) refreshCheck:   age:
956460
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(316) refreshCheck:
check_time: Tue, 20 Dec 2016 12:09:09 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(318) refreshCheck:
entry->timestamp:   Fri, 09 Dec 2016 10:28:09 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(173) refreshStaleness: STALE:
expires 1481279289 < check_time 1482235749
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(338) refreshCheck: Staleness
= 956460
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(362) refreshCheck: YES: Must
revalidate stale object (origin set no-cache or private)
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(259) store

Re: [squid-users] Squid freeze each hour.

2016-12-20 Thread FredB
I do not see this, do you have something particular ? SSLBump maybe ? SMP ?
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users


Re: [squid-users] Squid freeze each hour.

2016-12-20 Thread Eliezer Croitoru
Hey David,

Some things are missing and we need you to fill the picture for us.
What OS are you running squid ontop?
Are you running it in intercept or tproxy mode?
Are you using ssl-bump?
Are you using it with multiple cores?
Can you attach the squid.conf( removing the confidential details) to this email?

Thanks,
Eliezer


Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il


-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf 
Of David Touzeau
Sent: Tuesday, December 20, 2016 1:53 PM
To: squid-users@lists.squid-cache.org
Subject: [squid-users] Squid freeze each hour.

Hi

I'm using the 3.5.23, each hour, the proxy port did not respond for 3 to 10 
minutes.
During the freeze have made a -k debug to see whats happening.
Here a piece of log of the log during the freeze:

Is there something relevant ?:

2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(226) storeDigestAddable:
storeDigestAddable: checking entry, key: 877FE61D1641BCA926338890AF1478D2
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(291) refreshCheck: checking 
freshness of ''
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(312) refreshCheck: Matched '.
0 75%% 2592000'
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(314) refreshCheck:   age:
1024129
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(316) refreshCheck:
check_time: Tue, 20 Dec 2016 12:09:09 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(318) refreshCheck:
entry->timestamp:   Thu, 08 Dec 2016 15:40:20 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(168) refreshStaleness: FRESH:
expires 1486393228 >= check_time 1482235749
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(338) refreshCheck: Staleness = -1
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(461) refreshCheck: Object isn't 
stale..
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(463) refreshCheck: returning 
FRESH_EXPIRES
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(288) storeDigestAdd:
storeDigestAdd: added entry, key: 877FE61D1641BCA926338890AF1478D2
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(226) storeDigestAddable:
storeDigestAddable: checking entry, key: 87BF2568F0A7D71F1E567579CCC216F7
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(291) refreshCheck: checking 
freshness of ''
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(312) refreshCheck: Matched '.
0 75%% 2592000'
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(314) refreshCheck:   age:
1019863
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(316) refreshCheck:
check_time: Tue, 20 Dec 2016 12:09:09 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(318) refreshCheck:
entry->timestamp:   Thu, 08 Dec 2016 16:51:26 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(173) refreshStaleness: STALE:
expires 1481215886 < check_time 1482235749
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(338) refreshCheck: Staleness = 
1019863
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(362) refreshCheck: YES: Must 
revalidate stale object (origin set no-cache or private)
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(259) storeDigestAddable:
storeDigestAdd: entry expires within 3600 secs, ignoring
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(226) storeDigestAddable:
storeDigestAddable: checking entry, key: 873F5089579B6B7E351555B77F98259A
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(291) refreshCheck: checking 
freshness of ''
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(312) refreshCheck: Matched '.
0 75%% 2592000'
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(314) refreshCheck:   age:
956460
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(316) refreshCheck:
check_time: Tue, 20 Dec 2016 12:09:09 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(318) refreshCheck:
entry->timestamp:   Fri, 09 Dec 2016 10:28:09 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(173) refreshStaleness: STALE:
expires 1481279289 < check_time 1482235749
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(338) refreshCheck: Staleness = 
956460
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(362) refreshCheck: YES: Must 
revalidate stale object (origin set no-cache or private)
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(259) storeDigestAddable:
storeDigestAdd: entry expires within 3600 secs, ignoring
2016/12/20 12:09:09.072 kid1| 71,6| store_digest.cc(226) storeDigestAddable:
storeDigestAddable: checking entry, key: 87FFFEA8EBEFAE0DBC21EBC97D405839
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(291) refreshCheck: checking 
freshness of ''
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(312) refreshCheck: Matched '.
0 75%% 2592000'
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(314) refreshCheck:   age:
948473
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(316) refreshCheck:
check_time: Tue, 20 Dec 2016 12:09:09 GMT
2016/12/20 12:09:09.072 kid1| 22,3| refresh.cc(318) refreshCheck:
entry->timestamp:   Fri, 09 Dec 2016 12:41:16 GMT