Hi Hogan, On Wed, Nov 24, 2010 at 03:32:14PM +0800, Hogan Yu wrote: > Hi Willy, > > Sorry for give your feedback late. I test it several days and it does not > work with the new two patchs. It hang two times one day. > It still get the errors as follows, > haproxy[8728]: segfault at 000000001e90f000 rip 0000003ef9c7c51a rsp > 00007fff80e29208 error 6 > haproxy[18325]: segfault at 000000001e397000 rip 0000003ef9c7c373 rsp > 00007fff071afbd8 error 4 > haproxy[19660]: segfault at 000000001067a000 rip 0000003ef9c7c506 rsp > 00007ffff0703288 error 6 > haproxy[19955]: segfault at 0000000006a2e000 rip 0000003ef9c7c3df rsp > 00007fff15517608 error 4 > haproxy[20180]: segfault at 000000000958b000 rip 0000003ef9c7c4c8 rsp > 00007fff64b3ecb8 error 6 > > > do you think it maybe caused by enable the cookie and appsession together?
I don't see any reason why this could happen. Do you have a core file this time ? It would help a lot ! > cookie HTTPSERVERID insert nocache indirect > appsession JSESSIONID len 34 timeout 1h > should I disable the cookie and just enable the appsession to test it? You could very well try to disable one or the other in turn. > If it is cause by memory shortage, do you know how to disable the memory > limitation? Your ulimits don't report any memory limitation. You then just have to check if you still have some free memory on the system (just run the "free" command). Otherwise it's possible that we're on a very different bug. Thanks! Willy
