> I figured out what it was. When I create a DigitalOcean or AWS VM, it
> is taking the hostname (I am naming it the same as what I am proxying)
> and dumping it into the hosts file, with 127.0.0.1. I know this is out
> of the scope of a normal setup, but would be cool to throw a warning.
>
> Anyhow, all is good!
So by crashing you meant that the OOM killer terminates haproxy because
it eats up to much RAM.
A part from your forwarding loop caused by the hosts file, this means
your maxconn values are miss configured, because in this case haproxy
should hit maxconn, not eat up so much RAM that it gets terminated!
You will have to lower your maxconn values so that haproxy doesn't
eat up more RAM than you have (or swap).
Lukas
