max_check_attempts None
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nagios Charm |
Fix Released
|
High
|
Unassigned |
Bug Description
Charm shouldn't put in None for max_check_attempts.
Give it a default possibly?
define service {
use generic-service
check_command check_nrpe_
host_name bootstack-
service_
max_check_
}
Error: Invalid max_attempts, check_interval, retry_interval, or notification_
Error: Could not register service (config file '/etc/nagios3/
Error processing object config files!
***> One or more problems was encountered while processing the config files...
Check your configuration file(s) to ensure that they contain valid
directives and data defintions. If you are upgrading from a previous
version of Nagios, you should be aware that some variables/
may have been removed or modified in this version. Make sure to read
the HTML documentation regarding the config files, as well as the
'Whats New' section to find out what has changed.
sed '/max_check_
Changed in charm-nagios: | |
status: | New → Fix Committed |
status: | Fix Committed → In Progress |
Changed in charm-nagios: | |
importance: | Undecided → High |
Changed in charm-nagios: | |
milestone: | none → 21.04 |
I "think" this may be fixed in cs:nagios-42. To be verified.