Last week, when Nagios was restarted, it encountered nrpe: unable to read output. After searching the Internet, it was found that many people would encounter this problem
About the problem I encountered at that time, I modified the Nagios configuration and the nrpe. Conf configuration of the client. After restarting nrpe.conf, Nagios starts to alarm “unable to read output”. This problem does not occur when the configuration is not modified. After checking the configuration several times, there is still no harvest. The client can get the information by executing the command, but Nagios gets the information “unable to read output”.
Solution process:
When killing nrpe, the nrpe process is not completely killed, and the new configuration cannot be loaded in.
Three possibilities of problems in “nrpe: unable to read output”
1. Wrong configuration of CFG file
2. Wrong path configuration, related to the path parameter
3. Check whether the permissions of the client nrpe are readable and can be executed by Nagios. If the Nagios permission is not enough, it needs to be raised.
Similar Posts:
- Nginx Error: nginx: [emerg] “server” directive is not allowed here in
- Raspberry pie “wlan0: not associated” error reporting solution
- Solution of [errno 5] input / output error after Django is deployed on nginx
- [Solved] Nginx Log Error: open() “/opt/Nginx/nginx/nginx.pid” failed (2: No such file or directory)
- [Solved] RPC mount export: RPC: Unable to receive; errno = No route to host
- [mjpeg @ …] unable to decode APP fields: Invalid data found when processing input
- Xampp modify the port number Apache service detected with wrong [How to Solve]
- [Solved] Error: JAVA_HOME is not set and could not be found.
- Authenticate/Decrypt packet error: packet HMAC authentication failed
- Filebeat output redis i/o timeout [How to Solve]