Enable logs in your HAProxy configuration, configure your syslog to collect them and in the end do a tail on your log file :)
cheers On Wed, Dec 12, 2012 at 10:15 AM, Christophe Rahier <[email protected]> wrote: > Hi Baptiste, > > Just a stupid question but how can I access this log? > > Thanks, > > Christophe > > > Le 12/12/12 07:40, « Baptiste » <[email protected]> a écrit : > >>Hi, >> >>You seem to have an issue on your server side. >>Try logging the response Location header and compare it with the >>requested URL. >>Your server may be redirecting you to a URL that is still redirected to >>it. >> >>add "capture response header Location len 64" in your manager frontend >>section and share your logs here. >> >>cheers >> >>On Wed, Dec 12, 2012 at 7:03 AM, Christophe Rahier >><[email protected]> wrote: >>> Hi, >>> >>> I'd like to use haproxy with a certificate directly installed on this >>> server. For this, I copied my "key_andcert.pem". >>> >>> I use the same haproxy for our application (managers / players) with 2 >>> different official IP. >>> >>> When I try to access to my "Players", no problem. >>> >>> When I try to access to my "Managers", Chrome returns the error: "too >>>many >>> redirects". >>> >>> Please find below my config file. >>> >>> Thanks for your help and sorry for my poor English. >>> >>> Regards, >>> >>> Christophe >>> >>> >>> global >>> daemon >>> maxconn 10000 >>> stats socket /var/run/haproxy.sock level admin mode 600 >>> stats timeout 1m >>> log 192.168.0.113 local0 >>> log 127.0.0.1 local1 notice >>> defaults >>> log global >>> option dontlognull >>> retries 2 >>> timeout client 60s >>> timeout server 150s >>> timeout connect 5s >>> timeout http-keep-alive 10s >>> >>> frontend Players-Farm >>> mode http >>> option forwardfor >>> option httplog >>> option http-server-close >>> bind 192.168.0.113:443 ssl crt /etc/haproxy/key_andcert.pem >>> bind 192.168.0.113:80 >>> default_backend Players >>> >>> backend Players >>> mode http >>> server Player1 192.168.0.10:80 check on-marked-down shutdown-sessions >>> server Player2 192.168.0.11:80 check on-marked-down shutdown-sessions >>> server Player3 192.168.0.12:80 check on-marked-down shutdown-sessions >>> option httpchk HEAD /cfadmin/ping.cfm HTTP/1.0 >>> stats enable >>> balance source >>> >>> frontend Managers-Farm >>> mode http >>> option forwardfor >>> option httplog >>> option http-server-close >>> bind 192.168.0.113:444 ssl crt /etc/haproxy/key_andcert.pem >>> bind 192.168.0.113:81 >>> default_backend Managers >>> >>> backend Managers >>> mode http >>> server Manager01 192.168.0.60:80 check on-marked-down >>>shutdown-sessions >>> server Manager02 192.168.0.61:80 check on-marked-down >>>shutdown-sessions >>> option httpchk HEAD /cfadmin/ping.cfm HTTP/1.0 >>> stats enable >>> balance source >>> >>> listen info 192.168.0.113:90 >>> mode http >>> balance source >>> stats uri / >> > >
