Nagios peer config error: Could not find any host matching 'juju-placement-1'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nagios Charm |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Nagios dashboard fails with:
-------
[1637248412] Nagios 3.5.1 starting... (PID=16822)
[1637248412] Local time is Thu Nov 18 15:13:32 UTC 2021
[1637248412] LOG VERSION: 2.0
[1637248412] livestatus: Livestatus 1.2.8p16 by Mathias Kettner. Socket: '/var/lib/
[1637248412] livestatus: Please visit us at http://
[1637248412] livestatus: Hint: please try out OMD - the Open Monitoring Distribution
[1637248412] livestatus: Please visit OMD at http://
[1637248412] livestatus: Warning: environment_macros are enabled. This might decrease the overall nagios performance
[1637248412] livestatus: Finished initialization. Further log messages go to /var/log/
[1637248412] Event broker module '/usr/lib/
[1637248412] Error: Could not find any host matching 'juju-placement-1' (config file '/etc/nagios3/
[1637248412] Error: Could not expand members specified in hostgroup (config file '/etc/nagios3/
[1637248412] Bailing out due to one or more errors encountered in the configuration files. Run Nagios from the command line with the -v option to verify your config before restarting. (PID=16822)
[1637248412] livestatus: deinitializing
[1637248412] Caught SIGSEGV, shutting down...
-------
-------
ubuntu@nagios2-2:~$ cat /etc/nagios3/
# Configuration file /etc/nagios3-
# Edited by PyNag on Mon Nov 22 18:59:07 2021
define hostgroup {
notes #autogenerated#
members juju-placement-
}
-------
Running
$ juju status --model foundations-
and
$ juju status --model foundations-
Shows that placement/0 and placement/1 and nagios/0 are all happy and alive.
Maybe the problem is that placement is on model foundations-
no longer affects: | charm-placement |
This charm is no longer being actively maintained. There is no further update of this issue over 1 year. We will close it. /charmhub. io/topics/ canonical- observability- stack).
Please consider using the new Canonical Observability Stack instead.
(https:/