Hi.
On 18.04.2011 13:47, Amos Jeffries wrote:
> The behave identically in this regard. I suspect something is causing
> 3.1 to resume service much slower than 2.7 did. Which particular 3.1
> release is doing this?
That's a 3.1.12 right now.
>> Anyway, is there a way to do a 'soft reconfiguration' ? Without closing
>> HTTP/ICP/SNMP connections (or at least not breaking client
>
> Sadly not yet. We are working towards it for future releases.
Good news.
> If that is true, then I suspect you are using one of the early 3.1
> releases with broken LFS support. Or something is breaking/corrupting
> the swap.state journal during a reconfigure.
> Does your cache.log contain a warning about "version 1 LFS" detected
> or mention a DIRTY load during reconfigure? (may need ALL,1 debug level).
Actually it says this all the time:
Version 1 of swap file with LFS support detected...
# grep "Version 1 of swap file with LFS support detected" cache.log | wc -l
100
# stat swap.state
95 4012314 -rw-r----- 1 squid squid 16326000 10203960 "Apr 19 14:02:21
2011" "Apr 20 10:53:45 2011" "Apr 20 10:53:45 2011" "Apr 19 14:02:21
2011" 16384 19968 0 swap.state
cache_dir:
cache_dir ufs /usr/local/squid/cache 1100 16 256
And the solution is... ?
Thanks.
Eugene.
Received on Wed Apr 20 2011 - 05:09:37 MDT
This archive was generated by hypermail 2.2.0 : Wed Apr 20 2011 - 12:00:03 MDT