On 02.07.2012 19:18, Marc Becker wrote: > Hi, > > it's definitly possible to separate database, icinga and icinga-web each > to different hosts. > > At first your installing icinga and ido-utils on your monitoring server. > Icinga itself doesn't need access to the database. It connects to the > idoutils (socket or tcp). Idoutils are the "bridge" between database and > icinga. idoutils needs therefore access to the database. If all is > configured well you should find some lines like the following in your logs: > --- > [1340265156] idomod: IDOMOD 1.7.0 (05-15-2012) Copyright(c) 2005-2008 > Ethan Galstad, Copyright(c) 2009-2012 Icinga Development Team > (https://www.icinga.org) > [1340265156] idomod: Successfully connected to data sink. 0 queued > items to flush. > [1340265156] Event broker module 'IDOMOD' version '1.7.0' from > '/usr/local/icinga/lib/idomod.so' initialized successfully. > ---
- if idomod and ido2db run on the icinga host using a unix socket, you'll pass the remote db host to ido2db.cfg - if using tcp socket betweet idomod (icinga host) and ido2db (db host), you'll need to configure the socket address correctly, while the db information is done locally on the remote host on ido2db.cfg for the easyness of debugging stuff while developing it, i prefer keeping option 1 with a remote oracle rdbms e.g. for the productive systems i do recommend using tcp with ssl enabled though, also offloading the ido2db load from the icinga host, and putting that remote (one of those performance tuning tips) > > > After that you configure icinga-web to connect to: > - database server with it's own table (for example icinga_web): > - database server with the icinga/ido table for getting the status > > These config sections you find in > PREFIX/icinga-web/etc/conf.d/databases.xml. At least to send commands to > your icinga installation you have to configure ssh access for a user > from webhost to monitoring host. There the user has to be able to write > to command file (have a look at PREFIX/icinga-web/etc/conf.d/access.xml). ssh access should be configured for a user accessing the icinga.cmd pipe only. regarding the versions being run - i would recommend upgrading icinga core/ido to 1.7.x as well as use icinga web 1.7.x - those 'major' versions are tested together, others should work, but as you might know, younger versions normally resolve more bugs you have been reporting the the dev tracker ;-) well, and if the docs are not clear to you, you should probably throw a ticket with a yet better docs input onto https://dev.icinga.org in the docs section after figuring out how it's done. wolfgang will be happy to apply your suggestions then :) kind regards, michael > > > Regards, > > Marc > > Am 02.07.2012 17:19, schrieb Russell Poyner: >> I've been trying, and failing to install icinga-web on a a separate host >> from my icinga-core. >> >> Is this even possible? >> Anyone done it? >> >> What works: >> monitor.domain.edu is a vm running icinga-core 1.6.2 with idoutils, and >> the cgi interface successfully >> >> mysql.domain.edu is the mysql server for icinga-core, and a bunch of >> other apps here. >> >> What is desired: >> icinga-web running in an apache vhost on webhost.domain.edu >> >> Initially I tried installing icinga-web 1.7 on the webhost, but maybe I >> need to be using 1.6.2 to match my core install? >> >> It's not clear to me from the icinga-web install guide what all the >> communication channels between icinga-web and icinga-core are. >> >> The icinga-web install can talk to the ido database on the mysql server, >> and to it's own database. Are there other channels that need to be >> configured? >> >> icinga_pipe? >> icinga-api? >> >> RP >> >> ------------------------------------------------------------------------------ >> 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 > > > > ------------------------------------------------------------------------------ > 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 -- DI (FH) Michael Friedrich Vienna University Computer Center Universitaetsstrasse 7 A-1010 Vienna, Austria email: michael.friedr...@univie.ac.at phone: +43 1 4277 14359 mobile: +43 664 60277 14359 fax: +43 1 4277 14338 web: http://www.univie.ac.at/zid http://www.aco.net Lead Icinga Core Developer http://www.icinga.org ------------------------------------------------------------------------------ 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
