Re: TCP_SWAPFAIL_MISS and asyncufs/2.3

Check your cache.log for frequent restarts. Squid seems to dislike being
started twice, or killed and restarted in unfriendly ways - if it's
crashing and restarting, it may be corrupting it's index, which would lead
to that problem. For it to occur for that timeframe, I'd guess it might be
happening semi-regularly.

KevinL

>>> "Franklin R. Jones" wrote
> On Wed, Apr 12, 2000 at 11:50:06PM +0200, Henrik Nordstrom wrote:
> > Franklin R. Jones wrote:
> >
> > > (~3 months ago?) then upgraded to 2.3 about 2+ weeks ago. response
> > > through this cache dropped dramaticly, noticed that almost all
> > > accesses were either swapfail_miss or tcp_miss.
> >
> > How is your Squid built? Is you using async-io or anything similar?
>
> no, fairly default ./configure --prefix=/usr/local/squid
>
> used gcc2.8.1 under Solaris 2.7 Generic 106541-08 to build.
>
> cache disk is currently a single 18Gb fast wide scsi
>
> #
> # cache_dir directive
> #
>
> cache_dir ufs /usr/local/squid/cache 15000 64 256
>
>
> fj..
> --
> "The days are just packed!" Calvin & Hobbs
>
>

--------------- qnevhf@obsu.arg.nh ---------------
Kevin Littlejohn,
Technical Architect, Connect.com.au
Don't let the Govt censor our access to the 'net -
http://www.efa.org.au/Campaigns/stop.html
Received on Wed Apr 12 2000 - 18:48:38 MDT