This article is intended to those who are new to the Icinga installation. This article does not contain full Icinga installation. Rather this has some good information about the errors (and its solutions too) which you would come across while installing and configuring Icinga.
The icinga installation can be done in two ways. The first one is direct installation on a VM with Linux based operating system (CentOS, Ubuntu or RHEL) machine using git repository to install icinga.
The second one is much more simpler – create a virtual machine and attach the VHD file that contains Icinga pre-installed, but this is not recommended if this icinga server is used in a production environment.
If you’re going with the first option then you might need to do network configurations before icinga installation. Else, you can do this once after you install the VHD on your machine.
Now, let’s look at the network configurations that we need to do.
1. Setup IP and gateway. Use the commands below:
IP : ifconfig eth0 IP netmask mask
Gateway : route add default gw gwip adaptername
2. Verify IP and gateway using the commands
ifconfig and route -n. Also make sure that you can reach the other network too by pinging.
3. If you have installed Icinga, try accessing the icinga portal (http://yourip/icinga).
“http/1.1 403 forbidden” warning??
This is expected. Before moving to how to resolve this issue, lets find our what is the reason behind this warning.
Icinga checks for the index pages in the apache or HTTP root directory. So, creating an index file will solve this issue.
How to resolve this issue:
1. Move to the location (/var/www/html/) and create an index file by using the command
2. Restart web services using
service httpd restart or /etc/init.d/httpd restart
3. Restart Icinga services using /etc/init.d/icinga restart
Now reschedule the http warning and you can find it, as solved now 🙂 .
Files used in Icinga:
The main files used in Icinga can be foud in /etc/icinga/ or /usr/local/icinga/
1. icinga.cfg – Main configuration file, which holds all other config files location.
2. resource.cfg – Used to store sensitive configuration information.
3. Object definition files (hostgroups.cfg, hosts.cfg, services.cfg etc) – Used to define hosts, services, hostgroups, contactgroups, commands etc. Define what and how you want to monitor.
4. cgi.cfg – Contains many directives that affect the operation of CGI’s. Contains a reference to the main configuration file.
You might need to download some additional plugins for wide monitoring of your servers. Resource.cfg contains the module location where you need to put these modules.
Make sure that you have full control permission set to the plugin location. Use the command ls -l plugin_location to verify the permission.
If you don’t have full control, then change the permission using chmod command:
chmod zzz plugin_location
where zzz refers to the permission code.
777 – No restrictions on permissions (rwxrwxrwx)
755 – The file’s owner may read, write, and execute the file. All others may read and execute the file (rwxr-xr-x)
700 – The file’s owner may read, write, and execute the file. Nobody else has any rights (rwx——)
666 – All users may read and write the file (rw-rw-rw-)
644 – The owner may read and write a file, while all others may only read the file (rw-r–r–)
600 – The owner may read and write a file. All others have no rights (rw——-)