Control: tags -1 + confirmed Hi,
Thanks for the report! On 15:07 Thu 27 Jun , Alexandra N. Kossovsky wrote: > Package: haproxy > Version: 3.0.2-1 > Severity: important > > On debian testing haproxy is killed by OOM-killer at start. I've tried > both 2.9.9-1 from testing and 3.0.2-1 from experimental. > > > 0 bash$ sudo haproxy -V -f haproxy.conf > Note: setting global.maxconn to 536870899. Now this looks suspiciously high for a max connection count. I tried starting up with your config (plus setting maxconn to 536870899) and indeed HAProxy allocated all of the system's memory. I'll dig a bit deeper to see what's going on here, i.e. why it's calculating such an absurd value and why it's preallocating so much memory. Out of curiosity, how much memory does your system have? In the meantime you can set `maxconn' in the `global' section to something sane like 50000 and it should work. Cheers, Apollon
