Re: Trouble of Squid2.1PATCH2

Check your quota for cache_effective_user and file permission first.
Check the free space at the partition where cache_dir and cache logs exist.

M.

Shigeru Matsumoto:
>
> Dear Squid-Users,
>
> Today and the day before yesterday our Squid2.1PATCH2 broke down.
> I restarted the process but it didn't work, and then I rebooted the
> machine. However, it didn't recover, either.
>
> Error messages of cache.log is as follows:
> 1999/05/21 11:26:35| diskHandleWrite: FD 14: disk write error: (28) No
> space left on device
> FATAL: Write failure -- check your disk space and cache.log
> Squid Cache (Version 2.1.PATCH2): Terminated abnormally.
>
> And Error messages of squid.out is:
> FATAL: Write failure -- check your disk space and cache.log
> FATAL: Write failure -- check your disk space and cache.log
>
> There are enough spaces on the disk, though.
>
> Platform is Solaris2.6, and the machine is Ultra2.
>
> And this trouble happed when the traffic is very high. These days our
> Squid2.1PATCH2
> handle 690,000/day. Allocation mamory is 192 for the Squid and I set 2
> cache disks for
> juxtaposition as follows.
>
> cache_dir /export/home/squid/squid_cache 7000 16 256
> cache_dir /var/home/squid/squid_cache 1000 16 256
>
> Does anybody know the cause of the trouble?
>
> Best,
> Shiggy
> ------------------------------------------------------------------
> Shigeru Matsumoto << E-Mail: matumoto@ssd.sony.co.jp >>
> Sony Systems Design Co.Ltd.
> ------------------------------------------------------------------
>

-- 
           Maciej Kozinski         http://www.uck.uni.torun.pl/~maciek/ 
	   Remember: Un*x _IS_ user friendly... It's just selective about
		     who it's friends are.