Hello Alexandre,

On Fri, Oct 16, 2009 at 01:22:03PM +0000, alexandre oliveira wrote:
> 
> Hello. I've downloaded, compiled and installed haproxy version 1.3.20 in one 
> SUSE Linux Enterprise Server 10 (s390x), VERSION = 10, PATCHLEVEL = 2.
> 
>  
> 
> I start the haproxy with command line: /usr/sbin/haproxy -f 
> /etc/haproxy/haproxy.cfg -d
> 
> and I make some tests with HTTP and HTTPS. At first it works fine, but few 
> moments later I get the message: Segmentation fault

This should not happen at all !

Can you send the output of "haproxy -vv" and "uname -a" ? Also,
could you check if it still happens when you use "-db" instead
of "-d" ? It will disable debugging output but still stay in
foreground. I have a feeling that this may be specific to the
debugging output, which is rarely used.

> I dont know what to do to solve this trouble. Any tip?

Your config is so much simple that I'd bet a debugging issue
first. I have a few minor comments about your config below.
Also, please run a test on 1.3.22 which is the most recent
stable release.

> Follow is the haproxy.cfg file:
> 
> ##########################################################
> 
> global
>         log 127.0.0.1   local0
>         log 127.0.0.1   local1 notice
>         maxconn 4096
>         debug
> 
> 
> defaults
>         log     global
>         mode    tcp
>         option  httplog
>         option  httpclose

"option httplog" and "option httpclose" will not be used in TCP
mode, you can remove them.

>         option  dontlognull
>         retries 1
>         contimeout      500
>         clitimeout      5000
>         srvtimeout      5000
> 
>  
> 
> listen  uat 0.0.0.0:80,0.0.0.0:443
>         balance source
>         option      ssl-hello-chk
>         option      forwardfor

"option forwardfor" above will be ignored since you're in TCP, so
you can safely remove it.

>         server  server_first  192.168.0.1 weight 1 maxconn 5000 check
>         server  server_seco  192.168.0.2 weight 1 maxconn 5000 check

Please keep me informed !

Willy


Reply via email to