I chose to go to SSH way instead. I now managed to get the Icinga2 configuration working, thanks to Gerald. I'm now left with host key verification and private key permission issues, which I hope to resolve soon!
Thanks a lot! -Gijs On 10-10-2017 01:04, Antony Stone wrote: > On Tuesday 10 October 2017 at 00:22:51, Matthew Herzog wrote: > >> You do not want to install Icinga2 on all the hosts you need to monitor. > Why not? That is a perfectly standard way to configure client machines. > > Why do you recommend not doing this? > >> There is no Icinga agent. > Technically, correct - there is no separate application/binary for "Icinga > agent" in the same way that there's a separate Zabbix agent, or Nagios' NRPE. > > On the other hand, Icinga itself is lightweight and designed to be installed > on all monitored machines, so it *is* both the server and the "agent" if you > want to call it that when it's operating in client mode. > > The problem faced by Gijs is certificate validation; I don't know whether he > has managed to resolve it in the time since September 17th, but there surely > is a way to get this working, with Icinga installed normally on all monitored > machines. > > > Antony. > >> On Sun, Sep 17, 2017 at 5:27 AM, Gijs Rijnders wrote: >>> Dear Icinga2 users, >>> >>> I have an Icinga2 master node, and I want to monitor other Linux hosts >>> for apt package availability. I read that I have to install Icinga2 >>> locally as Satellite on every host, and connect it to the master node. I >>> installed Icinga2 in satellite mode on some Linux host, and tried to >>> connect it to the master. It can connect just fine, but it does not >>> accept connections. I get the following errors: >>> >>> [2017-09-17 11:22:22 +0200] warning/JsonRpcConnection: API client >>> disconnected for identity 'icinga2.master' >>> [2017-09-17 11:22:37 +0200] information/ApiListener: Reconnecting to API >>> endpoint 'icinga2.master' via host 'icinga2.master' and port '5665' >>> [2017-09-17 11:22:37 +0200] warning/ApiListener: Certificate validation >>> failed for endpoint 'icinga2.master': code 21: unable to verify the >>> first certificate >>> >>> Context: >>> (0) Handling new API client connection >>> >>> I ran the 'icinga2 node wizard' on the satellite and all configuration >>> seems to be correct. What could be wrong? Did I misconfigure something? >>> >>> Thanks in advance! >>> >>> Kind Regards, >>> >>> Gijs Rijnders _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
