Nagios and Cacti troubleshooting considerations
Nagios and Cacti troubleshooting considerations
I. Precautions for Naigos restart
1. Check the configuration file integrity before restarting the nagios Service (perform web page synchronization)
2. Pay attention to the Operation Sequence During master-slave synchronization. Do not worry about the operation sequence. Check the alarm mechanism (enable or disable notification)
3. Check whether the pnp4nagios process is enabled. If an exception occurs
3.1 check whether the ll/usr/local/nagios/var/rw/nagios. cmd permission is 777 if not modified
3.2 chmod 777 nagios. cmd
3.3 manually enable/etc/init. d/npcd start (small Sun flow chart)
3.4 restart httpd/etc/init. d/httpd restart
3.5 manual web page enabling detection time
4. After the device restarts, check whether the nagios process is normal, if an exception occurs, manually enable the nagios process/usr/local/nagios/bin/nagios-d/usr/local/nagios/etc/nagios. cfg
Ii. Cacti follows up on handling alarms
1. View logs and view a large number of alarms. Use commands to clear memory.
Clear memory
Sync
Echo 3>/proc/sys/vm/drop_caches
2. restore to normal after cleaning, and check the SNMP running status. If an exception occurs, manually enable service snmpd start.
-------------------------------------- Split line --------------------------------------
In RHEL6.4, the Cacti + Spine monitoring host is used to send mail alarms.
Configure Cacti to monitor MySQL database status
Use Cacti + Spine to monitor remote hosts in RHEL6.4
CentOS 5.5 complete installation of Cacti + Spine
Cacti construction document under CentOS 6
Detailed description of Cacti monitoring deployment under RHEL5.9
How to install Cacti in CentOS 6.3
Quick installation and configuration of Cacti in CentOS Linux
-------------------------------------- Split line --------------------------------------
Cacti details: click here
Cacti: click here
This article permanently updates the link address: