CLI removes Endpoint and Zone of an Agent

Hello,

i’m a bit confused, because since a couple of days i fight with the icinga-cli.

I have a host configured as an agent which is working fine.

A couple of minutes (1 to 10 Minutes) after the correct setup and deployment via Director i get a entry in the activity log waiting for deployment where “cli” removes the Endpoint and Zonesettings of this host.

I stopped all regarding import-jobs to see if it changes anything. -> didn’t help

Confused greetings…

Hi,

can you share screenshots and logs to illustrate your problem better? Also, include the involved versions of Director and Icinga 2.

Cheers,
Michael

Hello Michael,

icinga
icingaweb2 is 2.6.3
director is from January
icinga is 2.10.4

Just to be complete:
Agent a Debian 9 and also a icinga 2.10.4
Other Agents are working fine.

I currently lost the Agent again at 12:36:40

Log from agent:

[2019-05-17 12:34:32 +0200] information/RemoteCheckQueue: items: 0, rate: 0/s (12/min 60/5min 180/15min);
[2019-05-17 12:35:32 +0200] information/RemoteCheckQueue: items: 0, rate: 0/s (12/min 60/5min 180/15min);
[2019-05-17 12:36:02 +0200] information/RemoteCheckQueue: items: 0, rate: 0/s (6/min 30/5min 90/15min);
[2019-05-17 12:36:12 +0200] information/RemoteCheckQueue: items: 0, rate: 0/s (12/min 60/5min 180/15min);
[2019-05-17 12:36:16 +0200] information/ConfigObject: Dumping program state to file ‘/var/lib/icinga2/icinga2.state’
[2019-05-17 12:36:22 +0200] information/RemoteCheckQueue: items: 0, rate: 0/s (12/min 60/5min 180/15min);
[2019-05-17 12:36:42 +0200] information/RemoteCheckQueue: items: 0, rate: 0/s (6/min 30/5min 90/15min);
[2019-05-17 12:37:32 +0200] information/RemoteCheckQueue: items: 0, rate: 0/s (6/min 30/5min 90/15min);

Log from icinga:

[2019-05-17 12:35:25 +0200] information/WorkQueue: #8 (IdoPgsqlConnection, ido-pgsql) items: 6, rate: 9.48333/s (569/min 2789/5min 5169/15min);
[2019-05-17 12:35:35 +0200] information/WorkQueue: #8 (IdoPgsqlConnection, ido-pgsql) items: 7, rate: 9.96667/s (598/min 2813/5min 5271/15min);
[2019-05-17 12:35:55 +0200] information/WorkQueue: #8 (IdoPgsqlConnection, ido-pgsql) items: 1, rate: 10.45/s (627/min 2809/5min 5482/15min);
[2019-05-17 12:36:05 +0200] information/WorkQueue: #8 (IdoPgsqlConnection, ido-pgsql) items: 7, rate: 10.0333/s (602/min 2809/5min 5562/15min);
[2019-05-17 12:36:25 +0200] information/WorkQueue: #8 (IdoPgsqlConnection, ido-pgsql) items: 1, rate: 9.56667/s (574/min 2827/5min 5754/15min);
[2019-05-17 12:36:30 +0200] information/ConfigObject: Dumping program state to file ‘/var/lib/icinga2/icinga2.state’
[2019-05-17 12:36:35 +0200] information/WorkQueue: #8 (IdoPgsqlConnection, ido-pgsql) items: 7, rate: 9.08333/s (545/min 2831/5min 5833/15min);
[2019-05-17 12:36:45 +0200] information/WorkQueue: #8 (IdoPgsqlConnection, ido-pgsql) items: 7, rate: 8.66667/s (520/min 2818/5min 5919/15min);
[2019-05-17 12:36:55 +0200] information/WorkQueue: #6 (ApiListener, RelayQueue) items: 0, rate: 10.65/s (639/min 3314/5min 6990/15min);
[2019-05-17 12:36:55 +0200] information/WorkQueue: #5 (InfluxdbWriter, influxdb) items: 0, rate: 3.58333/s (215/min 1122/5min 2286/15min);
[2019-05-17 12:36:55 +0200] information/WorkQueue: #7 (ApiListener, SyncQueue) items: 0, rate: 0/s (0/min 0/5min 4/15min);
[2019-05-17 12:36:55 +0200] information/WorkQueue: #8 (IdoPgsqlConnection, ido-pgsql) items: 7, rate: 8.58333/s (515/min 2814/5min 6008/15min);
[2019-05-17 12:36:59 +0200] information/WorkQueue: #11 (JsonRpcConnection, #0) items: 0, rate: 1.06667/s (64/min 308/5min 675/15min);
[2019-05-17 12:37:05 +0200] information/WorkQueue: #8 (IdoPgsqlConnection, ido-pgsql) items: 7, rate: 8.9/s (534/min 2808/5min 6105/15min);
[2019-05-17 12:37:15 +0200] information/WorkQueue: #8 (IdoPgsqlConnection, ido-pgsql) items: 7, rate: 9.08333/s (545/min 2838/5min 6217/15min);
[2019-05-17 12:37:25 +0200] information/WorkQueue: #8 (IdoPgsqlConnection, ido-pgsql) items: 7, rate: 8.78333/s (527/min 2819/5min 6290/15min);

cli also removes the display_name.

So you’re using git master and not a stable release? Which git commit are you at and why?

Cheers,
Michael

Yes, i clone directly from GIT.
And to be honest… That’s the way i do it since it use Director. Maybe i missed te part of “releases”.

I try now 1.6.2 and keep you informed.

Maybe it’s something with the Import source. We had at the beginning similar problems. We do that with csv files and the data come from an internal CMDB. There we added a flag like “Icinga Agent” to the hosts. If this is set, I add in the CSV the fields “Agent”, “Master_Connect” and “Accept_Config” and synced it, than it works for us.