> On Mon Oct 23 11:39:52 UTC 2023 Ralf Hildebrandt wrote:
>
> > I upgraded from 6.3 to 6.4 today and it INSTANTLY began crashing
> > (frequently!)
> >
> > The Log messages in cache.log:
> > ...
> > 2023/10/23 09:57:21| Beginning Validation Procedure
> > 2023/10/23 09:57:21| Completed Validation Pr
> Hi,
>
> I have the similar problem on FreeBSD 10.1-STABLE #1 r275861 with
> squid-3.4.10. I also applied MEMPOOLS=1 when starting squid. I
> experience the process slowing down and unacceptable performance.
>
> Squid is configured to use kerberos and ntlm authentication and lap
> group authenti
> Nothing particularly stands out as leaking. Although the cache memory
> pages (mem_node) in-use size is suspiciously close to half what you
> say the OS is reporting.
>
> That makes me suspect that your OS is rounding up its allocations to
> 8KB of memory for each node. If that is the case the s
> On 26/11/2014 8:59 a.m., Doug Sampson wrote:
> >
> > Thanks, Amos, for your pointers.
> >
> > I've commented out all the fresh_patterns lines appearing above
> > the last two lines.
> >
> > I also have dropped diskd in favor of using aufs exclus
>Maybe your problem is related to sysctl mib tuning about
> swap/overcommit etc. I did not observed memory leak with squid 3.4.4,
> but FB 10 do swap frequently than old version.
Could you elaborate a bit more? That went over my head. What could I do in
terms of tuning the system?
~Doug
> On 25/11/2014 9:06 a.m., Doug Sampson wrote:
> > Recently due to squid 2.7 being EOL'ed, we migrated our squid
> > server to version 3.4.9 on a FreeBSD 10.0-RELEASE running on 64-bit
> > hardware. We started seeing paging file being swapped out
> > eventually
Recently due to squid 2.7 being EOL'ed, we migrated our squid server to version
3.4.9 on a FreeBSD 10.0-RELEASE running on 64-bit hardware. We started seeing
paging file being swapped out eventually running out of available memory. From
the time squid gets started it usually takes about two days
