Relationships Verified During The Pre-Flight Check:
During the "pre-flight check", Nagios verifies that you have
defined the data relationships necessary for monitoring.
Objects are all related and need to be setup properly in
order for things to run.
This is a list of the basic things that Nagios attempts to
check before it will start monitoring...
Verify that all contacts are a member of at least one
contact group.
Verify that all contacts specified in each contact group
are valid.
Verify that all hosts are a member of at least one host
group.
Verify that all hosts specified in each host group are
valid.
Verify that all hosts have at least one service
associated with them.
Verify that all commands used in service and host checks
are valid.
Verify that all commands used in service and host event
handlers are valid.
Verify that all commands used in contact service and host
notifications are valid.
Verify that all notification time periods specified for
services, hosts, and contact are valid.
Verify that all service check time periods specified for
services are valid.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hosts without services:
select host_name from nagios_hosts where register=1 and host_name not in (select host_name from nagios_services where register=1);
hosts without hostextinfo:
select host_name from nagios_hosts where register=1 and host_name not in (select host_name from nagios_hostextinfo where register=1);
Unused check_commands:
select command_name from nagios_commands where
command_name not in (select distinct check_command from nagios_hosts) and
command_name not in (select distinct check_command from nagios_services);
Unused misccommands
select command_name from nagios_misccommands where
command_name not in (select distinct host_notification_commands from nagios_contacts) and
command_name not in (select distinct service_notification_commands from nagios_contacts) and
command_name not in (select distinct service_notification_commands from nagios_contacts) and
command_name not in (select distinct event_handler from nagios_hosts);
Unused remote_config templates
select remote_host_name from nagios_remoteconfigs
where register=0 and remote_host_name not in (select distinct remote_config_template from nagios_remoteconfigs where register=1);
Unused timeperiods
select timeperiod_name from nagios_timeperiods where
timeperiod_name not in (select distinct host_notification_period from nagios_contacts) and
timeperiod_name not in (select distinct service_notification_period from nagios_contacts) and
timeperiod_name not in (select distinct escalation_period from nagios_hostescalations) and
timeperiod_name not in (select distinct check_period from nagios_hosts) and
timeperiod_name not in (select distinct notification_period from nagios_hosts) and
timeperiod_name not in (select distinct escalation_period from nagios_serviceescalations) and
timeperiod_name not in (select distinct check_period from nagios_services) and
timeperiod_name not in (select distinct notification_period from nagios_services);
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=423476
Relationships Verified During The Pre-Flight Check:
During the "pre-flight check", Nagios verifies that you have
defined the data relationships necessary for monitoring.
Objects are all related and need to be setup properly in
order for things to run.
This is a list of the basic things that Nagios attempts to
check before it will start monitoring...
contact group.
are valid.
group.
valid.
associated with them.
are valid.
handlers are valid.
notifications are valid.
services, hosts, and contact are valid.
services are valid.
Logged In: YES
user_id=423476
Originator: YES
hosts without services:
select host_name from nagios_hosts where register=1 and host_name not in (select host_name from nagios_services where register=1);
hosts without hostextinfo:
select host_name from nagios_hosts where register=1 and host_name not in (select host_name from nagios_hostextinfo where register=1);
Unused check_commands:
select command_name from nagios_commands where
command_name not in (select distinct check_command from nagios_hosts) and
command_name not in (select distinct check_command from nagios_services);
Unused misccommands
select command_name from nagios_misccommands where
command_name not in (select distinct host_notification_commands from nagios_contacts) and
command_name not in (select distinct service_notification_commands from nagios_contacts) and
command_name not in (select distinct service_notification_commands from nagios_contacts) and
command_name not in (select distinct event_handler from nagios_hosts);
Unused remote_config templates
select remote_host_name from nagios_remoteconfigs
where register=0 and remote_host_name not in (select distinct remote_config_template from nagios_remoteconfigs where register=1);
Unused timeperiods
select timeperiod_name from nagios_timeperiods where
timeperiod_name not in (select distinct host_notification_period from nagios_contacts) and
timeperiod_name not in (select distinct service_notification_period from nagios_contacts) and
timeperiod_name not in (select distinct escalation_period from nagios_hostescalations) and
timeperiod_name not in (select distinct check_period from nagios_hosts) and
timeperiod_name not in (select distinct notification_period from nagios_hosts) and
timeperiod_name not in (select distinct escalation_period from nagios_serviceescalations) and
timeperiod_name not in (select distinct check_period from nagios_services) and
timeperiod_name not in (select distinct notification_period from nagios_services);