NAGIOS
It is not enough to simply install and configure the server. For its optimal and reliable performance, it is necessary to monitor its running and the running of other elements in the network and make necessary adjustments. For this reason, the Nagios system is integrated into the ISPadmin system. It automatically monitors individual network devices (routers, servers, UPS etc.). Thanks to this system, it is possible to react very quickly to potential problems in the network or to requests for configuration changes.
For normal use, it is not necessary to configure anything. Everything is preset and ready for use. If you are interested in finding out more about Nagios, you may use the official documentation on the project’s website. Bear in mind, though, we cannot guarantee that monitoring will work correctly once you have made changes to the configuration files.
The configuration of Nagios is automatically updated every time ISPadmin alters it (device monitoring, notification groups). These changes will take effect within 10 minutes. If you modify the configuration files manually, it is necessary to restart Nagios:
/usr/local/script/ispadmin/nagios_cfg.pl; /etc/init.d/nagios restart; /etc/init.d/apache2 restart
Addition of new routers and devices to the system
When adding routers and devices to the system, you can assign them to a so-called superior device for Nagios. If you set this item correctly, given routers or devices will be put into the right place on the topological map and in the Nagios configuration.
It is important to bear in mind, though, that Nagios cannot create a ring topology. Such a configuration causes looping. That is why you should avoid creating such network topologies. If you already use it, edit the settings of the wrongly configured devices so that they are no longer in such a configuration.
nagios3 /usr/local/nagios/etc/nagios.cfg
/etc/init.d/nagios restart
Outage notifications
ISPadmin supports notifications for outages of servers, routers, and other connected devices (e.g. UPS) through the NAGIOS monitoring system.
The system uses these notification groups to distribute router failure, server failure, additional network device (UPS, IP camera etc.) failure notifications among individual network administrators.
Available notification groups:
- Email - It is easy to set up and it is free of charge.
- SMS - It is somewhat more difficult to set up and it is not free of charge, but if Internet is not working, it enables you to check devices through an independent (GSM) network (SMS gateway).
- Push - Notifications are shown on your portable device using the Task Manager application.
- Dashboard - Notifications are shown in the Dashboard.
How to set up notifications
Solutions to possible problems
Error: Could not read host and service status information!
- Possible cause: Incorrectly configured dependencies between devices
- Solution: Modification of problematic dependencies
- Restart the Nagios system using the following command: /etc/init.d/nagios restart
- A list of potential problems will appear.
- Modify the dependencies between devices on its basis.
- Make the system load the modified configuration using the following command: /usr/local/script/ispadmin/nagios_cfg.pl
- Restart the Nagios system one more time using the following command: /etc/init.d/nagios restart.
Error: Not Found
- To solve this problem, you have to remove the whole line containing the NAGIOS_SECRET field from the configuration file /data/support/ispadmin/config/config.php.
- Then, update the system with the help of the following command: admin_update stable.
- The automatic update of the Nagios hash used will be performed.
- If, despite this, the error message “The requested URL ... was not found on this server” appears, it will be necessary to update the Nagios hash manually.
-
Make the system provide you with the current Nagios hash using the following command:
more /etc/nagios3/apache2.conf |grep Alias
e.g. ScriptAlias /cgi-bin/2825857159481299247580/usr/lib/cgi-bin/nagios3 - Enter the hash into the configuration file /data/support/ispadmin/config/config.php. Replace the old hash with the new one in the NAGIOS_SECRET item.