Re: TCP_SWAPFAIL_MISS

From: as web server manager <webadm@dont-contact.us>
Date: Mon, 8 Feb 1999 11:36:00 +0000 (GMT)

Back in December 1998 ...

Henrik Nordstrom wrote:
>
> Eric wrote:
>
> > I read the source code, I know what it means, but I don't really
> > know what actually triggers it. I am running 2.1 PATCH1
>
> Two possible causes:
> 1. Some problem with your harddrive or filesystem
> 2. Some unknown problem with Squid.
>
> If the error is caused by (1), then you probably have a message in your
> systems messages or syslog file, or on the console.
>
> If the error is caused by (2) then Squid needs to be debugged but I have
> not yet heard any other people reporting this with 2.1.PATCH1.

I've just started using Squid 2.1.PATCH2 and seem to get a number of
TCP_SWAPFAIL_MISS log entries just after Squid is started. My guess based on
the timing (with only a few tens of thousands of cache entries currently, so
startup is quite fast, no chance to confirm the exact timing) is that it may
also arise while the metadata is being loaded and Squid does not yet know
reliably what is available from the cache, and hence pretends swapping
failed to force a remote fetch.

Can anyone say whether that's the right explanation? If it's definitely not,
any ideas what might have caused it...? [No sign of hardware/filesystem
problems.]

                                John Line

-- 
University of Cambridge WWW manager account (usually John Line)
Send general WWW-related enquiries to webmaster@ucs.cam.ac.uk
Received on Mon Feb 08 1999 - 04:39:18 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:44:29 MST