Page 1 of 2
Nagios Core to XI port
Posted: Mon May 02, 2011 4:11 pm
by ntextoll
I've been using Nagios Core for a couple months on a proof or concept and after purchase attempted to port the Core configs into Nagios XI via the Config Import tool. My configs are visable for tactical overview and through the Nagios Core Config Manager with all Host/Sevices/Hostgroups in the right place... The only thing that shows in NagiosXI host is the localhosts.
I checked the permissions and it finds no fault. Your assistance will be much appreciated.
Re: Nagios Core to XI port
Posted: Mon May 02, 2011 4:30 pm
by ntextoll
To add to this I've tried the import twice now on two different Centos 5.5/6 machines to no avail. Whatever I'm doing wrong is at least consistent.
Re: Nagios Core to XI port
Posted: Mon May 02, 2011 4:39 pm
by rdedon
Hello,
could you verify the following method is the one you implemented:
http://assets.nagios.com/downloads/nagi ... p_Tool.pdf?
Thank you.
Re: Nagios Core to XI port
Posted: Mon May 02, 2011 4:54 pm
by ntextoll
On the second attempt "yes". Ill give it another shot tonight.
Re: Nagios Core to XI port
Posted: Tue May 03, 2011 9:18 am
by rdedon
ntextoll wrote:On the second attempt "yes". Ill give it another shot tonight.
Sounds good, just report back here if there are any difficulties and we would be glad to assist you.
Re: Nagios Core to XI port
Posted: Sun May 08, 2011 6:41 pm
by ntextoll
Give me command line or give me death... Well, at least an option.
I've finally been able to import my configs. Here's the problem:
All host show with only a single ping service. All services are service groups are also there. It appears that nothing has connections anymore. Can someone verify that this should be appear this way after a import like the log alludes to?
FTR...
I'm only importing 760 host and 3800 service checks.
Re: Nagios Core to XI port
Posted: Mon May 09, 2011 10:08 am
by mguthrie
Admittedly, the import process does work, but depending on the circumstances things can get messy very quickly if things go wrong. Can I get some more details on the actual configs you're importing?
Here are some notes on importing configs that I've notice from previous support issues:
- any lists that have comma-separated values with spaces in-between them can throw off the relationships upon import. We try to catch these in our prep script, but the script has missed some in the past. Example:
Code: Select all
hostgroups group1,group2,group3,group4 ###this is good
hostgroups group1, group2, group3, group4
###this won't import correctly, it will create what appear to be empty or duplicate configs in the Core Config Manager.
- ideally you'll want to have all hostgroups in their own file, servicegroups in their own file, etc. I came across a user who literally had all of their configs in one file, and as you might guess the import didn't go well.
Are you able to "Apply Configuration" without error after the import?
Are you seeing duplicate objects in the CCM after all objects are imported?
Are you seeing "sync missed" after applying configuration?
Import issues can be tricky, so the more detail you give, the quicker we'll be able to diagnose the issue.
Re: Nagios Core to XI port
Posted: Tue May 10, 2011 8:43 am
by ntextoll
mguthrie wrote:Admittedly, the import process does work, but depending on the circumstances things can get messy very quickly if things go wrong. Can I get some more details on the actual configs you're importing?
Here are some notes on importing configs that I've notice from previous support issues:
- any lists that have comma-separated values with spaces in-between them can throw off the relationships upon import. We try to catch these in our prep script, but the script has missed some in the past. Example:
Code: Select all
hostgroups group1,group2,group3,group4 ###this is good
hostgroups group1, group2, group3, group4
###this won't import correctly, it will create what appear to be empty or duplicate configs in the Core Config Manager.
- ideally you'll want to have all hostgroups in their own file, servicegroups in their own file, etc. I came across a user who literally had all of their configs in one file, and as you might guess the import didn't go well.
Are you able to "Apply Configuration" without error after the import?
Are you seeing duplicate objects in the CCM after all objects are imported?
Are you seeing "sync missed" after applying configuration?
Import issues can be tricky, so the more detail you give, the quicker we'll be able to diagnose the issue.
I finally have a couple hours to get somewhere on this one:
Attached is my hostgroup and service groups.
Couple questions:
Do you think that some of the issues are due to my host having spaces in the names?
All my services have the same config name under CCM of _multiple_hosts. Could that be the problem?
Does the issue of Nagios stalling on "Writing monitoring data" have any correlation with the problem?
Is the actions of "writing monitoring data", then "checking configuration files" through the tools menu the same as what was done in the open source version?
All my serices
I'm at the point where I'm thinking about abandoning my services and starting over. The completion of the first phase of the deployment is due by COB Friday.
Your response would be much appreciated.
Re: Nagios Core to XI port
Posted: Tue May 10, 2011 11:26 am
by mguthrie
Do you think that some of the issues are due to my host having spaces in the names?
Nope, that should be fine.
All my services have the same config name under CCM of _multiple_hosts. Could that be the problem?
This is part of what the prep script does to make sure the services import correctly, so it
shouldn't be the cause.
Does the issue of Nagios stalling on "Writing monitoring data" have any correlation with the problem?
YES The Config Write is either timing out or hitting it's memory limit. Open the /etc/php.ini file, page down all the way to the bottom and remove the following line:
Code: Select all
; Up the memory limit
memory_limit = 64M
Scroll up to around line 300 and edit the following lines to match below:
Code: Select all
;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;
max_execution_time = 60 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
memory_limit = 256M ; Maximum amount of memory a script may consume
Save and close, then restart apache.
If the script keeps stalling out and not working, increase the limits so that the Write process can complete.
Is the actions of "writing monitoring data", then "checking configuration files" through the tools menu the same as what was done in the open source version?
Yes, I believe so.
I'm at the point where I'm thinking about abandoning my services and starting over. The completion of the first phase of the deployment is due by COB Friday.
Hopefully the solution above will get you up and running by Friday, we'll do our best to get you there
Re: Nagios Core to XI port
Posted: Tue May 10, 2011 3:25 pm
by ntextoll
YES The Config Write is either timing out or hitting it's memory limit. Open the /etc/php.ini file, page down all the way to the bottom and remove the following line:
Code: Select all
; Up the memory limit
memory_limit = 64M
Scroll up to around line 300 and edit the following lines to match below:
Code: Select all
;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;
max_execution_time = 60 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
memory_limit = 256M ; Maximum amount of memory a script may consume
Save and close, then restart apache.
Code: Select all
service httpd restart
If the script keeps stalling out and not working, increase the limits so that the Write process can complete.
No luck. I followed both and it still doesn't complete. It goes blank and that's pretty much it.
My resource limits are at the following:
;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;
max_execution_time = 360 ; Maximum execution time of each script, in seconds
max_input_time = 360 ; Maximum amount of time each script may spend parsing request data
memory_limit = 2056M ; Maximum amount of memory a script may consume
I'm at a lost...