cache_swap_low 95
cache_swap_high 98
I've sent the entries of my cache.log and access.log to the list (please
check the thread).
>>>>>>>>>>>>>>
Enable cache_store_log TAG and get some log informations.
Becuase we can check the swapin,swapout informations on that log.
> 2004/03/11 13:10:48| WARNING: newer swaplog entry for dirno 0, fileno
> 00025F38
This is the information related to the Warning.
/* swapfile in use, not by this URL, log entry is newer */
/* This is sorta bad: the log entry should NOT be newer at this
* point. If the log is dirty, the filesize check should have
* caught this. If the log is clean, there should never be a
* newer entry. */
> 2004/03/11 13:11:40| WARNING: 10 swapin MD5 mismatches
Meta Data check is getting failed over here.
Regards,
Muthukumar
=====================================================================
As for the store.log, I've disabled logging to store.log
cache_store_log none
Regards,
-------------------
Sent using Office 2003, Exchange Server 2000 and Windows XP
Professional
-------------------
-----Original Message-----
From: Muthukumar [mailto:[EMAIL PROTECTED]
Sent: Friday, March 12, 2004 3:28 PM
To: Michael Vincent Pozon; Henrik Nordstrom
Cc: [EMAIL PROTECTED]
Subject: Re: [squid-users] Incomplete error pages
cache_mem 2000 MB
maximum_object_size 1024000 KB
maximum_object_size_in_memory 128 KB
ipcache_size 16384
fqdncache_size 16384
cache_replacement_policy heap LFUDA
memory_replacement_policy heap GDSF
cache_dir diskd /cache 80000 32 256
ftp_list_width 64
>>>>>>>>>>
What is your cache_swap_low ,cache_swap_high settings.
What is your store.log and cache.log entries.
Regards,
Muthukumar.
-----Original Message-----
From: Henrik Nordstrom [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 11, 2004 11:09 PM
To: Michael Vincent Pozon
Cc: [EMAIL PROTECTED]
Subject: RE: [squid-users] Incomplete error pages
On Thu, 11 Mar 2004, Michael Vincent Pozon wrote:
> I think it has something to do with the entry in my cache.log:
>
> assertion failed: errorpage.c:292: "mem->inmem_hi == 0"
>
> then Squid dies but restarts itself with DIRTY storage upon
rebuilding.
This is a bug. Any traffic that was ongoing when this happened was
terminated immediately as Squid restarted.
> then these:
>
> 2004/03/11 13:10:48| WARNING: newer swaplog entry for dirno 0, fileno
> 00025F38
These are expected on dirty rebuilds.
> 2004/03/11 13:11:40| WARNING: 10 swapin MD5 mismatches
These as well, until the rebuild has finished.
Once the cache has been rebuild only very few of these are expected.
Regards
Henrik
