-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

The EPEL packagers have recently updated HAProxy from 1.3.14 to 1.3.18,
and it seems this has broken my previously working config.

I haven't really been watching the mailinglist closely lately so please
excuse me if this has been discussed earlier. (I did do a quick scan of
the archives and couldn't find anything that stood out as useful.)

My previously working config looks like this :

global
        log             127.0.0.1 local0 err
        maxconn         2000
        uid             0
        gid             0
        daemon
        nbproc          1

defaults
        log             global
        mode            http
        option          dontlognull
        clitimeout      150000ms
        srvtimeout      150000ms
        balance         roundrobin

frontend Loadbalancer
        bind            192.168.0.100:80 transparent
        maxconn         10000
        option          forwardfor
        option          httplog
        default_backend modperlpool

backend modperlpool
        stats enable
        stats uri       /some-stats-uri
        stats realm     Haproxy\ Statistics
        stats auth      someuser:somepass
        stats refresh   10s
        option          httpchk
        option          redispatch
        option          httpclose
        contimeout      8000ms
        retries         3
        server          apachemodperl1 192.168.0.20:8080 check weight 12
        server          apachemodperl2 192.168.0.30:8080 check weight 5


When doing a configcheck I get this :

# haproxy -f /etc/haproxy/haproxy.cfg -c
[ALERT] 173/104901 (31532) : parsing [/etc/haproxy/haproxy.cfg:23] :
'bind' : 'transparent' option not implemented.
[ALERT] 173/104901 (31532) : Error reading configuration file :
/etc/haproxy/haproxy.cfg

Simply removing transparent on the bind seems to work, but I get a lot
of warnings I cannot remember (is this simply check being more verbose
currently?) :

# haproxy -f /etc/haproxy/haproxy.cfg -c
[WARNING] 173/105045 (31750) : parsing [/etc/haproxy/haproxy.cfg:26] :
'httpchk' ignored because frontend 'Loadbalancer' has no backend capability.
[WARNING] 173/105045 (31750) : parsing [/etc/haproxy/haproxy.cfg:27] :
'redispatch' ignored because frontend 'Loadbalancer' has no backend
capability.
[WARNING] 173/105045 (31750) : parsing [/etc/haproxy/haproxy.cfg:31] :
connect timeout will be ignored because frontend 'Loadbalancer' has no
backend capability
[WARNING] 173/105045 (31750) : parsing [/etc/haproxy/haproxy.cfg:32] :
'retries' ignored because frontend 'Loadbalancer' has no backend capability.
[WARNING] 173/105045 (31750) : parsing /etc/haproxy/haproxy.cfg :
missing timeouts for backend 'localmodperl'.
   | While not properly invalid, you will certainly encounter various
problems
   | with such a configuration. To fix this, please ensure that all
following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
Configuration file is valid : /etc/haproxy/haproxy.cfg


It seems my config isn't exactly optimal, and I guess my HAProxy
configuration confusion continues :P Any help / tips would be highly
appreciated.

Regards
- --
Denis Brækhus
Redpill Linpro AS - Changing the game

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpAnDcACgkQlH2KYzu3lONu1ACggVRQibNq2JqKThbyRgMLXkmd
fVAAn3tR4xVXOA3FAp9oVgM70AxdAVMy
=aEWF
-----END PGP SIGNATURE-----

Reply via email to