Icinga2 daemon -C --dump-objects

Icinga 2
1

In this link the troubleshooting documentation there is a step to run icinga2 daemon -C --dump-objects (and I found I can add --validate to it: icinga2 daemon -C --validate --dump-objects) it states to run icinga2 daemon -C --dump-objects to update the icinga2.debug cache file. I found that initial command from a warning I got when investigating some objects in Icinga: “warning/cli: This data is 271 days, 7 hours, 35 minutes and 47 seconds older than the last Icinga config (re)load. It may be outdated. Consider running ‘icinga2 daemon -C --dump-objects’ first.”

Does running icinga2 daemon -C --dump-objects or icinga2 daemon -C --validate --dump-objects cause any potential issues or impacts to a current running Icinga2 environment? Or can this safely be ran without expecting an impact, such as running icinga2 daemon -C?

Thank you.

  • Icinga Web 2 version - 2.11.4
  • Used modules and their versions (System - About) - Grafana 2.0.3, Icingadb 1.0.2, Monitoring 2.11.4
  • Web browser used - Chrome, Edge, etc
  • Icinga 2 version used (icinga2 --version) - 2.11.4
  • PHP version used (php --version) - 8.1.2-1ubuntu2.13
  • Server operating system and version - Ubuntu Linux
  • Config validation (icinga2 daemon -C) - Icinga application loader (version: r2.14.2-1)
2

I run icinga2 daemon -C after editing any config file and before applying changes (and then committing to SVC for promotion to the production environment after testing). Production runs the icinga2 daemon -C before applying any changes.

I’m sure there is some impact, but from what I can tell it forks a separate Icinga daemon which then parses all of the configuration files, checks they are valid, and - with the dump-objects flag - dumps the objects on the CLI.

I’ve never had any issues running these commands in my production environment, they seem quite safe.

3

Thank you. I will test this out.