[squid-users] Crash: every 1-2 hour: kernel: Out of memory: Kill process (squid)
bcook at poughkeepsieschools.org
Thu Dec 15 04:56:50 UTC 2016
What does squidclient show?
Get a trace going..
On Dec 14, 2016 11:52 PM, "Amos Jeffries" <squid3 at treenet.co.nz> wrote:
On 15/12/2016 6:24 a.m., noc at forceline.net wrote:
> Eliezer, thanks for your reply. Guides:
> https://habrahabr.ru/post/267851/ <-- Russian lang
> https://habrahabr.ru/post/272733/ <-- Russian lang
>> First goes first change this: 13130:
> Done, nothing changed. Squid died.
> Maby it will be work fine whith lower load even with https. But I don't
> understand, why it killed by a kernel rather than just update memory by
>> Memory usage
>> /!\ Warning: Unlike the rest of this page at the time of writing, this
> section applies to Squid-3.3 and possibly later code capable of dynamic
> certificate generation and origin server certificate mimicking. The
> section text is intended primarily for developers and early adopters
> excessive memory consumption in certain SslBump environments. These notes
> may be relocated elsewhere if a better location is found.
>> Current documentation is specific to bump-server-first configurations.
> In attach server statistic.
I think you still have a forwarding loop. Does the cisco WCCP send port
443 connections from Squid to reach the Internet instead of sending them
back into Squid.
The Via header will protect against HTTP messages looping, but the TLS
handshake traffic has no such protection.
squid-users mailing list
squid-users at lists.squid-cache.org
This message may contain confidential information and is intended only for
the individual(s) named. If you are not an intended recipient you are not
authorized to disseminate, distribute or copy this e-mail. Please notify
the sender immediately if you have received this e-mail by mistake and
delete this e-mail from your system.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the squid-users