Haproxy.main: Cannot raise FD limit

Elastic Orchestration Elastic Cloud Enterprise (ECE)
1

We have only one proxy deployed (6 nodes, 3 allocators).
UI became unresponsive. We can authenticate, but get no deployments listed.
Via curl / API we can list all deployments etc.

Searching for reason we've found the following message:

ALERT] 051/133231 (106) : Cannot open configuration file/directory /app/managedd /haproxy.cfg : No such file or directory [WARNING] 051/133232 (113) : [haproxy.main()] Cannot raise FD limit to 200034, ll imit is 65536. [WARNING] 051/133232 (113) : Failed to connect to the old process socket '/app/dd ata/haproxy/haproxy.sock' [ALERT] 051/133232 (113) : Failed to get the sockets from the old process! [WARNING] 051/133232 (113) : [haproxy.main()] FD limit (65536) too low for maxcoo nn=100000/maxsock=200034. Please raise 'ulimit-n' to 200034 or more to avoid anyy trouble. [WARNING] 051/133232 (113) : Reexecuting Master process [WARNING] 051/141136 (113) : [haproxy.main()] Cannot raise FD limit to 200034, ll imit is 65536.

The proxy container runs in unprivileged state, so we can't set ulimit to another value.
How can we proceed?

TIA,
Agnes

...
on the other hand the API-Call says proxy is healthy

 ... api/v1/platform/infrastructure/proxies

"proxies": [{
    "public_hostname": "...",
    "runner_id": "...",
    "healthy": true,
    "proxy_id": "...",
    "host_ip": "...",
    "metadata": {
    }
  }]
2

Solved: Reason certificate has to be renewed.

1 Like