Hi Sven --
Thanks for your reply. Prior to your e-mail I went through the motions of
modifying the Local section of the deployment.ini file. Here is the syntax that
was used:
;; LOCAL deployment ;;
;[extract config]
;type = local
;source_file = "/var/www/nconf/output/NagiosConfig.tgz"
;target_file = "/usr/local/icinga/etc/Default_collector/"
;action = extract
;[copy collector config]
;type = local
;source_file = "/tmp/Default_collector/"
;target_file = "/usr/local/icinga/etc/Default_collector/"
;action = copy
;[copy global config]
;type = local
;source_file = "/tmp/global/"
;target_file = "/usr/local/icinga/etc/global/"
;action = copy
;[copy nagios.cfg]
;type = local
;source_file = "/var/www/nconf/static_cfg/icinga.cfg"
;target_file = "/usr/local/icinga/etc/icinga.cfg"
;action = copy
;reload_command = "sudo /etc/rc.d/init.d/icinga reload
When I tried running the Generate Nagios config utility within the console, the
following error message appeared on-screen:
Icinga 1.7.0
Copyright (c) 2009-2012 Icinga Development Team
(http://www.icinga.org<http://www.icinga.org/>)
Copyright (c) 2009-2012 Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 05-15-2012
License: GPL
Reading configuration data...
Error: Cannot open main configuration file
'/var/www/nconf/temp/test/Default_collector.cfg' for reading!
Error processing main config file!
***> 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/icinga/etc/icinga.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 definitions. If you are upgrading from a previous
version of Icinga, 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.
I am not sure where my syntax is wrong, so if you, or someone, can point that
out, I would appreciate it. Also, you mentioned adding several lines
of bash code to the /etc/init.d/icinga script. That sounds like a great idea,
and I wondering if you could provide the syntax of the code?
Thanks.
________________________________
From: Bauknecht, Sven [mailto:sven.baukne...@its-technidata.de]
Sent: Wednesday, May 23, 2012 3:35 PM
To: icinga-users@lists.sourceforge.net
Subject: Re: [icinga-users] Configuration of NConf 1.3 for Icinga 1.7
Hello Andrew,
I am using Icinga with NConf for quite a while now. The NConf 1.2 and 1.3
Version work nicely with Icinga (I use this combination since icinga-1.0). If
your "old" Nagios is completely configured with NConf 1.2.x you should can
import the nconf generated configuration in your NConf-1.3. Or maybe you simply
can use the 1.2.x NConf database with the new one.
Since you intend to run nconf and icinga on the same machine you don't need to
worry about config deployment that much. I have some lines of bash code added
to my /etc/init.d/icinga script that unpacks nconf's tgz to a configuration
folder read by icinga on every reload or restart.
Hope I could help a little
Cheers
Sven
Von: Kaplan, Andrew H. [mailto:ahkap...@partners.org]
Gesendet: Mittwoch, 23. Mai 2012 16:02
An: 'icinga-users@lists.sourceforge.net'
Betreff: [icinga-users] Configuration of NConf 1.3 for Icinga 1.7
Hello --
I have completed the installation of the Icinga and Icinga-web 1.7, and NConf
1.3.0 applications. The server is designated to replace
an existing Nagios 3.3.1 system, and to that end one of the goals here is to
successfully migrate the configuration files and databases
from the old to the new system. The NConf installation on the Nagios server is
running the 1.2.6 release. A dump of the database on that
server was completed, and the sql file from that server was successfully
imported into that on the new server.
I have gone to the webpage that describes how to import and modify the
appropriate nagios configuration files into the Icinga installation.
The NConf database is an added dimension to this process, and I thought I had
better talk to the group about it.
The icinga and icing-web folders are located in the /usr/local directory. The
next step here is to configure NConf 1.3.0 to work with the
Icinga installation. Part of the process is reconfiguring the deployment.ini
file of NConf to enable the application to generate the correct
configuration files. I have included a copy of the file with this posting.
Since NConf is on the same computer as Icinga, I am concerned
about the Local Deployment section.
When generating the configuration files, NConf creates a tgz file which, when
extracted in the appropriate directory, creates three folders
called Default_Collector, global, and static_cfg.
The Default_Collector folder contains the files:
extended_host_info.cfg
extended_service_info.cfg
hostgroups.cfg
hosts.cfg
servicegroups.cfg
services.cfg
The global folder contains the following:
checkcommands.cfg
contactgroups.cfg
contacts.cfg
host_templates.cfg
misccommands.cfg
service_templates.cfg
timeperiods.cfg
The static_cfg folder does not contain any files.
I want to be able to deploy the existing configuration files along with NConf
on the Icinga server. Does anyone have experience in configuring
NConf to work with Icinga?
The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
