nagios-charmers team mailing list archive

[Xav Paice <xav.paice@xxxxxxxxxxxxx>]

So far, I've been unable to reproduce Aurelien's reproducer, but I'm
also aware that the Nagios charm takes a while to complete all the
iterations of monitors-relation-changed.  The hook does include a
service reload, and on my tests I have seen new hosts appear in the list
after some time, without a restart.

The original bug is regarding nagios.cfg, which is affected by only a
few config changes.  If this needs a restart rather than a reload, we'd
see it by changing a service check to force it to timeout (nrpe checks
have a different error), and viewing the result and if it behaves as
expected after changing service_check_timeout_state=u.

Testing showed that even manually updating nagios.cfg, and service
definition files, and using reload, is enough to trigger Nagios to
notice the change.  I've therefore been unable to reproduce the actual
problem, although I confirm that the service isn't restarted (which is
OK).

** Changed in: charm-nagios
       Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Nagios
Charm developers, which is subscribed to Nagios Charm.
https://bugs.launchpad.net/bugs/1834976

Title:
  config-changed doesn't restart nagios3 when config file is modified

Status in Nagios Charm:
  Invalid

Bug description:
  If a hook modifies /etc/nagios3/nagios.cfg, we need the service to
  restart to collect that change, but the hook doesn't initiate that
  service restart.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nagios/+bug/1834976/+subscriptions