Nrpe:unable to read output causes and exclusions

The nrpe:unable to read output alarm appears in Nagios monitoring of several recently added hosts, one is Check_mysql and the other is Check_uptime

Check_mysql

I'm now being monitored. Check_mysql is the information returned, so with Check_nrpe to detect Check_mysql also has data returned, but in the monitoring machine execution script on the error, because the running Nrpe is run with sudo, So I added sudo to run check_mysql, so I prompted libmysqlclient.so.15:no such file or directory. Obviously less libmysqlclient.so.15, so whereis MySQL to find the Lib directory MySQL, Then in Lib or lib64 (64-bit system) ln A soft connection to the MySQL libmysqlclient.so.15 file in the Lib directory, and then execute the Check_mysql. The information has been returned to the monitoring machine to perform the check_nrpe-h Hostname-c Check_mysql, Normal.

Check_uptime

There are also reports of nrpe:unable to read output errors, the same on the monitored machine execution check_uptime, normal, sudo check_uptime also normal, using check_nrpe-h hostname-c check_ Uptime, error. So strange, so much so that there are no errors in the machine, why just a few of these machines error, so the idea of replacing Check_uptime script, from other normal monitored host to take the Check_uptime, uploaded to the problematic host, chmod +x Check_ Uptime, perform check_nrpe-h hostname-c check_uptime, normal. It's really a script problem.

Nrpe:unable to read output causes and exclusions