NagiosQL 3.2<\/p>\n
NagiosQL 3.2 ? Installation Page 2
\nTable of contents
\n1 Installation ………………………………………………………………………………………………………………………………. 3
\n1.1 Prerequisites …………………………………………………………………………………………………………………….. 3
\n1.2 Prepare directory structure …………………………………………………………………………………………………. 3
\n1.3 Nagios configuration files ……………………………………………………………………………………………………. 4
\n1.4 Prepare Apache configuration……………………………………………………………………………………………… 5
\n1.5 Install PHP modules (SSH) …………………………………………………………………………………………………… 6
\n1.6 Install NagiosQL ………………………………………………………………………………………………………………… 6
\n1.7 NagiosQL installer (new installation) …………………………………………………………………………………….. 7
\n1.8 Update NagiosQL ……………………………………………………………………………………………………………… 12
\n2 Configure NagiosQL ………………………………………………………………………………………………………………… 15
\n2.1 Base configuration ……………………………………………………………………………………………………………. 15
\n2.2 Domain config (paths) ………………………………………………………………………………………………………. 16
\n2.2.1 Data domains ……………………………………………………………………………………………………………. 16
\n2.2.2 Configuration domain ………………………………………………………………………………………………… 18
\n2.3 2.3 Setup remote access (FTP or SSH\/SFTP) …………………………………………………………………………. 20
\n2.3.1 Remote access via FTP ……………………………………………………………………………………………….. 20
\n2.3.2 Remote access via SSH\/SFTP ………………………………………………………………………………………. 20
\n3 Nagios Configuration ………………………………………………………………………………………………………………. 22
\n3.1 Nagios Configuration file …………………………………………………………………………………………………… 22
\n3.2 Additional permissions ……………………………………………………………………………………………………… 22
\n3.2.1 Check command ……………………………………………………………………………………………………….. 22
\n3.2.2 Configuration editor ………………………………………………………………………………………………….. 23
\n3.2.3 Restart command ……………………………………………………………………………………………………… 23
\n3.3 Support page ………………………………………………………………………………………………………………….. 23
\n3.3.1 Common checks ……………………………………………………………………………………………………….. 23
\n3.3.2 Config checks ……………………………………………………………………………………………………………. 24
\nNagiosQL 3.2 ? Installation Page 3
\n1 Installation
\n1.1 Prerequisites
\nNagiosQL is a web application and requires a running web server including PHP support and a database
\nserver.
\n? Apache web server
\n? MySQL Server version 4.1 or above
\n? PHP version 5.2 or above
\n? Nagios 2.x or 3.x
\n? additional PHP modules:
\n? session
\n? MySQL (php5?mysql)
\n? gettext
\n? filter
\n? ftp (optional \u2013 for FTP connections to remote servers)
\n? SSH (PECL module \u2013 optional \u2013 for SSH\/SCP connections to remote servers)
\n1.2 Prepare directory structure
\nNagiosQL stores the Nagios configuration files in a separate directory structure. This should preferably be
\ncreated by a super user (root). Where the files are stored is left to the administrator, in this guide we will
\nuse the folder \/etc\/nagiosql. Please note that this directory structure has to be added to the Nagios
\nconfiguration file nagios.cfg later on so Nagios can find its own configuration files.
\nThis directory structure has to be created on the server running Nagios.
\n# mkdir \/etc\/nagiosql
\n# mkdir \/etc\/nagiosql\/hosts
\n# mkdir \/etc\/nagiosql\/services
\n# mkdir \/etc\/nagiosql\/backup
\n# mkdir \/etc\/nagiosql\/backup\/hosts
\n# mkdir \/etc\/nagiosql\/backup\/services
\nThis way NagiosQL will store all configuration files below \/etc\/nagiosql. Host configurations will be stored
\nin \/etc\/nagiosql\/hosts, service configurations in \/etc\/nagiosql\/services. The backup structure will hold the
\nprevious version of a configuration file.
\nNagiosQL will run as a web application so you have to make sure that the web server daemon has write
\npermissions on these folders if this is a local installation. Furthermore the Nagios daemon must have read
\npermissions. If the users of both daemons are unknown you can use the following commands:
\n# ps -ef | grep http
\nroot 2999 1 0 Jul04 ? 00:00:10 \/usr\/sbin\/httpd2-prefork -f \/etc\/apache2\/httpd.conf
\nwwwrun 3123 2999 0 Jul04 ? 00:00:00 \/usr\/sbin\/httpd2-prefork -f \/etc\/apache2\/httpd.conf
\nThe user running the web server daemon is wwwrun.
\n# ps -ef | grep nagios
\nnagios 2902 1 0 Jun22 ? 00:05:39 \/usr\/sbin\/nagios -d \/etc\/nagios\/nagios.cfg
\nThe user running the Nagios daemon is nagios but in this case we need the group.
\n# id nagios
\nuid=111(nagios) gid=111(nagios) groups=111(nagios)
\nThe group of the user running the Nagios daemon is called nagios as well.
\nNagiosQL 3.2 ? Installation Page 4
\nNow we can set the permissions of the structure as follows:
\n# chown \u2013R wwwrun.nagios \/etc\/nagiosql
\nAlternatively the permissions can be set to 750 (directories), and 640 (cfg files), respectively.
\nUsing remote Nagios installations being administered by NagiosQL via FTP or SSH\/SCP this directory
\nstructure has to be created on the remote system. Then instead of the web server daemon user you have
\nto set write permissions on the directories for the user accessing via FTP or SSH\/SCP.
\n1.3 Nagios configuration files
\nNagiosQL needs read\/write permissions on some Nagios configuration files as well. The following files are
\naffected:
\nNagios main configuration file: nagios.cfg (write permissions)
\nNagios CGI configuration file: cgi.cfg (write permissions)
\nNagios process file: nagios.pid or nagios.lock (read permissions)
\nNagios command pipe: nagios.cmd (write permissions)
\nThe location of these files can be determined using the \u201efind\u201c command:
\n# find \/ -name nagios.cfg
\n\/etc\/nagios\/nagios.cfg
\n# find \/ -name cgi.cfg
\n\/etc\/nagios\/cgi.cfg
\n# find \/ -name nagios.pid
\n\/var\/run\/nagios.pid
\n# find \/ -name cgi.cfg
\n\/var\/spool\/nagios\/nagios.cmd
\nPlease note that the web server daemon and the Nagios daemon have to get the necessary permissions.
\nThis can be accomplished in several ways via user\/group permissions. Following an example for a local
\ninstallation:
\n# chown \u2013R wwwrun.nagios \/etc\/nagios\/nagios.cfg
\n# chown \u2013R wwwrun.nagios \/etc\/nagios\/cgi.cfg
\n# chown \u2013R wwwrun.nagios \/var\/spool\/nagios\/nagios.cmd
\n# chmod 640 \/etc\/nagios\/nagios.cfg
\n# chmod 640 \/etc\/nagios\/cgi.cfg
\n# chmod 660 \/var\/spool\/nagios\/nagios.cmd
\nRead permissions on the process file are normally achieved via standard permissions 644 but in this case
\nthe path should be remembered. All other paths should be jotted down as well so you can fill them in into
\nthe NagiosQL configuration domain.
\nNagiosQL 3.2 ? Installation Page 5
\n1.4 Prepare Apache configuration
\nNow a web server directory has to be created where the NagiosQL web application can be installed later
\non. This guide will use \/opt\/nagiosql.
\n# mkdir \/opt\/nagiosql
\n# chown wwwrun \/opt\/nagiosql
\nThe setting of two options in php.ini of the Apache web server should be verified (using openSuSE\/SLES the
\nlocation is \/etc\/php5\/apache\/php.ini, Fedora, CentOS \/etc\/php.ini, Debian \/etc\/php5\/apache2\/php.ini):
\nfile_uploads = On
\nsession.auto_start = 0
\ndate.timezone = “Europe\/Zurich” (bzw. “Europe\/Berlin” oder “Europe\/London” etc.)
\nPlease create a configuration file for the web server. The location differs between distributions. Using
\nopenSuSE\/SLES\/Debian the location is \/etc\/apache2\/conf.d, Fedora, CentOS \/etc\/httpd\/conf.d.
\n# touch \/etc\/apache2\/conf.d\/nagiosql.conf
\nThe file can be modified using your favourite editor (e.g. vi) and should have the following contents:
\n# NAGIOSQL SAMPLE CONFIG SNIPPETS FOR APACHE WEB SERVER
\n# Last Modified: 03-24-2011
\n#
\n# This file contains examples of entries that need
\n# to be incorporated into your Apache web server
\n# configuration file. Customize the paths, etc. as
\n# needed to fit your system.
\nAlias \/nagiosql “\/opt\/nagiosql”
\n<Directory “\/opt\/nagiosql”>
\nOptions None
\nAllowOverride None
\nOrder allow,deny
\nAllow from all
\n# Order deny,allow
\n# Deny from all
\n# Allow from 127.0.0.1
\n# AuthName “NagiosQL Access”
\n# AuthType Basic
\n# AuthUserFile \/etc\/nagiosql\/auth\/nagiosql.users
\n# Require valid-user
\n<\/Directory>
\nIf you want to use basic Apache authentication the lines in red have to be activated, the blue ones
\ndeactivated. The path to AuthUserFile has to be adapted to your environment. Besides basic authentication
\nyou can use every other authentication method supported by Apache (LDAP\/Kerberos\/MySQL\/etc.) \u2013
\nplease consult the Apache documentation for details.
\nPlease verify that Apache processes these *.conf files at all. This might be done via http.conf or using a
\nsuitable VirtualHost configuration:
\nInclude \/etc\/apache2\/conf.d\/nagiosql.conf
\nDon\u2019t forget to create the web folder, test the new configuration and activate the changes
\n(SLES\/openSuSE):
\n# rcapache2 configtest
\n# rcapache2 restart
\nFedora\/RHEL\/CentOS:
\n# service http restart
\nDebian\/Ubuntu:
\n# \/etc\/init.d\/apache2 restart
\nNagiosQL 3.2 ? Installation Page 6
\n1.5 Install PHP modules (SSH)
\nIf PHP modules are missing (prerequisites or installer), they have to be installed before continuing. In most
\ncases this is possible using the tools included in your distribution (YaST\/apt?get\/rpm). A special case is the
\nSSH module. Following some instructions on how to install SSH for NagiosQL.
\nTo install the SSH module the tool PECL is needed. Normally this can be installed using the package tool
\n(YaST\/apt?get\/rpm).
\nIf PECL is installed it can be called issuing:
\n# pecl
\nWithout any parameters some help text is shown. If the system is behind a proxy server, it might be
\nnecessary to configure PECL to use it:
\n# pecl config-set http_proxy http:\/\/proxy.myserver.tld:8080
\n# pecl config-show
\nNow the SSH module can be installed:
\n# pecl install ssh2
\nThen is has to be included in php.ini. Don\u2019t forget to restart Apache:
\nextension = ssh2.so
\n# rcapache2 restart
\nThe setup of a user for SSH is shown later on in this guide.
\n1.6 Install NagiosQL
\nNow you can install NagiosQL into the new web folder. Please copy it to \/opt (not \/opt\/nagiosql) and
\nunpack it:
\n# cd \/opt
\n# gunzip \u2013c nagiosql_320.tar.gz | tar xf \u2013
\n# mv nagiosql32 nagiosql
\n# chown \u2013R wwwrun \/opt\/nagiosql
\n# chmod 750 \/opt\/nagiosql\/config
\nNow NagiosQL should be reachable via your web browser:
\nhttp:\/\/localhost\/nagiosql
\nhttp:\/\/mein.virtualhost.tld\/nagiosql
\nNagiosQL 3.2 ? Installation Page 7
\n1.7 NagiosQL installer (new installation)
\nNormally the installer is started automatically during the first call of NagiosQL. You might start it manually
\nas well:
\nhttp:\/\/localhost\/nagiosql\/install\/index.php
\nIf all is correct your browser should something like the following:
\nThis page just shows a short list of the current prerequisites for the installation of NagiosQL. Additionally it
\nis possible to select your favourite language.
\nSTART UPDATE is only available if a valid version of settings.php of a previous version was copied to
\n\/opt\/nagiosql\/config. The update is described later on in 1.8.
\nNagiosQL 3.2 ? Installation Page 8
\nClick START INSTALLATION to continue.
\nNext are the environment tests divided into seven sections.
\nThe following image shows an executable environment:
\nChecking Client:
\nIt is checked if the browser processes JavaScript and if this is activated. Some browser add?ons can disable
\nJavaScript \u2013 if this is the case JavaScript has to be enabled for NagiosQL explicitly.
\nCheckin PHP version:
\nIt is checked if the PHP version is adequate. If this is not the case you have to update your PHP version.
\nConsult the documentation of your distribution for details.
\nNagiosQL 3.2 ? Installation Page 9
\nChecking PHP extensions:
\nThe first PHP extensions are mandatory. Missing ones must be installed to be able to use NagiosQL. The
\noptional extensions only have to be installed if you want to use the appropriate options of NagiosQL.
\nChecking available database connections:
\nNagiosQL requires at least one PHP module to interface with a database (e.g. module MySQL).
\nChecking php.ini\/.htaccess settings:
\nIt is checked if the required settings in php.ini are correct (see 1.4)
\nChecking System Permissions:
\nIt is checked if all NagiosQL files are readable\/writeable. At the most some permissions have to be
\nmodified. If you followed this guide all settings should be correct already.
\nYou can recheck the environment by calling install\/index.php and clicking START INSTALLATION once again.
\nIf all tests are successful you can click on \u201eNext\u201c to get to the next page:
\nNagiosQL 3.2 ? Installation Page 10
\nOn this page the information for the database server is specified.
\nDatabase Type: Select the database type (not yet active in 3.2.0)
\nDatabase Server: Host name of the database server
\nLocal hostname or IP address: Host name or IP address of the web server
\nImportant: if the database server is not running on the same system as the web server the entry \u201elocal
\nhostname\u201c is used to specify the access (source) for the database server!
\n(allow access for: nagiosql_user@webserver)
\nDatabase Server Port: TCP port of the database server daemon
\nDatabase name: Name of the database to be created for NagiosQL
\nNagiosQL Database User: User name for the NagiosQL database
\nNagiosQL Database Password: Password of the NagiosQL database user
\nThe NagiosQL database user will not exist during a new installation and will be created according the
\ninformation given here.
\nAdministrative Database User: Admin user
\nAdministrative Database Passwort: Admin password
\nThe administrative user (e.g. root) has to exist already and must have sufficient rights to create a new
\ndatabase and a user which will be given access to the new database. The data of the administrative user will
\nNOT be stored in NagiosQL \u2013 it will only be used to create the database.
\nDrop database if already exists: Delete a database with the same name (Attention)
\nInitial NagiosQL User: NagiosQL admin user (admin)
\nInitial NagiosQL Password: NagiosQL admin password
\nAdministrative user for login to the NagiosQL web application. This user cannot be deleted later on.
\n\u201eImport Nagios sample config\u201c would import some sample data into the database.
\n\u201eCreate NagiosQL config paths\u201c creates a directory structure as decribed in 1.2 (which isn\u2019t necessary
\nanymore if you are following this guide). One requirement would be that the NagiosQL config directory is
\nwriteable for the webserver daemon. A modification of UID\/GID is not possible so it has to be done later on
\nmanually.
\nNagiosQL config path: Base directory for the config files
\nNagios config path: Base directory for the Nagios config files (contains nagios.cfg)
\nThis information is used to preconfigure the \u201elocalhost\u201c domain.
\nNagiosQL 3.2 ? Installation Page 11
\nIf all information was entered correctly and the database could be created, you get the following output:
\nAfterwards the directory \/opt\/nagiosql\/install should be deleted.
\n# rm \u2013rf \/opt\/nagiosql\/install
\nAfter successful installation some base configurations within NagiosQL have to be checked or set. The next
\nchapter deals with this task.
\nNagiosQL 3.2 ? Installation Page 12
\n1.8 Update NagiosQL
\nUpdate is similar to the installation as described in 1.7. Please note that the file config\/settings.php of the
\nold NagiosQL installation will not be modified and is copied to the config directory of the new installation.
\nYou must never copy the files of a new version into the existing directory of an old\/previous NagiosQL
\nversion!
\nIt is very important to backup the existing database before you start! Otherwise if anything goes wrong
\nduring the update it cannot be repeated and the database may be corrupt and in an undefined state. In
\nmost cases you then have to run a new installation and import all configuration data.
\nA backup can be made very easily using common tools like phpMyAdmin. Alternatively there are command
\nline tools like mysqldump.
\nClick START UPDATE to continue.
\nAfterwards the same environment tests are executed as during a new installation. Please consult the page
\nfor details.
\nNagiosQL 3.2 ? Installation Page 13
\nIf all tests are successful you can click on \u201eNext\u201c to get to the next page:
\nTo run the update as expected you only have to enter the information regarding the administrative
\ndatabase user. The other data is modifiable as well but you should only alter it if you are sure that you
\nknow what you are doing.
\nAdministrative Database User: Admin user
\nAdministrative Database Passwort: Admin password
\nThe administrative user (e.g. root user) has to exist already and must have sufficient rights to create a new
\ndatabase and a user which will be given access to the new database. The data of the administrative user will
\nNOT be stored in NagiosQL \u2013 it will only be used to create the database.
\nNagiosQL 3.2 ? Installation Page 14
\nIf all information was entered correctly and the database could be created, you get the following output:
\nAfterwards the directory \/opt\/nagiosql\/install should be deleted.
\n# rm \u2013rf \/opt\/nagiosql\/install
\nNagiosQL 3.2 ? Installation Page 15
\n2 Configure NagiosQL
\n2.1 Base configuration
\nThe NagiosQL base configuration can be accessed in the web application clicking Administration \u2013 Settings.
\nHere you will find some other data which you entered using the installer. The blue question mark symbol
\nnext to each item will show a short help text.
\nWorth mentioning are the following values:
\nTemporary Directory: The directory NagiosQL uses to store temporary files. Normally this will
\nbe \/tmp.
\nServer protocol: If NagiosQL is installed in an SSL environment you can choose https.
\nSetting an incorrect value might affect\/end the operation!
\nLanguage: The NagiosQL interface might be changed to use another language.
\nSometimes the browser cache has to be cleared, the browser and\/or
\nApache to be restarted so that the new setting takes effect.
\nAuthentication type: If the Apache authentication is to be used this value has to be set
\naccordingly.
\nData lines per page: The number of lines in list views can be set here.
\nOnline version check: The NagiosQL support page will show if a new NagiosQL version is
\navailable.
\nEnvironments using a proxy server will have to set the appropriate values.
\nNagiosQL 3.2 ? Installation Page 16
\n2.2 Domain config (paths)
\nThe different domains and paths of the Nagios installations to be controlled are determined using the
\ndomain administration. This is to be found below Administration.
\nThere are two sorts of domains:
\n2.2.1 Data domains
\nData domains are used for data storage, i.e. they contain the configuration objects. The selection field in
\nthe upper left of the view always shows the currently active data domain.
\nThere are two given data domains which cannot be deleted or renamed:
\nCommon Data Domain
\nA general data domain which can be included into every other data domain. This might be useful for
\ncontacts, time periods, or commands, which are identical in every data domain. There are only very few
\nsettings available.
\nLocalhost Data Domain
\nThe data domain of the local server. Apart from the fact that this data domain cannot be renamed there is
\nno difference to other data domains.
\nNagiosQL 3.2 ? Installation Page 17
\nConfiguration options
\nDomain: Internal name of the data domain (will be shown in the config views).
\nDescription: Detailed description of the data domain
\nConfiguration target: Selection of the target configuration domain (see 2.2.2).
\nNagios Version: Version of the Nagios installation (version 2.x or 3.x are supported) \u2013 depending
\non the version additional options are displayed in the views.
\nUse common domain: The common data domain can be switched on or off. As soon as the common
\ndata domain is switched on and objects are defined, these objects will be written
\ninto the config files of the current data domain.
\nAccess group: Select which user group gets access to this data domain.
\nActive: Define whether the data domain is active or not.
\nNagiosQL 3.2 ? Installation Page 18
\n2.2.2 Configuration domain
\nConfiguration domains are used to define a Nagios installation (site), they contain the paths and connection
\nsettings.
\nConfiguration options
\nDomain: Internal name of the configuration domain
\n(will be shown in data domain \u2013 config target)
\nDescription: Detailed description of domain
\nServer name: Host name of the system running the Nagios installation of this domain \u2013 must be
\nresolvable to an IP address
\nMethod: The connection type specifies how NagiosQL will access the config files. Valid
\noptions are:
\n? Fileaccess The files are stored on the local file system of the server
\nor are accessible from there (NFS\/SMB\/CIFS etc.)
\n? FTP The config files are accessed via FTP
\n? SSH\/SFTP The config files are accessed via SSH\/SFTP
\nIn the next chapter (2.3) we will give some short instructions on how to setup FTP
\nand SSH\/SFTP
\nUser name: User name to login onto the target system (only FTP or SSH\/SFTP)
\nPassword: Password to login onto the target system (only FTP or SSH\/SFTP)
\nDir. with SSH key
\npair:
\nLocal directory where the SSH key is stored (only SSH\/SFTP)
\nNagiosQL 3.2 ? Installation Page 19
\nBase directory: Base directory for Nagios config files. All config files apart from those for hosts
\nand services are stored in this folder.
\n\/etc\/nagiosql
\nHost directory : Directory for the Nagios host config files
\n\/etc\/nagiosql\/hosts
\nService directory: Directory for the Nagios service config files
\n\/etc\/nagiosql\/services
\nBackup directory: Directory where NagiosQL will store backup versions of config files (except for
\nhosts\/services)
\n\/etc\/nagiosql\/backup
\nHost backup dir.: Directory where NagiosQL will store backup versions of host config files
\n\/etc\/nagiosql\/backup\/hosts
\nService backup dir.: Directory where NagiosQL will store backup versions of service config files
\n\/etc\/nagiosql\/backup\/services
\nNagios base dir.: Base directory of the Nagios installation. The files nagios.cfg and cgi.cfg are
\nstored in this directory and NagiosQL expects them to be there!
\n\/etc\/nagios
\nImport directory: Alternative import directory. Config files in this directory are offered to be
\nimported as well
\n\/etc\/nagios\/objects
\nPicture base dir.: Alternative image directory. Normally the path to images is static in Nagios (e.g.
\n\/usr\/local\/nagios\/share\/images\/logos). This directory can be used as a second
\nbase directory for additional files\/directories. Other definitions using the folder
\nare relative to this entry.
\nNagios command file: Path to the Nagios command file (nagios.cmd). This file is required to send
\nexternal commands to the Nagios daemon. Please note that this file is only
\ncreated \/ read when check_external_commands=1 is set in nagios.cfg!
\n\/var\/nagios\/rw\/nagios.cmd
\nNagios binary file: Path to the Nagios binary
\n\/opt\/nagios\/bin\/nagios
\nNagios Process file: Path to the Nagios process file (PID or LOCK file)
\n\/var\/nagios\/nagios.lock
\nNagios config file: Path to nagios.cfg
\n\/etc\/nagios\/nagios.cfg
\nNagios version: Version of the Nagios installation (Version 2.x or 3.x are supported).
\nAccess group: Select which user group gets access to this data domain
\nActive: Define whether the data domain is active or not
\nNagiosQL 3.2 ? Installation Page 20
\n2.3 2.3 Setup remote access (FTP or SSH\/SFTP)
\n2.3.1 Remote access via FTP
\nOn the local system the PHP module ftp has to be installed.
\nOn the target system an FTP server has to be installed. Additionally a separate user for NagiosQL is set up.
\nThe NagiosQL directory structure as described in 1.2 will be created on the target system. Furthermore the
\npermissions on the remote system have to be set up as described in 1.2 and 1.3. Instead of the web server
\ndaemon the NagiosQL FTP user has to get write permissions.
\nThe credentials of the NagiosQL FTP user have to filled into the fields user and password in the domain
\nconfiguration (2.2).
\nIt is recommended to check the FTP connection using an FTP client before you enter the values.
\nUsing FTP the functionality in \u201eTools \u2013 Nagios control\u201c is limited. \u201eCheck configuration files\u201c and \u201eRestart
\nNagios\u201c via FTP will only work on a server supporting REMOTE EXEC \u2013 but due to security limitations
\nnowadays this is rarely seen.
\n2.3.2 Remote access via SSH\/SFTP
\nOn the local system the PHP module ssh2 has to be installed (1.5).
\nOn the target system an SSH server has to be installed. Allow access (firewall etc.) from the local system to
\nthe target system.
\nCreate a new user for NagiosQL on the target system, e.g. nagiosql_usr. Please note that some distributions
\nmay limit the length of user names. Then you have to create a key pair as follows.
\nLocal system:
\n1. Create a path for the SSH keys:
\n# mkdir \/etc\/nagiosql\/ssh
\n2. Create a key pair \u2013 only rsa is supported:
\n# ssh-keygen -t rsa
\nGenerating public\/private rsa key pair.
\nEnter file in which to save the key (\/root\/.ssh\/id_rsa): \/etc\/nagiosql\/ssh\/id_rsa
\n?> leave the password empty!
\nThe name of the key file must be id_rsa!
\n3. The key is to be copied to the target system:
\n# ssh-copy-id -i \/etc\/nagiosql\/ssh\/id_rsa\/id_rsa.pub nagiosql_usr@remote-system
\n4. The key in \/etc\/nagiosql\/ssh has to be readable for the web server daemon!
\n# chown \u2013R wwwrun.nagios \/etc\/nagiosql\/ssh
\n# chown \u2013R wwwrun.nagios \/etc\/nagiosql\/ssh\/id_rsa
\n5. Please check login manually:
\n# ssh -i \/etc\/nagiosql\/ssh\/id_rsa nagiosql_usr@remote-system
\n?> Login has to be possible without entering a password!
\nThe name of the NagiosQL SSH user (nagiosql_usr) will be set in the domain config (2.2) filling in \u201cUser
\nname\u201d. The field for the SSH key pair directory will hold the value of the directory (\/etc\/nagiosql\/ssh\/).
\nNagiosQL 3.2 ? Installation Page 21
\nThe field \u201cpassword\u201d can be left empty because it is not used.
\nAn authentication using user and password (without key) is possible but strongly discouraged because it is
\ngenerally more error prone. If you still want to use it then you have to set the following value in
\nsshd_config on the target system:
\nPasswordAuthentication yes
\nNagiosQL 3.2 ? Installation Page 22
\n3 Nagios Configuration
\n3.1 Nagios Configuration file
\nThe Nagios configuration file nagios.cfg has to be adapted so that Nagios can find and use the configuration
\nfiles written by NagiosQL. This can be done using the integrated editor of NagiosQL, if the access
\npermissions were set correctly (1.3).
\nImportant are the paths of the standard config files:
\ncfg_file=\/etc\/nagiosql\/contacttemplates.cfg
\ncfg_file=\/etc\/nagiosql\/contactgroups.cfg
\ncfg_file=\/etc\/nagiosql\/contacts.cfg
\ncfg_file=\/etc\/nagiosql\/timeperiods.cfg
\ncfg_file=\/etc\/nagiosql\/commands.cfg
\ncfg_file=\/etc\/nagiosql\/hostgroups.cfg
\ncfg_file=\/etc\/nagiosql\/servicegroups.cfg
\ncfg_dir=\/etc\/nagiosql\/hosts
\ncfg_dir=\/etc\/nagiosql\/services
\nSome additional config files if they are used:
\ncfg_file=\/etc\/nagiosql\/hosttemplates.cfg
\ncfg_file=\/etc\/nagiosql\/servicetemplates.cfg
\ncfg_file=\/etc\/nagiosql\/servicedependencies.cfg
\ncfg_file=\/etc\/nagiosql\/serviceescalations.cfg
\ncfg_file=\/etc\/nagiosql\/hostdependencies.cfg
\ncfg_file=\/etc\/nagiosql\/hostescalations.cfg
\ncfg_file=\/etc\/nagiosql\/hostextinfo.cfg
\ncfg_file=\/etc\/nagiosql\/serviceextinfo.cfg
\nAll existing lines starting with cfg_file= or cfg_dir= have to be removed or deactivated using a leading hash
\nsign (#)! There must be no other cfg lines except the ones mentioned above.
\nRestarting Nagios from NagiosQL requires that Nagios has to accept external commands which is controlled
\nby the following line in nagios.cfg:
\ncheck_external_commands=1
\n3.2 Additional permissions
\nFor complete functionality of NagiosQL some Nagios files have to be accessible for NagiosQL (see 1.3). For
\nlocal installations the user running the web server daemon has to be permitted, remote installations
\nrequire the NagiosQL FTP or SSH\/SCP user to be permitted. Subsequently the guide uses the term \u201euser\u201c.
\nThe paths to these files have to be set in the domain configuration (see 2.2). Regarding the
\npermissions there are several ways (file permissions, sudo, acl). Furthermore the installations
\ndiffer individually.
\n3.2.1 Check command
\nTo check the curring configuration NagiosQL will use the internal verify method of Nagios:
\n# nagios \u2013v nagios.cfg
\n<nagios?binary> ?v <nagios configuration file>
\nThe user must have permissions to execute the Nagios binary and read permissions on nagios.cfg.
\nNagiosQL 3.2 ? Installation Page 23
\n3.2.2 Configuration editor
\nThe files nagios.cfg and cgi.cfg can be edited directly from within NagiosQL using a simple editor.
\nThe user must have write permissions on the config files nagios.cfg and cgi.cfg.
\n3.2.3 Restart command
\nTo activate a new configuration directly from within NagiosQL permissions on the command file
\nnagios.cmd and the process file nagios.lock are required.
\nThe user must have write permissions on the command file nagios.cmd and read permissions on the
\nprocess file nagios.lock , or nagios.pid, respectively.
\n3.3 Support page
\nSince NagiosQL 3.2.0 we have a support page running the most important internal checks and showing the
\nresults. Common misconfigurations are detected quickly and you are able to solve your problems.
\n3.3.1 Common checks
\nYou will find some helpful links. Basic environment checks are executed. If something doesn\u2019t work after a
\nsystem upgrade you might find a hint.
\nIf enabled it will be checked if the most current version of NagiosQL is installed.
\nNagiosQL 3.2 ? Installation Page 24
\n3.3.2 Config checks
\nIt will be checked if all relevant Nagios files are available and if the user permissions are correct (see 1.3).
\nThe last part processes the Nagios config file (nagios.cfg) and checks if the necessary path settings (see 3.1)
\nwere made and if they are equal to the ones in the selected config domain.
\nGenerally all red entries on the support page indicate a problem which must be solved. Yellow entries
\nindicate problems which might pop up later.<\/p>\n","protected":false},"excerpt":{"rendered":"
NagiosQL 3.2<\/p>\n
NagiosQL 3.2 ? Installation Page 2 Table of contents 1 Installation ………………………………………………………………………………………………………………………………. 3 1.1 Prerequisites …………………………………………………………………………………………………………………….. 3 1.2 Prepare directory structure …………………………………………………………………………………………………. 3 1.3 Nagios configuration files ……………………………………………………………………………………………………. 4 1.4 Prepare Apache configuration……………………………………………………………………………………………… 5 1.5 Install PHP modules (SSH) …………………………………………………………………………………………………… 6 1.6 Install NagiosQL ………………………………………………………………………………………………………………… 6 1.7 NagiosQL installer (new installation) …………………………………………………………………………………….. 7 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[41],"tags":[],"_links":{"self":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/2465"}],"collection":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2465"}],"version-history":[{"count":3,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/2465\/revisions"}],"predecessor-version":[{"id":2466,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/2465\/revisions\/2466"}],"wp:attachment":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2465"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2465"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2465"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}