Hello,
I setup an distributed Icinga2 system with a master and multiple clients
(actually multiple Debian kvm VMs on the same host). The master has
endpoints with addresses of all the clients and the clients have endpoints
with only the name of the master setup like this:
--- zones.conf on master
Little confused about why new hosts in /etc/icinga2/conf.d/ directory are
not showing up after restart. Does each host need its own .conf file or are
they supposed to be configured in the one hosts.conf file?
Disabled features: compatlog debuglog gelf graphite influxdb opentsdb
perfdata statusdata
On Wednesday 19 July 2017 at 17:30:14, Garrett Pye wrote:
> Little confused about why new hosts in /etc/icinga2/conf.d/ directory are
> not showing up after restart.
Are you saying that old hosts, which were there before, are still showing up,
but *new* ones aren't?
Or is this a new installatio
All very good questions and apologize for being generic in my initial post.
This is a new install of icingaweb2. The primary configuration is existing
hosts is configured to use Nagios; nrpe.cfg and plugins are already
established and looking to migrate the fleet of Linux servers to IcingaWeb.
I h
On 19.07.17 19:05, Garrett Pye wrote:
*[root@bcv-devops-icinga icinga2]# icinga2 daemon -C*
information/cli: Icinga application loader (version: v2.6.3)
information/cli: Loading configuration file(s).
warning/ConfigCompiler: Cannot compile file
'/etc/icinga2/conf.d/host/baschisp02.conf': Error:
You have got to be kidding!? That was the issue and now host is showing up.
Completely overlooked the obvious.
Thank you
//Garrett
On Wed, Jul 19, 2017 at 11:15 AM, Gerald Vogt wrote:
> On 19.07.17 19:05, Garrett Pye wrote:
>
>> *[root@bcv-devops-icinga icinga2]# icinga2 daemon -C*
>> informa
