Nagios Support Forum

I get errors on numerous hosts after putting them in maintenance mode for several hours , any ideas how to fix? everything looks ok and services are fine but down time reporting is messed up now.

status Information: CONFIG IS FALSEGroup state is: Ok: 6 Child Problems

By maintenance mode, do you mean you put them in downtime? Is that status information from another check of some sort, like check_cluster? Please provide more details, or possibly a screenshot of what has been done to this system, what is happening presently, and what you feel it should be doing.

sorry yes, I put in scheduled downtime for a set period of time
it seemed to come out of scheduled downtime ok but when I look at a hosts status I see the error

see attached screenshot from Nagios dashboard and Nagios core

sheetzdw wrote:status Information: CONFIG IS FALSEGroup state is: Ok: 6 Child Problems

This looks like BPI output. Can you post the configuration and check command for of these problematic hosts?

I would be glad to, not sure where to look ...

I assume on the Nagios server I can find these check commands? not sure which directory to search and I am lousy with Linux

How did you configure those checks? Does the person who configured them have any idea how they were set up? It looks like either Core BPI, or some strange check for aggregating results. The error you are receiving is not from nagios its output from the check, who's identity you have not been able to tell us. You configurations (if using Centos/rhel) should be in the standard location of:
Please see:

http://nagios.sourceforge.net/docs/3_0/toc.html

I can tell you these are hostgroups with 5 or 6 items in each group

this is running on UBUNTU server 12.04

each group has a dependency on a host server and several services

attached is nagios.cfg AND any other files I found that were relevant

Hope this helps

I may be wrong, but usually "CONFIG IS FALSE" in BPI is caused by too many iterations.

I noticed that you added bunch of hostgroups as members to themselves. For example:

define hostgroup {
hostgroup_name AmericanRailcar
alias AmericanRailcar
members NT37,nt4ftp,clientemail,RightFax,AmericanRailcar
}

or

define hostgroup {
hostgroup_name Anchor
alias Anchor
members Anchor,Citrix,NT32,NT37,nt4ftp,clientemail,RightFax
}

I would recommend removing these members out of the hostgroup definition.

actually I think the person who built this set host with same names as host groups

My bad - hostgroup members would be defined with "hostgroup_members", not "members"... We will have to try to recreate the issue in house.