Nconf Error: Deployment not possible due to errors in config

[rohithroki]

Dear TEam,
I am getting below error while generating nagios config in Nconf.

Please find the below log
Processing object config file '/usr/local/nagios/share/nconf/temp/global/timeperiods.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/global/contacts.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/global/misccommands.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/global/checkcommands.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/global/host_templates.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/global/service_templates.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/global/contactgroups.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/Default_collector/service_dependencies.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/Default_collector/host_dependencies.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/Default_collector/advanced_services.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/Default_collector/services.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/Default_collector/servicegroups.cfg'...
Processing object config file '/usr/local/nagios/share/nconf/temp/Default_collector/hosts.cfg'...
Error: Invalid notification option 'durs' in host definition.
Error: Could not add object property in file '/usr/local/nagios/share/nconf/temp/Default_collector/hosts.cfg' on line 3109.
Error processing object config files!


***> The name of the main configuration file looks suspicious...

Make sure you are specifying the name of the MAIN configuration file on
the command line and not the name of another configuration file. The
main configuration file is typically '/usr/local/nagios/etc/nagios.cfg'

***> 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.

Note : My default collector directory is empty /usr/local/nagios/share/nconf/temp/Default_collector/

[nozlaf]

inb4 these aren't the nconf support forums...

i love nconf

Code: Select all

Error: Invalid notification option 'durs' in host definition.

it should be d,u,r,s (assuming you want these states for notification) as it needs commas

[rohithroki]

Yes it is in commas.

Please let me know how to fix the error.

I am unable to add any servers to nagios due to this error

[nozlaf]

Yes it is in commas.

your original post clearly shows that it is not in commas and that it is the error causing your config to break

[rohithroki]

kindly let me know in which config file i need to check the same.
As i don't have any files in directory /usr/local/nagios/share/nconf/temp/Default_collector/

[nozlaf]

kindly let me know in which config file i need to check the same.
As i don't have any files in directory /usr/local/nagios/share/nconf/temp/Default_collector/

the issue is within nconf
you need to review what you have entered and remove the entry that you put in there that has the DURS

Processing object config file '/usr/local/nagios/share/nconf/temp/Default_collector/hosts.cfg'...
Error: Invalid notification option 'durs' in host definition.

this line that you pasted earlier shows that the config file that nconf created is wrong
it is located in the path shown

but the issue needs to be fixed within nconf, so read that cfg file, find the durs entry and then fix it in nconf

[rkennedy]

Thanks @nozlaf!

As mentioned, we did not write nconf so we are unable to provide support for it. Your best bet is going to be read what @nozlaf mentioned, or look for support on their forums.

[rohithroki]

Hi All

Was able to fix the isseu as one of the server was wrongly configured with wrong notification option

[rkennedy]

Great to hear!

Going to mark this as resolved, and close it out. Feel free to make a new thread if you have any questions in the future.