由于agent版本差异监控项的参数不一样 , 解决方法升级agent版本 Cannot obtain filesystem information: [2] No such file or directory 提示没有这个监控数值
[root@m01 ~]# zabbix_get -s10.0.1.61-k vfs.fs.size[{#FSNAME},free] ZBX_NOTSUPPORTED: Cannot obtain filesystem information: [2] No such file or directory [root@m01~]# zabbix_agentd -p|grep vfs.fs.size vfs.fs.size[/,free] [u|15713636352] [root@m01~]# zabbix_get -s10.0.1.61...
Server 发送vfs.fs.size[/nono]\n Agent 读取请求并响应<HEADER><DATALEN>ZBX_NOTSUPPORTED\0Cannot obtain filesystem information: [2] No such file or directory Server 处理数据, 更改项目状态为不支持并显示指定的错误消息 TCP连接关闭 主动检查 主动检查需要更复杂的处理,agent 必须首先从server端检索独立处...
● Agent接收请求并且返回响应数据 <HEADER><DATALEN>ZBX_NOTSUPPORTED\0Cannot obtain filesystem information: [2] No such file or directory ● Server接收并处理数据, 将item的状态改为“ not supported ” ● 关闭TCP连接 从以上可以看出,主动模式下server端压力会减小,所以如果线上机器非常多的话,建议尽量使...
ZBX_NOTSUPPORTED\0Cannot obtain filesystem information: [2] No such file or directory Server接收并处理数据, 将item的状态改为“ not supported ” 主动模式 Agent打开TCP连接(主动检测变成Agent打开) Agent请求items检测列表 Server返回items列表 Agent 处理响应 ...
“value”:“Cannot obtain filesystem information: [2] No such file or directory”, “clock”:1400675595, “ns”:78154128 } ], “clock”: 1400675595, “ns”: 78211329 } Server response 《HEADER》《DATALEN》{ “response”:“success”, ...
Agent接收请求并且返回响应数据 <HEADER><DATALEN>ZBX_NOTSUPPORTED\0Cannot obtain filesystem information: [2] No such file or directory Server接收并处理数据, 将item的状态改为“ not supported ” 关闭TCP连接 主动模式: Agent打开TCP连接(主动检测变成Agent打开) ...
Agent接收请求并且返回响应数据 <HEADER><DATALEN>ZBX_NOTSUPPORTED\0Cannot obtain filesystem information: [2] No such file or directory Server接收并处理数据, 将item的状态改为“ not supported ” 关闭TCP连接 主动模式: Agent打开TCP连接(主动检测变成Agent打开) ...
[/nono]\nAgent接收请求并且返回响应数据<HEADER><DATALEN>ZBX_NOTSUPPORTED\0Cannotobtainfilesysteminformation:[2]NosuchfileordirectoryServer接收并处理数据,将item的状态改为“notsupported”关闭TCP连接主动检测如前面所说,zabbix首先向ServerActive配置的IP请求获取activeitems,获取并提交activetiems数据值server或者...
options- the type of log file rotation and other options. Possible values: rotate(default), copytruncate- note thatcopytruncatecannot be used together withmaxdelay. In this casemaxdelaymust be 0 or not specified; seecopytruncatenotes, mtime-reread- non-unique records, reread if modification time ...