Import Configuration failure ~ Can't recover.

[awatch]

I've been trying unsuccessfully to roll out a nagiosxi server to replace our current production nagios core server. The current nagios core is version 3.2.0, and has very many custom scripts and tweaks I've added to it since we first brought it up. The current core configuration works perfectly, however I simply cannot port it into nagiosxi. I've followed all of the documentation, run each file through the import script individually, tried many different methods of importing the results into the database... All to no avail. The import wizard is skipping hosts and, even worse, reading host names with negating prefixes as new hosts. ( !host ) I've even tried skipping the DB all together and trying the configuration from the static/ folder. This works occasionally, but with all the broken DB definitions it won't even start the monitoring service.

Some direction on this would be greatly appreciated as I've already spent hours scouring the documentation/these forums/google... Thanks in advance.

[mmestnik]

Try this: http://bit.ly/bsdHgy
There are some hints in here on how to deal with some of the problems you describe.

[awatch]

Thanks for the reply, unfortunately this document wasn't really of any help. It's just the standard latter bit of importing any sort of configuration. Short of having to manually edit the imported configuration in the database (At which point I may as well just rewrite the entire configuration from the ground up into the DB) there are no better ways to troubleshoot the conversion tool, or completely wipe the configuration database so I can verify there aren't some sort of lingering definition errors?

[mmestnik]

The document should have helped you recover from any configuration error that you would be unable to recover from otherwise.

[awatch]

I ended up recovering from the nonsense in the DB by restoring a backup from a much earlier date. What I was really hoping to find in the documentation was some sort of explanation as to why a working set of configuration files from Nagios Core would, after being passed through the import script, fail horribly upon import into the database. It's skipping over object definitions and adding objects which aren't defined, such as adding a host from a service reference based upon a negation title. Example:

Code: Select all

define host{
     host_name     !host1
       ....etc....
}

From a negation in a service definition such as:

Code: Select all

define service{
     service_description     someservice
     hostgroup_names        Hostgroup1
     host_names                !host1
}

Wherein the service is to run on all hosts in the hostgroup -except- host1. This anomaly is making it seem like I'll have to rewrite our entire production configuration from scratch to avoid these constructs so that nagiosxi can actually run. Is there anything I'm missing from the documentation as to how to accomplish this...?

[mmestnik]

To investigate this further I'm looking to the NagiosQL community for assistance. This may take a few days.

[awatch]

Thank you! Any assistance is appreciated.

[danielquinde]

I have been following the documents
- Importing config files.pdf
- Using the config import prep tool.pdf

I don’t receive any error, until I clic the option "check configuration files", I get this:

Error: Template 'Interurbanos' specified in host definition could not be not found (config file '/usr/local/nagios/etc/hosts/Ambato.cfg', starting on line 14)
Error processing object config files!

Hope you can help me to resolve this,

Thank you!

[mmestnik]

Thus far I've received no reply from the NagiosQL community. One thing I'd like to point out is that having every body(or even just 3 or 4 pp) from the NagiosXI community trying to get assistance from the NagiosQL community could unintentionally create disparity. So please unless you know some one personally or have a friendly chat conversation please avoid contacting them. Previously with other communities as soon as ppl mention NagiosXI they have been, somewhat rudely, shown the door.

We are going to expand the NagiosXI community to include liaisons for the adjoining projects so if you are working with or would like to work on any of these projects please let us know. The qualifications would include programming ability and the ability to understand and work on the project, hacking/reading code and fixing bugs(like the above).

Some big words in this one, /me pats self on back.

[danielquinde]

Hi MMESTNIK,

Let me if i can get what u mean.

The support of Nagios XI is defficient?
You are creating a community to resolve and help people?

I work out with my issue, and can resolved the weekend. So now i i am dealing with the migration in a controlled environment.
If i can contribuite a piece with this, i will be agree to do it.

Daniel