Re: [squid-users] xcalloc Fatal (squid 3.1.9)

Hi Amos,

I read the Bugzilla thread and found the patch may not work for 3.0
since 3.1 has changed its implementaion using reader callback. (Also
mentioned by Alex.)

Any advice how to apply the patch to 3.0?

In 3.0 it does reading(true) before makeSpaceAvailable(); If I do
"maybeMakeSpaceAvailable()" after reading(true), I may be trouble if
"maybeMakeSpaceAvailable()" fails.

Do you think if I do reading(false) following maybeMakeSpaceAvailble()
failure may be good enough?

Thanks in advance.

Edward

2011/3/9 V�ctor Jos� Hern�ndez G�mez <vjhergom_at_cic.upo.es>:
>
>>> I have found a message such as:
>>>
>>> FATAL: xcalloc: Unable to allocate 1 blocks of 536870912 bytes!
>>> Looks like a strange big block.
>>>
>>> My squid versi�n is 3.1.9. Any suggestion?
>>
>> Probably bug http://bugs.squid-cache.org/show_bug.cgi?id=3113
>>
>> Please try an upgrade to 3.1.11 to resolve that and a few other smaller
>> leaks.
>
> thank you, Amos, I have already upgraded squid to 3.1.11.
>
> In 3.1.9 we also got messages warning in that way :
> squidaio_queue_request: WARNING - Queue congestion (they were no very
> frequent)
>
> So I raised aufs_threads from 100 to 192 in compilation time. With very few
> activity I have received again the same warning. �Any idea or
> recommendation? �May be 192 threads is a very high value?
>
> Regards,
> --
> V�ctor
>
>
Received on Thu Mar 10 2011 - 18:03:47 MST