Nagios Monitoring alarm anomaly Status Two

In the event of a wonderful problem, Nagios monitors the CPU service entry under Windows with the following warning message: (But the other service item status OK, and this warning message will automatically restore the OK state after a period of time and will become as in the warning information status warning)

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/47/1E/wKioL1P26aaBsBkPAAFxRhd8r2w723.jpg "title=" 1.jpg " alt= "Wkiol1p26aabsbkpaafxrhd8r2w723.jpg"/>650) this.width=650; src= http://s3.51cto.com/wyfs02/M01/47/1E/ Wkiol1p26cbhlapyaacbht2zhwi873.jpg "title=" 1.jpg "alt=" Wkiol1p26cbhlapyaacbht2zhwi873.jpg "/>

Solution Ideas:

First: Troubleshoot the cause of this situation:

1. nsclient++ version reason (Troubleshooting the same version of the Server CPU monitoring entry does not appear for this issue)

2. nsclient++ Service Restart (observed not faulted here)

3. Replace the CPU monitoring mode: (changed from CHECK_NT command detection to SNMP detection.) Resolve this issue eventually)

   The first step: Write the SNMP mode to monitor the CPU's script and put it in the following directory:

   650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/47/1E/wKioL1P266jD3C8_AARMNLo5luk988.jpg "title=" 4.jpg " alt= "Wkiol1p266jd3c8_aarmnlo5luk988.jpg"/> The second step: defined in the command.conf file:

   650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/47/1E/wKioL1P268rQhpJaAADFUED1URA804.jpg "title=" 2.jpg " alt= "Wkiol1p268rqhpjaaadfued1ura804.jpg"/>
   

   Step three: Define the service monitoring items:

   650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/47/1E/wKioL1P26_GRQfHEAAH-D6p8Lbo846.jpg "title=" 1.jpg " alt= "Wkiol1p26_grqfheaah-d6p8lbo846.jpg"/>

4. Configure the above steps to restart the Nagios server.

Encounter the Nagios alarm as shown in the behavior:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/47/1E/wKioL1P27GOiobzUAAFAJMO2U3s182.jpg "title=" 1.jpg " alt= "Wkiol1p27goiobzuaafajmo2u3s182.jpg"/>

Analysis: May be/var/empty/sshd directory permissions issue

If you can ssh to the server, then execute the following command on the server to see if the/VAR/EMPTY/SSHD directory permissions are 744

If not, change to 744.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/47/1E/wKioL1P27S_ihy2qAABUUTkNH-0994.jpg "title=" 1.jpg " alt= "Wkiol1p27s_ihy2qaabuutknh-0994.jpg"/>

This article from the "Anna--linux Home" blog, declined to reprint!

Nagios Monitoring alarm anomaly Status Two