Hi Hogan,

[I removed Cyril from the CC, he might get bored and he's on the list]

On Sat, Nov 20, 2010 at 10:46:53AM +0800, Hogan Yu wrote:
> Hi Willy,
>  I update all your suggestion
> 
>    1.  compile with USE_PCRE=1
>    2. set ulimit -m unlimited
>    3. use the two patches

perfect.

> Here is my ulimit -a list
> 
> # ulimit -a
> core file size          (blocks, -c) unlimited
> data seg size           (kbytes, -d) unlimited
> scheduling priority             (-e) 0
> file size               (blocks, -f) unlimited
> pending signals                 (-i) 139264
> max locked memory       (kbytes, -l) 32
> max memory size         (kbytes, -m) unlimited
> open files                      (-n) 65535
> pipe size            (512 bytes, -p) 8
> POSIX message queues     (bytes, -q) 819200
> real-time priority              (-r) 0
> stack size              (kbytes, -s) 10240
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) unlimited
> virtual memory          (kbytes, -v) unlimited
> file locks                      (-x) unlimited
> 
> do you think I need to change the max locked memory to a bigger value?

No, because we're not using any locked memory. All your settings look
good.

> FYI:
>    Here is the hang information when I disable the regireg command in the
> configuration file, The error code change from 6 to 4:
> 
> haproxy[26980]: segfault at 0000000020334000 rip 0000003ef9c7c3db rsp
> 00007fff8bd01398 error 4
> haproxy[1310]: segfault at 0000000021151000 rip 0000003ef9c7c4a4 rsp
> 00007fff9a1167b8 error 4
> haproxy[19029]: segfault at 0000000019f33000 rip 0000003ef9c7c4ef rsp
> 00007fff8982e158 error 4
> haproxy[25044]: segfault at 0000000020737000 rip 0000003ef9c7c4df rsp
> 00007fff73962638 error 4

OK, those might very well be the two issues that I fixed with the two
patches then.

> I will monitor the haproxy status and give your feedback it it works well.
> :)
> 
> Thanks again for your help and patience.

No, thanks to you first for your fast reports and for taking the risks to run
buggy code !

Cheers,
Willy


Reply via email to