Re: [squid-users] squidaio_queue_request: WARNING - Queue congestion

On Tue, 16 Feb 2010 16:24:22 -0800, Tory M Blue <tmblue_at_gmail.com> wrote:
>>> 2010/02/16 14:18:15| squidaio_queue_request: WARNING - Queue
congestion
>>> 2010/02/16 14:18:26| squidaio_queue_request: WARNING - Queue
congestion
>>>
>>> What can I look for, if I don't believe it's IO wait or load (the box
>>> is sleeping), what else can it be. I thought creating a new build with
>>> 24 threads would help but it has not (I can rebuild with 10 threads vs
>>> the default 18 (is that right?) I guess.
>>
>> Each of the warnings doubles the previous queue size, so
>>
>>
>> I think its time we took this to the next level of debug.
>> Please run a startup with the option -X and lets see what squid is
really
>> trying to do there.
>>
>> Amos
>
>
> Okay not seeing anything exciting here. Nothing new with -X and/or
> with both -X and -d
>
> 2010/02/16 16:17:51| squidaio_queue_request: WARNING - Queue congestion
> 2010/02/16 16:17:59| squidaio_queue_request: WARNING - Queue congestion
>
> No additional information was provided other than what appears to be
> something odd between my config and what squid is loading into it's
> config.
>
> for example;
> conf file :maximum_object_size 1024 KB
> What it says it's parsing: 2010/02/16 16:12:07| parse_line:
> maximum_object_size 4096 KB
>
> conf file: cache_mem 100 MB
> What it says it's parsing: 2010/02/16 16:12:07| parse_line: cache_mem 8
MB
>
> This may not be the answer, but it's odd for sure (
>
> Nothing more on the queue congestion, no idea why this is happening.

To stdout/stderr or cache.log? I think if thats to stdout/stderr might be
the defaults loading.
There should be two in that case. The later one correct.

Though it may be worth double checking for other locations of squid.conf.

Amos
Received on Wed Feb 17 2010 - 00:45:15 MST