HAPROXY: backend change has no effect
-
Yesterday I encountered some strange situation in latest HaProxy-devel.
Changing a backend from port 80 to 443 seemed straightforward but didn’t work. Hovering over the entry in stats showed why: it was still using the old port 80.
Back to the backend, where 443 was shown. Saved it agin to no avail, even restarted HaProxy completely, still the same. Then cloned the backend and used the cloned backend and it worked straight away. Deleted the old unwilling backend, renamed the cloned, all fine.
Have reproduced this on another Pfsense with also lastest HaProxy-devel.
Forgot to look in the generated HaProxy config, but it must be not generated right from the Pfsense config is my best guess.
Anyone else seeing this? -
automatically generated configuration looks OK, the port change is reflected over there. Really puzzeled why HaProxy doesn't pick that up. It still uses the old port, even after a complete restart. Can see on stats page and a packet capure confirmed it.
-
I had the same issue and was really scratching my head for a few minutes before I hovered the backend name on the stats page and saw the same thing you did - the wrong port. I had to completely uninstall and reinstall the package to get it to reflect the change. No combination of disabling the service, deleting backend/frontend had any effect for me. Seems like quite the bug, but I guess it's devel for a reason.
Edit: Seems like if I toggle the backend to disabled after changing the port it updates. I don't know where the stats page/health check/etc. gets its port info from but it's definitely not from /ver/etc/haproxy/haproxy.cfg because that shows the port changes correctly.
-
Still present in HaProxy-devel 0.62_10. While workaround is simple indeed (disable backend, save and enable backend, save) it’s still annoying and I don’t understand what’s exactly happening here.