haproxy 0.63_2 weird behavior, edits not working

[iSagen]

After creating a backend, any modifications will not work after the initial creation. I have lost days trying to resolve errors. So if I used the wrong port or forgot to enable SSL, correcting the backend and trying again would fail, even if the config now was correct. The new changes would show up, but the old config was still enabled. Even restarting the service would not convert to the new changes.

Deleting the backend and creating it again, with the correct configuration the first time works.

This makes troubleshooting tedious, but at least I am aware of this behavior now.

Anyone else having the same issue?

[TheCyborgWeasel]

Yes, I can confirm that, at least partially. I simply had to enable SSL on the backend and thought the connection was secured. The SSL server was not available so I should have seen a 503. But haProxy did continue to gain access to the webserver which means that the settings were not applied correctly. Also a restart of the service did not help. Only a restart of the whole pfSense worked and applied the new SSL setting. I got a 503 then.

Strange: The other way around worked directly. Disabling SSL and hitting the apply button showed immediately the old website again, no need to restart the haProxy service or even the whole pfSense. So it is partially buggy :-)

This is reproducable!

Is this enough to open a case?

[iSagen]

@TheCyborgWeasel said in haproxy 0.63_2 weird behavior, edits not working:

Yes, I can confirm that, at least partially. I simply had to enable SSL on the backend and thought the connection was secured. The SSL server was not available so I should have seen a 503. But haProxy did continue to gain access to the webserver which means that the settings were not applied correctly. Also a restart of the service did not help. Only a restart of the whole pfSense worked and applied the new SSL setting. I got a 503 then.

Strange: The other way around worked directly. Disabling SSL and hitting the apply button showed immediately the old website again, no need to restart the haProxy service or even the whole pfSense. So it is partially buggy :-)

This is reproducable!

Is this enough to open a case?

Thank you for confirming that there is a bug in haproxy.

[andrew_cb]

@iSagen @TheCyborgWeasel
The issue is likely the same as in https://forum.netgate.com/topic/178348/haproxy-backend-port-changes-are-not-applied/

Try adding load-server-state-from-file none to the Advanced Settings > Backend pass thru section of each backend.