Hello Björn,
On Wednesday, 18 September 2019, Björn Jacke <b...@sernet.de> wrote: > Hi, > On 2019-09-18 at 01:23 +0200 Lukas Tribus sent off: > > On Wed, Sep 18, 2019 at 1:14 AM PR Bot <haproxy-pr-bot-no-re...@ltri.eu> > wrote: > > > Description: > > > systemd by default limits the max open files to 1k, which also > limits > > > the socket connections to 1k, the service script must be told to > > > remove the limit. > > > > Since haproxy is started as root we have the privilege to bump the > > ulimit ourselfs. We cannot rely on init scripts or systemd to set > > correct values. The values are computed automatically based on maxconn > > configuration and then set accordingly by haproxy itself. > > hm, and how come that the stats page shows: > > system limits: memmax = unlimited; ulimit-n = 1023 > maxsock = 1023; maxconn = 240; maxpipes = 0 > > unless the systemd limit is removed with the change I made in the systemd > service file? Because with a global maxconn configuration of 240, haproxy does not need to configure more. Like I said, this is based on maxconn (ulimit will be about twice the maxconn value with some overhead). If you want to see the ulimit value move, bump your global maxconn and you will see how haproxy adjusts the ulimit. lukas
