Dear all,
this is my very first post in this forum so a big hello to everybody and thank you to anybody who will spend a little time to help me.
I inherited a quite old setup with haproxy 1.5 and 2 backends. What’s the correct path to update it to a recent 3.x release? Can I just drop the new executable keeping the same configuration files?
Thank you for your kind support
Gaetano
Hi ghap,
I would make a current executable available under an alternative path or name, without overwriting the original one.
Then, I would use the new executable to check the old configuration:
/path_to_new/haproxy_3.x -c -f /path/to/configfile
The output is very helpful and would guide you to the parts that need changing.
I agree with @mrks that is indeed a good start. It’s possible you are using some of the features that have been removed (like URI rewriting changed since 1.5). Running the old config against a modern executable with the -c flag will tell you what’s wrong with it.
Also, you should probably update your init script or systemd unit file, the tarball will come with new examples.
Please make sure you are running a modern LTS branch if you are not looking to upgrade between major releases every year. You can find informations about this on the top of the haproxy.org page.
Hello and thank you so much to everybody.
I will surely proceed this way, so that I will be able to check the configuration before trying it in real traffic.
As far as I can understand, I can try jumping directly to the latest version and that’s good.
I will post the outcome here and keep you posted.
Servers are running RedHat 8.10, I hope it can be considered a modern LTS
Have a nice day.
Gaetano
What I meant was haproxy LTS, not your OS.
For example, Haproxy 3.2 and 3.4 branch are LTS version, while 3.3 is not.
Study the version table on haproxy.org to make a decision, based on your expected EOL requirements.
I see what you mean @lukastribus , my misunderstanding.
I will study the version table and make the decision.
Thank you
Gaetano