Auto discovery does not set the check commands

[cloudcom]

Hi
I have a problem with auto discovery process.
Auto discovery wizard find the new device but can not set check commands to the device's services.
when I 'finish' (pressing finish button) the auto discovery job, configuration verification fails.

output of "/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg" command is:

Read main config file okay...
Error: Service description, host name, or check command is NULL
Error: Could not register service (config file '/usr/local/nagios/etc/services/10.10.96.1.cfg', starting on line 14)
Error processing object config files!

When I check the line 14 for that .cfg file, I do not see check commands.
On web interface, The services (ping and https) seem on the CCM but check command fields are blank.

Platform is:
Centos 6.5 64bit version
Manual installation of NagiosXI
Nagios Core 4.0.5
Nagios XI 2014R1.0

[scottwilkerson]

This is weird, but I believe I have found a bug.

can you install the following wizard in Admin -> Manage Wizards then run the auto discovery wizard again.

autodiscovery.zip

[cloudcom]

Hi scottwilkerson,

I have installed the wizard that you attached but it could not fix the problem.
Here is the autodiscovered host's service file 10.10.96.1.cfg :

###############################################################################
#
# Service configuration file
#
# Created by: Nagios QL Version 3.0.3
# Date: 2014-05-28 10:11:35
# Version: Nagios 3.x config file
#
# --- DO NOT EDIT THIS FILE BY HAND ---
# Nagios QL will overwite all manual settings during the next update
#
###############################################################################

define service {
host_name 10.10.96.1
service_description HTTPS
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contacts nagiosadmin
_xiwizard autodiscovery
register 1
}

define service {
host_name 10.10.96.1
service_description Ping
use xiwizard_genericnetdevice_ping_service
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contacts nagiosadmin
_xiwizard autodiscovery
register 1
}

###############################################################################
#
# Service configuration file
#
# END OF FILE
#
###############################################################################

The topic http://support.nagios.com/forum/viewtop ... =6&t=27260 is the same with my problem.

[scottwilkerson]

The ping service looks correct

Code: Select all

use xiwizard_genericnetdevice_ping_service

Would inherit the check_command from the template, the HTTPS service does not though, did you select both when you re-ran the wizard, or could this be left-over from before?

[cloudcom]

Hi scottwilkerson,

Yes, I selected both of them. This could not be left-over before because that was the first time that I configured the host 10.10.96.1

Here is a new try and result:

auto discovery problem.docx

admin > manage components >Auto-Discovery
Provides device and service auto-discovery.
Version: 2.04 Author: Nagios Enterprises, LLC

admin > manage config wizards > Auto-Discovery
Monitor devices and services found by auto-discovery jobs.
Version: 1.3.2

[slansing]

There should be a new wizard available now, please navigate to Admin > Manage Wizards > Check for Updates, then update to the most recent version, let us know what the outcome is, thanks!

[cloudcom]

Hi slansing,

This is the last version of the auto discovery wizard.
I run "check for update" and it showed "uptodate".

I can not set all devices' commands by hand. I must fix the problem.
Can re-installing the Nagios-XI be a solution?

[cloudcom]

And I realized that nagios is not running as a service.

# service nagios status
nagios is not running
# service nagios start
Starting nagios: done.
# service nagios status
nagios is not running

Altough it says starting done, its status still shows not running.

here is the log file when i try to start nagios:

[1401566880] Nagios 4.0.5 starting... (PID=32587)
[1401566880] Local time is Sat May 31 23:08:00 EEST 2014
[1401566880] LOG VERSION: 2.0
[1401566880] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[1401566880] qh: core query handler registered
[1401566880] nerd: Channel hostchecks registered successfully
[1401566880] nerd: Channel servicechecks registered successfully
[1401566880] nerd: Channel opathchecks registered successfully
[1401566880] nerd: Fully initialized and ready to rock!
[1401566880] wproc: Successfully registered manager as @wproc with query handler
[1401566880] wproc: Registry request: name=Core Worker 32589;pid=32589
[1401566880] wproc: Registry request: name=Core Worker 32590;pid=32590
[1401566880] wproc: Registry request: name=Core Worker 32594;pid=32594
[1401566880] wproc: Registry request: name=Core Worker 32595;pid=32595
[1401566880] wproc: Registry request: name=Core Worker 32593;pid=32593
[1401566880] wproc: Registry request: name=Core Worker 32591;pid=32591
[1401566880] Error: Could not load module '/usr/local/lib/mk-livestatus/livestatus.o' -> /usr/local/lib/mk-livestatus/livestatus.o: undefined symbol: last_command_check
[1401566880] Error: Failed to load module '/usr/local/lib/mk-livestatus/livestatus.o'.
[1401566880] ndomod: NDOMOD 2.0.0 (02-28-2014) Copyright (c) 2009 Nagios Core Development Team and Community Contributors
[1401566880] ndomod: Successfully connected to data sink. 0 queued items to flush.
[1401566880] ndomod registered for process data
[1401566880] ndomod registered for log data'
[1401566880] ndomod registered for system command data'
[1401566880] ndomod registered for event handler data'
[1401566880] ndomod registered for notification data'
[1401566880] ndomod registered for comment data'
[1401566880] ndomod registered for downtime data'
[1401566880] ndomod registered for flapping data'
[1401566880] ndomod registered for program status data'
[1401566880] ndomod registered for host status data'
[1401566880] ndomod registered for service status data'
[1401566880] ndomod registered for adaptive program data'
[1401566880] ndomod registered for adaptive host data'
[1401566880] ndomod registered for adaptive service data'
[1401566880] ndomod registered for external command data'
[1401566880] ndomod registered for aggregated status data'
[1401566880] ndomod registered for retention data'
[1401566880] ndomod registered for contact data'
[1401566880] ndomod registered for contact notification data'
[1401566880] ndomod registered for acknowledgement data'
[1401566880] ndomod registered for state change data'
[1401566880] ndomod registered for contact status data'
[1401566880] ndomod registered for adaptive contact data'
[1401566880] Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.
[1401566880] Error: Module loading failed. Aborting.

[lmiltchev]

[1401566880] Error: Failed to load module '/usr/local/lib/mk-livestatus/livestatus.o'.

Comment out the entries, pertaining to mk-livestatus in the nagios.cfg file, save, exit, and restart nagios. Let me know if this helped.

You will have to uninstall mk-livestatus and install a version that is compatible with Core 4 (if you want to use it).

[cloudcom]

Thanks lmiltchev,
I have already solved the problem about mk-livestatus
Yes, removing the lines related to mk-livestaus works.

But auto discovery problem persists. The wizard is not be able to set check commands for all detected services. So, configuration verification fails.
After detecting new devices, the wizard gives options for detected services like all, comman and none. That is ok.
if I select "none", configuration verification is OK since the ping service is set correctly.
But some services shuch as http,ftp,https are not set correctly.

Were you aware of this problem before Or did you just hear this issuse recently?