Hi Greg,
> Connect() failed for backend frontend: no free ports.
> Connect() failed for backend frontend: no free ports.
> Connect() failed for backend frontend: no free ports.
> Connect() failed for backend frontend: no free ports.
> Connect() failed for backend frontend: no free ports.
> Connect() failed for backend frontend: no free ports.
>
> Which is not saying anything to me.
>
> So anybody know what resource "free ports" relates to in the unix
> domain socket case? Are there any other debug options to find out
> more about what is happening.
I suspect the connect() call returns EAGAIN, this makes haproxy
come up with the "no free ports" message, which yes, doesn't
make that much sense in a unix domain socket world.
What kernel are you using here?
Are you sure the backend is ready to accept new connections?
What happens if you connect (socat) to the backend manually, while
in this condition?
Can you strace while in this condition to confirm the we see EGAIN
return code (strace -ttT -o haproxy-trace.txt -p $(pidof haproxy))?
Regards,
Lukas
