Search squid archive

Re: Squid 5.2: assertion failed: Controller.cc:930: "!transients || e.hasTransients()"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/23/21 6:39 AM, David Touzeau wrote:

> cache dir rock : objects larger than 32,000 bytes cannot be cached

Modern rock versions do not have that limitation. Relying on wiki pages
for documentation carries elevated risks, especially when reading old
pages, but introduction of large object support was documented at
https://wiki.squid-cache.org/Features/LargeRockStore

A better starting point may be cache_dir documentation in your
squid.conf.documented generated for your Squid version.


HTH,

Alex.



> Le 23/11/2021 à 11:01, David Touzeau a écrit :
>> Ok thanks, we will investigate in this way
>>
>> Le 22/11/2021 à 19:33, Alex Rousskov a écrit :
>>> On 11/22/21 12:48 PM, David Touzeau wrote:
>>>> Here our SMP configuration:
>>>>
>>>> workers 2
>>>>
>>>> cache_dir rock /home/squid/cache/rock 0 min-size=0 max-size=131072 slot-size=32000
>>>>
>>>> if ${process_number} = 1
>>>> memory_cache_mode always
>>>> cpu_affinity_map process_numbers=${process_number} cores=1
>>>> cache_dir    aufs    /home/squid/Caches/disk    50024    16    256 min-size=131072 max-size=3221225472
>>>> endif
>>>>
>>>> if ${process_number} = 2
>>>> memory_cache_mode always
>>>> cpu_affinity_map process_numbers=${process_number} cores=2
>>>> endif
>>>>
>>>>
>>>> where is the false settings ?
>>> I am limiting my answer to the problems in this email thread scope: aufs
>>> cache_dirs are UFS-based cache_dirs. UFS-based cache_dirs are not
>>> SMP-aware and are not supported in SMP configurations. Your choices include:
>>>
>>> * drop SMP (i.e. remove "workers" and ARA)
>>> * drop aufs (i.e. remove "cache_dir aufs" and ARA)
>>>
>>> ... where ARA is "adjust the rest of the configuration accordingly".
>>>
>>>
>>> HTH,
>>>
>>> Alex.
>>>
>>>
>>>> Le 22/11/2021 à 18:18, Alex Rousskov a écrit :
>>>>> On 11/22/21 11:55 AM, David Touzeau wrote:
>>>>>
>>>>>> What does mean this error :
>>>>>>
>>>>>> 2021/11/21 17:23:06 kid1| assertion failed: Controller.cc:930:
>>>>>> "!transients || e.hasTransients()"
>>>>>> We are unable to start the service it always crashes.
>>>>>> How can we can fix it ( purge cache , reboot )... ?
>>>>> This is a Squid bug or misconfiguration. If you are using a UFS-based
>>>>> cache_dir with multiple workers, then it is a misconfiguration. If you
>>>>> want to use SMP disk caching, please use rock store instead.
>>>>>
>>>>> HTH,
>>>>>
>>>>> Alex.
>>>>> P.S. This assertion has been reported several times, including for Squid
>>>>> v4, but it was probably always due to a Squid misconfiguration. We need
>>>>> to find a good way to explicitly reject such configurations instead of
>>>>> asserting (while not rejecting similar unsupported configurations that
>>>>> still "work" from their admins point of view).
>>
>>
>> _______________________________________________
>> squid-users mailing list
>> squid-users@xxxxxxxxxxxxxxxxxxxxx
>> http://lists.squid-cache.org/listinfo/squid-users
> 

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




[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux