I just installed HAProxy 2.5.1 on a new system planing to move it there, compilation was error-free on the first try, first time I get it right on the first time too. The system, runs Red Hat Enterprise Linux 8.5, same as the last one, the configuration file, certificates, errorpages all were rsynced from the other system in the same locations but when HAProxy attempts to start basically most keywords are unrecognized.
Despite an error- and warning-free validation of the file it won’t start. Could PCRE be generating this error?
Compared to the last server I there are two things I did differently; (1) I changed to the newer version 2.5.1 but only a point update from 2.5.0. Going from 2.4 to 2.5 didn’t break things so I doubt this is it. The second is that I compiled the server with PCRE2; the site says the last PCRE — 1 — is EOL, it made sense to go for the next number up. The release I got from the package manager is dated from 2018 so not bleeding edge either.
haproxy -vv (click for more details)I also thought for a minute that the file’s encoding could the issue but both systems are configured nearly identical. I stay away from encoding, SSH configuration, locales, etc bc I use macOS and Windows to connect from and it gets messy fast first with line break errors. Neither cat or vim or the basic GNOME text editor show anything in the lines nor in the lines surrounding where the errors are supposed to be (…and the validation passes.)
Thanks in adv for your help.
1 post - 1 participant