haproxy 3.1.0 fails to fully start

[drboone]

Our haproxy guest got updated to haproxy-3.1.0 this morning. After an extended period of searching, I realized that none of the listen ports were actually in use. Some fiddling with truss -f seems to show that the master process starts its first worker, which never really makes any progress, and there's just no further truss output. There's a message "Failed to load worker".

Falling back to 3.0.6 has us back on the air for now.

Platform 20241017T041739Z.

Apologies for the crappy bug report.

[jperkin]

Are you able to share any non-sensitive parts of your config? At least with a basic proxy setup 3.1.0 works ok for me, so I wonder if this is due to specific features.

[drboone]

Interesting. Unfortunately my test install is also my production install so I don't have a good way to generate a minimum test case right now.

I think the secrets are all out of the attached full config. I should extract a promise not to laugh... :)
haproxy.cfg.txt

Sorry I missed your question for so long.