Problem with haproxy v1.8

[tkald]

Multibinder haproxy-multi@service dies with latest haproxy version 1.8.

Nov 29 10:55:01 LB2 multibinder-haproxy-wrapper[15875]: /var/lib/gems/2.3.0/gems/multibinder-0.0.5/bin/multibinder-haproxy-wrapper:62:in `waitpid': No child processes (Errno::ECHILD)
Nov 29 10:55:01 LB2 multibinder-haproxy-wrapper[15875]: #011from /var/lib/gems/2.3.0/gems/multibinder-0.0.5/bin/multibinder-haproxy-wrapper:62:in `block in <top (required)>'
Nov 29 10:55:01 LB2 multibinder-haproxy-wrapper[15875]: #011from /var/lib/gems/2.3.0/gems/multibinder-0.0.5/bin/multibinder-haproxy-wrapper:61:in `loop'
Nov 29 10:55:01 LB2 multibinder-haproxy-wrapper[15875]: #011from /var/lib/gems/2.3.0/gems/multibinder-0.0.5/bin/multibinder-haproxy-wrapper:61:in `<top (required)>'
Nov 29 10:55:01 LB2 multibinder-haproxy-wrapper[15875]: #011from /usr/local/bin/multibinder-haproxy-wrapper:23:in `load'
Nov 29 10:55:01 LB2 multibinder-haproxy-wrapper[15875]: #011from /usr/local/bin/multibinder-haproxy-wrapper:23:in `<main>'
Nov 29 10:55:01 LB2 systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Nov 29 10:55:01 LB2 systemd[1]: [email protected]: Unit entered failed state.
Nov 29 10:55:01 LB2 systemd[1]: [email protected]: Failed with result 'exit-code'.

[theojulienne]

haproxy 1.8 now includes support for reusing binds from a previous invocation 🎉 (very similar to the way multibinder works), so unless your application gets benefit from multibinder being a separate process, it might be worth looking at using that feature directly. Was there a particular use case you had in mind that would make multibinder preferable over haproxy managing the binds directly?

[tkald]

Thank you!
No I don't have any special use case.