Thanks everyone for the advice. Upgrade now completed without any major
problems.
I couldn't get my original stats config to work (currently just removed).
Can anyone suggest how I should update this please?:
listen stats :1234
stats auth xxxxx:xxxxx
stats uri /
stats realm Haproxy\ Statistics
stats hide-version
stats enable
mode http
On 21 October 2015 at 23:26, Cyril Bonté <[email protected]> wrote:
> Hi all,
>
> Le 21/10/2015 22:16, Lukas Tribus a écrit :
>
>> On Wed, Oct 21, 2015 at 7:14 PM, SL <[email protected]> wrote:
>>>
>>>> I'll be doing an upgrade from 1.4 to 1.6 tomorrow. Just wondering if
>>>> there
>>>> are any changed defaults, breaking changes, anything like that? Or
>>>> should
>>>> my config work as before?
>>>>
>>>
>>> Haproxy 1.5 changed the default connection mode if you use http. Up to
>>> version 1.5-dev21 "option tunnel" was the default, now it's "option
>>> http-keep-alive".
>>> https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#4
>>>
>>> This bit me a bit, when I upgraded from 1.4 to 1.5, as the tunnel mode
>>> works a bit different. But with settings "option http-keep-alive" and
>>> "option prefer-last-server" specified, everthing was fine.
>>>
>>
>> Yeah, I think thats about the most important change, even between 1.4
>> and 1.6.
>>
>> Definitely use latest 1.6.1 if you want to go with 1.6 already.
>>
>> I don't expect that the new release silently breaks old configurations,
>> however you may wanna do some testing before going into production.
>>
>
> For the configuration itself, before replacing your 1.4 instance with a
> 1.6.x version, you can install a 1.6.x version beside the running 1.4 one,
> and use "haproxy -c" to check the configuration. As Lukas said, warnings
> will be emitted if the configuration is not compatible anymore (except for
> the HTTP mode, which only change the behaviour but isn't directly a
> configuration compatibility issue).
>
> Incompabilities :
> - you can't specify [<ip>]:<port> on a "listen"/"frontend" line, you'll
> have to explicitly specify a "bind" line inside the section.
>
> Example :
> listen test :80
> must be written as :
> listen test
> bind :80
>
> Warning displayed :
> [ALERT] ... 'listen' cannot handle unexpected argument ':80'.
> [ALERT] ... please use the 'bind' keyword for listening addresses
>
> - The "appsession" keyword has been removed and should be replaced with
> stick-tables.
>
> Warning displayed :
> [ALERT] ... 'appsession' is not supported anymore, please check the
> documentation.
>
> --
> Cyril Bonté
>
>
