Auto-Discovery not assigning Check Command NULLERROR

[Lisa.sorenson]

I've ran your steps exactly, and it does same thing. I get configuration verification failed.

Nagios Core 4.0.7
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 06-03-2014
License: GPL

Website: http://www.nagios.org
Reading configuration data...
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/servername.cfg', starting on line 14)
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/definitions
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.

[Box293]

When going through the steps, do you ever get to a point where the Apply Configuration succeeds?

[Lisa.sorenson]

It succeeds after I remove all the services from the discovered servers. When I run configuration after doing this it succeeds. How do I add services back so I can monitor these servers, and have configuration run successfully?

Thanks,
Lisa

[tmcdonald]

So you still have the host and you want to re-add the services? I believe you can just re-run the Autodiscover wizard and it will re-create the services for you. I just tested this and it appears FTP, HTTP, HTTPS, SSH, and SMTP are not being given a check command either directly or via a template, so you will want to deactivate them for apply config to take effect. These were just five that I found - there may be more. Check all your Sync Missed services that were just added for any missing check commands that also do not have templates assigned. It would be helpful if we knew which of those are failing so we can fix the wizard.

I will talk to the devs about this.

[Lisa.sorenson]

Yes, when I re-add the service by running auto-discover we are back to where we were with the services causing config error.

[tmcdonald]

Did you see any services that had missing check commands or templates like I suggested in my last post? If so it would be very helpful to know which ones so we can fix the wizard properly.

[Lisa.sorenson]

Yes the NetBIOS, LDAP, and RDP services have missing commands.

[tmcdonald]

Since I was able to recreate this issue I have put in a bug report for this (ID 3423). I set the priority a bit higher than the default so this should be looked at fairly soon.

Does the issue present itself if you scan a smaller range? For that matter, how many are you scanning initially?

[Lisa.sorenson]

Hello,
I am still unable to run the Auto-Discovery Monitoring Wizard successfully for 11 objects in one of our IP ranges. I still get the following error and the configuration fails:

Nagios Core 4.0.8
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 08-12-2014
License: GPL

Website: http://www.nagios.org
Reading configuration data...
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.8.3.1.cfg', starting on line 32)
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/definitions
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.

The services that are check marked are: SSH, NetBIOS, RDP, HTTP, HTTPS, LDAP, TELNET, NRPE, IPP

We are on the lastest version of Nagios XI 2014R1.4

Let me know of anything else I can do so we can get our IP ranges monitoring without failing the configuration.

Thanks,
Lisa

[abrist]

Can you post one of the configs of these broken services? In the CCM, go to Services, search for one of the problematic ones, and then click the disk icon to the right. Post the text output.