NRPE: Unable to read output

简介:

NRPE: Unable to read output

 

除了百度常见的三种情况:

1.nagios目录权限

2.监控脚本位置路径和权限

3.Nrpe.cfg的脚本路径

 

还有一种是缺少依赖安装包,可以通过脚本的绝对路径+参数去测试。

比如,我遇到一种情况:

/usr/local/nagios/libexec/check_nrpe -H localhost -c check_disks

显示NRPE: Unable to read output

/usr/local/nagios/libexec/check_disks 70 80

显示缺少glibc的一个包,yum 安装这个包之后就可以测试通过了

OK -Disk  All partitions have enough space.




      本文转自YU文武貝 51CTO博客,原文链接:http://blog.51cto.com/linuxerxy/1783821 ,如需转载请自行联系原作者

相关文章
成功解决OSError: Unable to open file (truncated file: eof = 8388608, sblock->base_addr = 0, stored_eof =
成功解决OSError: Unable to open file (truncated file: eof = 8388608, sblock->base_addr = 0, stored_eof =
成功解决OSError: Unable to open file (truncated file: eof = 8388608, sblock->base_addr = 0, stored_eof =
|
缓存 JavaScript
Error: EPERM: operation not permitted, mkdir ‘C:\Program Files\nodejs‘TypeError: Cannot read proper
Error: EPERM: operation not permitted, mkdir ‘C:\Program Files\nodejs‘TypeError: Cannot read proper
183 0
|
Windows
UE INI File Operation [ Read / Write ] Plug-in description
UE INI File Operation [ Read / Write ] Plug-in description
90 0
未解决:dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/-1.diff.rm5mTN
未解决:dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/-1.diff.rm5mTN
135 0
|
开发工具 Android开发
unable to write jarlist cache file
unable to write jarlist cache file
106 0
|
SQL 测试技术
The process could not read file xxx due to OS error 53
在不同地域的两个SQL Server服务器上配置了复制(Replication)用于同步数据(生产环境配置有Replication,测试环境也配有Replication),两地通过专线连接起来,这些复制(Replication)已经稳定运行了一两年了, 但是前阵子,测试环境的SQL Se...
1104 0