<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Okay, so there has to be something I'm doing wrong still.. I know I'm on a 32 bit system (centos), but even lowering threads, ulimit -s to all values between 32 and 1024, and even trying to adjust thread_pool_stack, I can't keep varnish running for more than 10 minutes at a time under load. <div><br></div><div>There /has/ to be something I"m doing wrong. For some reason, even though they are running, i don't have anything in syslogs. Unfortunately, I'm not the linux pro i should be to enable and get a coredump of the daemon running.</div><div><br></div><div>- Is anyone else running varnish on a 32 bit OS? (centos / redhat)</div><div>- Is seg fault and stop / start every 4-10 minutes normal in this case and should i just deal? </div><div>- If not, what startup commands are you using to keep things under control? </div><div><br></div><div>Just doesn't make sense that varnish is /this/ unstable in a 32 bit os... Seems that if it were this bad for everyone, it would be completely unusable on anything BUT 64 bit architecture. </div><div><br></div><div>(our servers are all remote, or we would have upgraded already. Doing a remote upgrade on live production servers is a bit scary as we're concerned about other libraries not functions with a new kernel, and how much debugging and fixing are we going to have to be doing!).</div><div><br></div><div>Thanks in advance ! </div><div><br></div></body></html>