[#ZBX-8617] vfs.fs.size* and vfs.fs.inode* metrics for nested mounpoints claim ZBX

[ZBX-8617] vfs.fs.size* and vfs.fs.inode* metrics for nested mounpoints claim ZBX_NOTSUPPORTED Created: 2014 Aug 13 Updated: 2017 May 30 Resolved: 2014 Oct 07
Status:	Closed
Project:	ZABBIX BUGS AND ISSUES
Component/s:	Agent (G)
Affects Version/s:	2.0.12, 2.2.3, 2.2.5
Fix Version/s:	None

Type:

Incident report

Priority:

Major

Reporter:

Tomas Pipo

Assignee:

Unassigned

Resolution:

Won't fix

Votes:

Labels:

agent, mountpoint, nested

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

OS Linux RedHat 5.x,6.x, AIX, HPUX

Description

We have many nested mount points on our servers,but these can't be monitored, because they keep in state Not supported.
Brief explanation of this behavior:
First FS is mounted into /mount and second into /mount/fs2. In Zabbix the server has items vfs.fs.size[fs, free|total|pused] for these two FS. First fs in /mount has all items supported,but second fs in /mount/fs2 claims 'Not supported' on all associated items. Tested on HPUX,AIX,Linux with same results.

Some debug from agent log:
Processing request.
Requested [vfs.fs.size[/mount/fs2,free]]
Sending back [ZBX_NOTSUPPORTED]
In send_buffer() host:'zabbix_server.domain.cz'
port:10051 values:0/100
End of send_buffer():SUCCEED
Sleeping for 1 second(s)

Thank you

Comments

Comment by Alexander Vladishev [ 2014 Sep 01 ]

What filesystems are mounted?
Whether has access to these mount points the zabbix-user?

Comment by Tomas Pipo [ 2014 Oct 07 ]

You're right, Alex. Sorry for my mistake - zabbix user had no access to these nested mount points. Closing the issue.

Generated at Sat Apr 27 00:58:31 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.

[ZBX-8617] vfs.fs.size* and vfs.fs.inode* metrics for nested mounpoints claim ZBX_NOTSUPPORTED Created: 2014 Aug 13 Updated: 2017 May 30 Resolved: 2014 Oct 07