Child Process Killed
nadahalli at gmail.com
Wed Mar 23 05:27:48 CET 2011
I found a couple of other threads involving the OOM killer.
both these cases, they had quite a few purge requests which added purge
records which never got expired and that might have caused the out of
control memory growth.
I have a similar situation - with purges happening every 15 minutes.
Mar 22 06:31:35 ip-10-116-105-253 varnishd: CLI telnet 127.0.0.1 60642
127.0.0.1 2000 Rd purge req.url ~ ^/\\?idsite=18&url=http%3A%2F%
These are essentially the 'same' purges that are fired every 15 minutes. Do
I have to setup the ban lurker to avoid out of control memory growth?
On Tue, Mar 22, 2011 at 11:48 PM, Tejaswi Nadahalli <nadahalli at gmail.com>wrote:
> I am running my Python origin-server on the same machine. It seems like the
> Python interpreter caused the OOM killer to kill Varnish. If that's the
> case, is there anything I can do prevent this from happening?
> On Tue, Mar 22, 2011 at 11:46 PM, Tejaswi Nadahalli <nadahalli at gmail.com>wrote:
>> Resending the other attachments (syslog and varnishstat)
>> On Tue, Mar 22, 2011 at 11:44 PM, Tejaswi Nadahalli <nadahalli at gmail.com>wrote:
>>> The child process got killed abruptly.
>>> I am attaching a bunch of munin graphs, relevant syslog, the current
>>> varnishstat -1 output.
>>> I am running Varnish 2.1.5 on a 64 bit machine with the following
>>> sudo varnishd -f /etc/varnish/default.vcl -s malloc,5G -T 127.0.0.1:2000-a
>>> 0.0.0.0:80 -p thread_pools=2 -p thread_pool_min=100 -p
>>> thread_pool_max=5000 -p thread_pool_add_delay=2 -p cli_timeout=25 -p
>>> session_linger=100 -p lru_interval=20 -p listen_depth=4096 -t 31536000
>>> My VCL is fairly simple, and I think has nothing to do with the error.
>>> Any help would be appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the varnish-misc