How does Ulimit-n computation works

@Vfi wrote:

I got a haproxy 1.8 vanilla alpine docker image running with maxconn = 2000

curl -s http://host:port/stats| grep maxsock
<b>maxsock = </b> 4017; <b>maxconn = </b> 2000; <b>maxpipes = </b> 0<br>

Sometimes I get the following Warning in my logs:

[WARNING] 0/0 (0) : [/usr/local/sbin/haproxy.main()] FD limit (4015) too low for maxconn=2000/maxsock=4016. Please raise 'ulimit-n' to 4016 or more to avoid any trouble.

I find it very odd since I read this in haproxy doc:

ulimit-n
Sets the maximum number of per-process file-descriptors to . By
default, it is automatically computed, so it is recommended not to use this
option.

Not sure if it’s a bug on haproxy or something I am doing wrong.

What do you think of that?

Posts: 1

Participants: 1

Read full topic