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?
-T On Tue, Mar 22, 2011 at 11:46 PM, Tejaswi Nadahalli <[email protected]>wrote: > Resending the other attachments (syslog and varnishstat) > > -T > > > On Tue, Mar 22, 2011 at 11:44 PM, Tejaswi Nadahalli > <[email protected]>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 command: >> >> 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. >> >> -T >> >> >> >> >
_______________________________________________ varnish-misc mailing list [email protected] http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
