Re: [squid-users] squid continued even though it couldn't log?

On 25.01.2012 01:19, E.S. Rosenberg wrote:
> Hi all,
> I'm a bit puzzled by some logs at the moment:
>
> Last night we had a situation that caused one of our proxies to fill
> up it's logging disk, squid went down (as expected), but in syslog it
> looks like the squid parent is stil going and trying to create new
> children to handle requests:
> Jan 24 05:13:30 proxy (squid): logfileWrite:
> /var/log/squid3/access.log: (28) No space left on device
> Jan 24 05:13:31 proxy squid[26964]: Squid Parent: child process 1962
> exited with status 1
> Jan 24 05:13:34 proxy squid[26964]: Squid Parent: child process 2016
> started
>
> I always thought that squid goes down completely when it can't log
> but
> this seems to suggest otherwise....
>
> System:
> Ubuntu 11.04 server x86-64 on vmware
> squid 3.1.11
>
> The problem itself is solved I am just curious about it going down or
> not....
>
> Thanks,
> Eli

I'm suspecting the parent sees no problem, but the child does.
ie, the parent can open the file, but does not need to write, the child
dying on write errors. You could end up with spawning one squid worker,
service one request, dies logging it. rinse, repeat...

Amos
Received on Tue Jan 24 2012 - 23:02:00 MST