Score:0

haproxy "max open files" reduces automatically after startup

sd flag

I was trying to fix the following error being logged by haproxy...

Proxy https-in reached process FD limit at 544. Please check 'ulimit-n' and restart

...and added LimitNOFILE=1024 in haproxy's systemd unit file.

However, what I"m observing is that haproxy starts-up with 1024 "max open files" (confirmed via /proc/<pid>/limit), which drops back down to 544 after a few seconds.

Two related questions:

  • where is the strange 544 limit coming from?
  • apart from LimitNOFILE in systemd's unit file, is there any other file/configuration that controls this parameter?
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.