Simple as that. Version 1.7 worked fine in FreeBSD 10.3. Now 1.8 with the same config blocks indefinitely when I run
haproxy -f /usr/local/etc/haproxy.conf -p /var/run/haproxy.pid
Which worked before. If I add -D it will detach and run in the background. But this wasn't necessary in FreeBSD 10.3 and/or version 1.7.x.
The worst thing is that if you reboot your computer with haproxy enabled in /etc/rc.conf you will never be able to access it via ssh again since haproxy runs before sshd (in rcorder).
I'm wondering if this is a misconfiguration issue (-D not being used in port's rc script, but then again, it wasn't required in previous FreeBSD and/or haproxy), or if FreeBSD changed how it loads scripts (but other daemons from ports like nginx come up fine).
service haproxy start
. The command run (from its rc.d script) ishaproxy -f /usr/local/etc/haproxy.conf -p /var/run/haproxy.pid
Which worked before. If I add -D it will detach and run in the background. But this wasn't necessary in FreeBSD 10.3 and/or version 1.7.x.
The worst thing is that if you reboot your computer with haproxy enabled in /etc/rc.conf you will never be able to access it via ssh again since haproxy runs before sshd (in rcorder).
I'm wondering if this is a misconfiguration issue (-D not being used in port's rc script, but then again, it wasn't required in previous FreeBSD and/or haproxy), or if FreeBSD changed how it loads scripts (but other daemons from ports like nginx come up fine).