[dev.icinga.com #12649] Allow increasing resource limits

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12649

Created by jonan on 2016-09-06 04:17:10 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-11-18 14:01:15 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

---

My environment is hitting the file descriptor resource limit. This appears to be hard coded in Application::SetResourceLimits() . Please provide a method to increase this beyond 16384.

The problem manifests as failed API connections or checks failing with: "Error: Function call 'pipe2' failed with error code 24, 'Too many open files'"

FYI, I have tried increasing with ulimit as well as recompiling with increased limit for RLIMIT_NOFILE but the limit never increases beyond 16384. My usage is mostly from the API which receives 10 - 15k connections per minute.

Running Ubuntu 14.04 and Icinga 2.5.3

[icinga-migration]

Updated by jonan on 2016-09-07 09:28:32 +00:00

Some additional information. Icinga doesn't seem to handle exhaustion gracefully, process often locks up and does not respond when hitting the limit. Only restarting resolves this.

ls /proc/8658/fd/ | wc -l
16384

[icinga-migration]

Updated by thoughtfix on 2016-11-17 20:52:22 +00:00

+1 on this one. Additionally the non-graceful exit spams "too many files open" errors to the error log at an extremely high rate, filling up the log partition.

[icinga-migration]

Updated by thoughtfix on 2016-11-17 20:57:19 +00:00

Update on my intended environment:

1200 hosts (13k total checks) divided across 3 zones, each zone with a local icinga2 satellite, pdo_pgsql and icingaweb running on a different host compiling from all three zone satellites. Ubuntu 12.04. Icinga 2.5.4

PR: #111

[icinga-migration]

Updated by mfriedrich on 2016-11-18 14:01:15 +00:00

• Category set to libbase

[dnsmichi]

That's already implemented and can be adjusted with environment variables.