Hi, We're still looking in to solving this issue, but I'm confused as to what's causing the problem. If the memory allocated to Varnish fills up is it expected to crash like this? Or under what circumstances will it crash if the memory fills up? I thought the very nature of running it in two processes prevented these kind of situations where it needs to be manually restarted?
Thanks for all your help so far, Connor Walls From: Per Buer [mailto:[email protected]] Sent: 22 August 2012 16:12 To: Connor Walls Cc: [email protected] Subject: Re: Out of memory exception on Varnish 2.1.5 Hi Connor, On Wed, Aug 22, 2012 at 3:49 PM, Connor Walls <[email protected]<mailto:[email protected]>> wrote: Hi, We've recently been having problems with varnish being killed with out of memory problems, our logs show information like this: This is not a bug in Varnish. It is most probably a misconfiguration. You either have to little memory in your system or you are asking Varnish to use too much. I'm guessing you are using -s malloc. Remember that there is a 1k overhead on each object stored in Varnish. (..) Now, we've been planning from Varnish 2.1.5 to 3.0 for a while, and we're hoping that this will solve our issues, but I just want to check if there are known OOM issues in 2.1.5, or is the problem likely to persist after upgrading to 3.0? It will probably persist. -- [cid:~WRD000.jpg] Per Buer Phone: +47 21 98 92 61 / Mobile: +47 958 39 117 / Skype: per.buer Varnish makes websites fly! Whitepapers<http://www.varnish-software.com/whitepapers> | Video<http://www.youtube.com/watch?v=x7t2Sp174eI> | Twitter<https://twitter.com/varnishsoftware>
<<inline: ~WRD000.jpg>>
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
