Icinga client connection running in loop

Icinga 2
1

Hi there,
I am new to Icinga2 and I need help with an issue. I successfully run Icinga2 (r2.10.2-1) on CentOS 7 with Icinga2web (2.6.2) and the director (1.6.0). I have more than 100 machines connected (with active checks) and the mostly monitored well. I checked the /var/log/icinga2/icinga2.log and I suggest, that it grows very fast to multiple GBs. When I took a like inside I recognized, that Icinga doing the connections to it´s client in the loop (I could not better explain it). The logfile always shows the same for every node (example for one node):

[2021-03-22 14:41:33 +0100] information/ApiListener: 
New client connection for identity 'node55268.domain.com' from [10.42.27.28]:57828
[2021-03-22 14:41:33 +0100] information/ApiListener: 
Sending config updates for endpoint 'node55268.domain.com' in zone 'node55268.domain.com'.
[2021-03-22 14:41:33 +0100] information/ApiListener: 
Syncing configuration files for global zone 'director-global' to endpoint 'node55268.domain.com'.
[2021-03-22 14:41:33 +0100] information/ApiListener: 
Finished sending config file updates for endpoint 'node55268.domain.com' in zone 'node55268.domain.com'.
[2021-03-22 14:41:33 +0100] information/ApiListener: 
Syncing runtime objects to endpoint 'node55268.domain.com'.
[2021-03-22 14:41:33 +0100] information/ApiListener:
 Finished syncing runtime objects to endpoint 'node55268.domain.com'.
[2021-03-22 14:41:33 +0100] information/ApiListener:
Finished sending runtime config updates for endpoint 'node55268.domain.com' in zone 'node55268.domain.com'.

This is happening for each node which is connected to Icinga.

Do you have an idea?
Thanks
Jens

2

Hi & welcome to the icinga community,

You’re using outdated versions. I’d recommend to update first.

3

Hello Roland,
ok, I updated icinga2 to 2.12.0-1. Still the same problem. Every registered node generates these log entries in the loop.

And as an extra bonus, I got this message (of course in loop):

[2021-03-23 06:54:00 +0100] critical/ApiListener: 
Cannot accept new connection: Too many open files
4

v2.12.3 is the most current and there were some bug fixes in the area of communication (as you can read here).

The message from your log is incomplete. Here you’ll find tips for proper formatting.