2018/08/04 04:42:59 kid1| FATAL: Dying from an exception handling
failure; exception: check failed: false
exception location: mem/PageStack.cc(106) push
Then it tries to run again and again every kid but they always die:
2018/08/04 04:43:05 kid1| FATAL: kid1 registration timed out
2018/08/0
On 05/08/18 14:41, Heiler Bemerguy wrote:
> 2018/08/04 04:42:59 kid1| FATAL: Dying from an exception handling
> failure; exception: check failed: false
> exception location: mem/PageStack.cc(106) push
>
What are your cache_mem and cache_dir settings?
And what *-bit type (eg 16, 32, 64, 128)
Em 05/08/2018 05:47, Amos Jeffries escreveu:
On 05/08/18 14:41, Heiler Bemerguy wrote:
2018/08/04 04:42:59 kid1| FATAL: Dying from an exception handling
failure; exception: check failed: false
exception location: mem/PageStack.cc(106) push
What are your cache_mem and cache_dir settings?
On 07/08/18 03:32, Heiler Bemerguy wrote:
> Em 05/08/2018 05:47, Amos Jeffries escreveu:
>> On 05/08/18 14:41, Heiler Bemerguy wrote:
>>> 2018/08/04 04:42:59 kid1| FATAL: Dying from an exception handling
>>> failure; exception: check failed: false
>>> exception location: mem/PageStack.cc(106)
Em 06/08/2018 13:39, Amos Jeffries escreveu:
workers 5
cache_mem 5500 MB
cache_dir rock /cache2 13 min-size=1 max-size=196608
cache_dir rock /cache3 13 min-size=196609 max-size=624288
cache_dir rock /cache4 13 min-size=624289 max-swap-rate=500
swap-timeout=500
And what *-bit type
Em 06/08/2018 13:39, Amos Jeffries escreveu:
workers 5
cache_mem 5500 MB
cache_dir rock /cache2 13 min-size=1 max-size=196608
cache_dir rock /cache3 13 min-size=196609 max-size=624288
cache_dir rock /cache4 13 min-size=624289 max-swap-rate=500
swap-timeout=500
And what *-bit type
On 07/08/18 04:53, Heiler Bemerguy wrote:
> Em 06/08/2018 13:39, Amos Jeffries escreveu:
>>
>>> workers 5
>>> cache_mem 5500 MB
>>> cache_dir rock /cache2 13 min-size=1 max-size=196608
>>> cache_dir rock /cache3 13 min-size=196609 max-size=624288
>>> cache_dir rock /cache4 13 min-size=6
On 08/07/2018 08:01 AM, Amos Jeffries wrote:
> On 07/08/18 04:53, Heiler Bemerguy wrote:
>> Em 06/08/2018 13:39, Amos Jeffries escreveu:
cache_mem 5500 MB
cache_dir rock /cache2 13 min-size=1 max-size=196608
cache_dir rock /cache3 13 min-size=196609 max-size=624288
cache
On 08/08/18 04:30, Alex Rousskov wrote:
> On 08/07/2018 08:01 AM, Amos Jeffries wrote:
>> On 07/08/18 04:53, Heiler Bemerguy wrote:
>>> Em 06/08/2018 13:39, Amos Jeffries escreveu:
> cache_mem 5500 MB
> cache_dir rock /cache2 13 min-size=1 max-size=196608
> cache_dir rock /cache3 13
Em 07/08/2018 11:01, Amos Jeffries escreveu:
On 07/08/18 04:53, Heiler Bemerguy wrote:
Em 06/08/2018 13:39, Amos Jeffries escreveu:
workers 5
cache_mem 5500 MB
cache_dir rock /cache2 13 min-size=1 max-size=196608
cache_dir rock /cache3 13 min-size=196609 max-size=624288
cache_dir rock /
On 08/07/2018 11:04 AM, Amos Jeffries wrote:
> Do you have any idea then why the cunt of used slots should be over
> 2^32?
I suspect this is a Squid bug. We have seen the same symptoms while
working on not-directly-related bug 4823. I do not know whether OP
suffers from the same underlying proble
Em 07/08/2018 14:55, Alex Rousskov escreveu:
On 08/07/2018 11:04 AM, Amos Jeffries wrote:
Do you have any idea then why the cunt of used slots should be over
2^32?
I suspect this is a Squid bug. We have seen the same symptoms while
working on no
12 matches
Mail list logo
