{"id":12104,"date":"2019-03-22T10:15:08","date_gmt":"2019-03-22T10:15:08","guid":{"rendered":"http:\/\/www.appservgrid.com\/paw92\/?p=12104"},"modified":"2019-03-22T10:15:08","modified_gmt":"2019-03-22T10:15:08","slug":"icinga-a-next-generation-open-source-linux-server-monitoring-tool-for-rhel-centos-7-0","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw92\/index.php\/2019\/03\/22\/icinga-a-next-generation-open-source-linux-server-monitoring-tool-for-rhel-centos-7-0\/","title":{"rendered":"Icinga: A Next Generation Open Source \u2018Linux Server Monitoring\u2019 Tool for RHEL\/CentOS 7.0"},"content":{"rendered":"

Icinga<\/b>\u00a0is a modern open source monitoring tool that originated from a\u00a0Nagios<\/b>\u00a0fork, and now has two parallel branches,\u00a0Icinga 1<\/b>\u00a0and\u00a0Icinga 2<\/b>. What this tool does is, not to different from Nagios due to the fact that it still uses Nagios plugins and add-ons and even configuration files to check and monitor network services and hosts, but some differences can be spotted on web interfaces, especially on new web interface, reporting capability and easy add-ons development.<\/p>\n

\n

\"Install<\/a><\/p>\n

Install Icinga Monitoring Tool in CentOS\/RHEL 7.0<\/p>\n<\/div>\n

This topic will concentrate on a basic installation of\u00a0Icinga 1<\/b>\u00a0Monitoring Tool from binaries on\u00a0CentOS<\/b>\u00a0or\u00a0RHEL 7<\/b>, using\u00a0RepoForge<\/b>\u00a0(previously known as RPMforge) repositories for CentOS 6, with the classical web interface held by Apache Webserver and the use of Nagios Plugins that will be installed on your system.<\/p>\n

Read Also<\/b>:\u00a0Install Nagios Monitoring Tool in RHEL\/CentOS<\/a><\/p>\n

Requirements<\/h4>\n

A basic\u00a0LAMP<\/b>\u00a0installation on RHEL\/CentOS 7.0 without MySQL and PhpMyAdmin, but with these PHP modules:\u00a0php-cli<\/b>
\nphp-pear<\/b>\u00a0php-xmlrpc<\/b>\u00a0php-xsl<\/b>\u00a0php-pdo<\/b>\u00a0php-soap<\/b>\u00a0php-gd<\/b>.<\/p>\n

    \n
  1. Installing Basic LAMP in RHEL\/CentOS 7.0<\/a><\/li>\n<\/ol>\n

    Step 1: Installing Icinga Monitoring Tool<\/h3>\n

    1.<\/strong>\u00a0Before proceeding with Icinga installation from binaries add\u00a0RepoForge<\/b>\u00a0repositories on your system by issuing the following command, depending on your machine.<\/p>\n

    For 86-64-bit<\/h5>\n
    # rpm -Uvh http:\/\/pkgs.repoforge.org\/rpmforge-release\/rpmforge-release-0.5.3-1.el6.rf.x86_64.rpm<\/pre>\n
    For 32-bit<\/h5>\n
    # rpm -Uvh http:\/\/pkgs.repoforge.org\/rpmforge-release\/rpmforge-release-0.5.3-1.el6.rf.i686.rpm<\/pre>\n
    \n
    \"Install<\/a><\/p>\n
    Install RepoForge Repository<\/p>\n<\/div>\n
    2.<\/strong>\u00a0After RepoForge repositories had been added on your system, start with Icinga basic installation without the web interface yet, by running the following command.<\/p>\n
    # yum install icinga icinga-doc<\/pre>\n
    \n
    \"Install<\/a><\/p>\n
    Install Icinga Monitoring Tool<\/p>\n<\/div>\n
    3.<\/strong>\u00a0The next step is to try to install Icinga web interface provided by\u00a0icinga-gui<\/b>\u00a0package. It seems that for the moment this package has some unresolved issues with CentOS\/RHEL 7, and will generate some transaction check errors, but you can feel free to try to install the package, maybe meanwhile the problem was resolved.<\/p>\n
    Still, if you get the same errors on your machine as the pictures below shows you, use the following approach as further described, to be able to install Icinga web interface.<\/p>\n
    # yum install icinga-gui<\/pre>\n
    \n
    \"Install<\/a><\/p>\n
    Install Icinga Gui<\/p>\n<\/div>\n
    \n
    \"Icinga<\/a><\/p>\n
    Icinga Gui Conflict Error<\/p>\n<\/div>\n
    4.<\/strong>\u00a0The procedure to install\u00a0icinga-gui<\/b>\u00a0package which provides the web interface is the following. First download the binary package form RepoForge website using\u00a0wget<\/b>\u00a0command.<\/p>\n
    For 86-64-bit<\/h5>\n
    # wget http:\/\/pkgs.repoforge.org\/icinga\/icinga-gui-1.8.4-4.el6.rf.x86_64.rpm<\/pre>\n
    For 32-bit<\/h5>\n
    # wget http:\/\/pkgs.repoforge.org\/icinga\/icinga-gui-1.8.4-4.el6.rf.i686.rpm<\/pre>\n
    \n
    \"Install<\/a><\/p>\n
    Install Icinga RPM Package<\/p>\n<\/div>\n
    5.<\/strong>\u00a0After wget finishes downloading the package, create a directory named\u00a0icinga-gui<\/b>\u00a0(you can choose other name if you want), move\u00a0icinga-gui<\/b>\u00a0RPM binary to that folder, enter the folder and extract RPM package contents by issuing the next series of commands.<\/p>\n
    # mkdir icinga-gui\r\n# mv icinga-gui-* icinga-gui\r\n# cd icinga-gui\r\n# rpm2cpio icinga-gui-* | cpio -idmv<\/pre>\n
    \n
    \"Copy<\/a><\/p>\n
    Copy Icinga GUI Packages<\/p>\n<\/div>\n
    6.<\/strong>\u00a0Now that you have the extracted\u00a0icinga-gui<\/b>\u00a0package, use\u00a0ls<\/b>\u00a0command to visualize folder content \u2013 it should result three new directories \u2013\u00a0etc<\/b>,\u00a0usr<\/b>\u00a0and\u00a0var<\/b>. Start by executing a recursive copying of all three resulted directories on your system root file system layout.<\/p>\n
    # cp -r etc\/* \/etc\/\r\n# cp -r usr\/* \/usr\/\r\n# cp -r var\/* \/var\/<\/pre>\n
    \n
    \"Copy<\/a><\/p>\n
    Copy Directories Recursively<\/p>\n<\/div>\n
    Step 2: Modify Icinga Apache Configuration file and System Permissions<\/h3>\n
    7.<\/strong>\u00a0As presented on this article introduction, your system needs to have Apache HTTP server and PHP installed in order to be able to run Icinga Web Interface.<\/p>\n
    After you finished the above steps, a new configuration file should be now present on Apache\u00a0conf.d<\/b>\u00a0path named\u00a0icinga.conf<\/b>. In order to be able to access Icinga from a remote location from browser, open this configuration file and replace all its content with the following configurations.<\/p>\n
    # nano \/etc\/httpd\/conf.d\/icinga.conf<\/pre>\n
    Make sure you replace all file content with the following.<\/p>\n
    ScriptAlias \/icinga\/cgi-bin \"\/usr\/lib64\/icinga\/cgi\"\r\n\r\n<Directory \"\/usr\/lib64\/icinga\/cgi\">\r\n#  SSLRequireSSL\r\n   Options ExecCGI\r\n   AllowOverride None\r\n   AuthName \"Icinga Access\"\r\n   AuthType Basic\r\n   AuthUserFile \/etc\/icinga\/passwd\r\n\r\n   <IfModule mod_authz_core.c>\r\n      # Apache 2.4\r\n      <RequireAll>\r\n         Require all granted\r\n         # Require local\r\n         Require valid-user\r\n      <\/RequireAll>\r\n   <\/IfModule>\r\n\r\n   <IfModule !mod_authz_core.c>\r\n      # Apache 2.2\r\n      Order allow,deny\r\n      Allow from all\r\n      #  Order deny,allow\r\n      #  Deny from all\r\n      #  Allow from 127.0.0.1\r\n      Require valid-user\r\n    <\/IfModule>\r\n <\/Directory>\r\n\r\nAlias \/icinga \"\/usr\/share\/icinga\/\"\r\n\r\n<Directory \"\/usr\/share\/icinga\/\">\r\n\r\n#  SSLRequireSSL\r\n   Options None\r\n   AllowOverride All\r\n   AuthName \"Icinga Access\"\r\n   AuthType Basic\r\n   AuthUserFile \/etc\/icinga\/passwd\r\n\r\n   <IfModule mod_authz_core.c>\r\n      # Apache 2.4\r\n      <RequireAll>\r\n         Require all granted\r\n         # Require local\r\n         Require valid-user\r\n      <\/RequireAll>\r\n   <\/IfModule>\r\n\r\n   <IfModule !mod_authz_core.c>\r\n      # Apache 2.2\r\n      Order allow,deny\r\n      Allow from all\r\n      #  Order deny,allow\r\n      #  Deny from all\r\n      #  Allow from 127.0.0.1\r\n      Require valid-user\r\n   <\/IfModule>\r\n<\/Directory><\/pre>\n
    8.<\/strong>\u00a0After you have edited Icinga httpd configuration file, add Apache system user to Icinga system group and use the following system permissions on next system paths.<\/p>\n
    # usermod -aG icinga apache\r\n# chown -R icinga:icinga \/var\/spool\/icinga\/*\r\n# chgrp -R icinga \/etc\/icinga\/*\r\n# chgrp -R icinga \/usr\/lib64\/icinga\/*\r\n# chgrp -R icinga \/usr\/share\/icinga\/*<\/pre>\n
    9.<\/strong>\u00a0Before starting Icinga system process and Apache server, make sure you also disable\u00a0SELinux<\/b>\u00a0security mechanism by running\u00a0setenforce 0<\/b>\u00a0command and make the changes permanent by editing\u00a0\/etc\/selinux\/config<\/b>file, changing SELINUX context from\u00a0enforcing<\/b>\u00a0to\u00a0disabled<\/b>.<\/p>\n
    # nano \/etc\/selinux\/config<\/pre>\n
    Modify SELINUX directive to look like this.<\/p>\n
    SELINUX=disabled<\/pre>\n
    \n
    \"Disable<\/a><\/p>\n
    Disable SELinux<\/p>\n<\/div>\n
    You can also use\u00a0getenforce<\/b>\u00a0command to view SELinux status.<\/p>\n
    10.<\/strong>\u00a0As the last step before starting Icinga process and web interface, as a security measure you can now modify Icinga Admin password by running the following command, and then start both processes.<\/p>\n
    \n
    # htpasswd -cm \/etc\/icinga\/passwd icingaadmin\r\n# systemctl start icinga\r\n# systemctl start httpd<\/pre>\n
    \n
    \"Create<\/a><\/p>\n
    Create Icinga Admin Password<\/p>\n<\/div>\n
    \n
    \"Start<\/a><\/p>\n
    Start Icinga Service<\/p>\n<\/div>\n
    Step 3: Install Nagios Plugins and Access Icinga Web Interface<\/h3>\n
    11.<\/strong>\u00a0In order to start monitoring public external services on hosts with Icinga, such as HTTP, IMAP, POP3, SSH, DNS, ICMP ping and many others services accessible from internet or LAN you need to install\u00a0Nagios Plugins<\/b>package provided by\u00a0EPEL<\/b>\u00a0Repositories.<\/p>\n
    # rpm -Uvh http:\/\/dl.fedoraproject.org\/pub\/epel\/7\/x86_64\/e\/epel-release-7-6.noarch.rpm\r\n# yum install yum install nagios-plugins nagios-plugins-all<\/pre>\n
    \n
    \"Install<\/a><\/p>\n
    Install Epel Repository<\/p>\n<\/div>\n
    \n
    \"Install<\/a><\/p>\n
    Install Nagios Plugin<\/p>\n<\/div>\n
    12.<\/strong>\u00a0To login on Icinga Web Interface, open a browser and point it to the URL\u00a0http:\/\/system_IP\/icinga\/<\/b>. Use\u00a0icingaadmin<\/b>\u00a0as username and the password that you changed earlier and you can now see your localhost system status.<\/p>\n
    \n
    \"Icinga<\/a><\/p>\n
    Icinga Admin Login<\/p>\n<\/div>\n
    \n
    \"Icinga<\/a><\/p>\n
    Icinga Monitoring Dashboard<\/p>\n<\/div>\n
    That\u2019s all! Now you have Icinga basic with the classical web interface \u2013 nagios like \u2013 installed and running on your system. Using Nagios Plugins you can now start adding new hosts and external services to check and monitor by editing Icinga configuration files located on\u00a0\/etc\/icinga\/<\/b>\u00a0path. If you need to monitor internal services on remote hosts then you must install an agent on remote hosts like NRPE, NSClient++, SNMP to gather data and send it to Icinga main process.<\/p>\n
    Read Also<\/b><\/p>\n
      \n
    1. Install NRPE Plugin and Monitor Remote Linux Hosts<\/a><\/li>\n
    2. Install NSClient++ Agent and Monitor Remote Windows Hosts<\/a><\/li>\n<\/ol>\n
      Source<\/a><\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
      Icinga\u00a0is a modern open source monitoring tool that originated from a\u00a0Nagios\u00a0fork, and now has two parallel branches,\u00a0Icinga 1\u00a0and\u00a0Icinga 2. What this tool does is, not to different from Nagios due to the fact that it still uses Nagios plugins and add-ons and even configuration files to check and monitor network services and hosts, but some … <\/p>\n
      Continue reading “Icinga: A Next Generation Open Source \u2018Linux Server Monitoring\u2019 Tool for RHEL\/CentOS 7.0”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-12104","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/12104","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/comments?post=12104"}],"version-history":[{"count":1,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/12104\/revisions"}],"predecessor-version":[{"id":12105,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/12104\/revisions\/12105"}],"wp:attachment":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/media?parent=12104"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/categories?post=12104"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/tags?post=12104"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}