VFS.FS.SIZE strange behaviour

[stewie83]

Hi,

I'm running zabbix 3.4.8 (both on server and proxy) and I'm experiencing a very strange behaviour. I've a server running Ubuntu Vivid that is not returning correct value for some fuse filesystem. From the web interface i always see 0B as total, used, pfree, free which is obviously false. I've tried to query the agent both with zabbix_agentd and zabbix_get and this is the result:

zabbix_agentd from the monitored host:

zabbix_agentd -t vfs.fs.size[/srv/dd_rm/imm_log,total]
vfs.fs.size[/srv/dd_rm/imm_log,total] [u|138588670918656] (Correct, is 127TB)

zabbix_get from the zabbix proxy:

zabbix_get -s HOSTNAME -p 10050 -k "vfs.fs.size[/srv/dd_rm/imm_log,total]"
0 (Wrong)

Do you have any advice? I've tried almost everything, no more ideas... Maybe a limitation of the filesystem size monitored by Zabbix?

[kernbug]

Hi,

I'm running zabbix 3.4.8 (both on server and proxy) and I'm experiencing a very strange behaviour. I've a server running Ubuntu Vivid that is not returning correct value for some fuse filesystem. From the web interface i always see 0B as total, used, pfree, free which is obviously false. I've tried to query the agent both with zabbix_agentd and zabbix_get and this is the result:

zabbix_agentd from the monitored host:

zabbix_agentd -t vfs.fs.size[/srv/dd_rm/imm_log,total]
vfs.fs.size[/srv/dd_rm/imm_log,total] [u|138588670918656] (Correct, is 127TB)

zabbix_get from the zabbix proxy:

zabbix_get -s HOSTNAME -p 10050 -k "vfs.fs.size[/srv/dd_rm/imm_log,total]"
0 (Wrong)

Do you have any advice? I've tried almost everything, no more ideas... Maybe a limitation of the filesystem size monitored by Zabbix?

Hi

Plea, show from Ubuntu Vivid:

mount

ls -la /srv/dd_rm/

cat /etc/fstab

[stewie83]

Hi

Plea, show from Ubuntu Vivid:

mount

cat /etc/fstab

(Only relevant part)
xxx:/imm_altro /srv/dd_rm/imm_altro boostfs _netdev 0 0
xxx:/imm_log /srv/dd_rm/imm_log boostfs _netdev 0 0
xxx:/imm_db /srv/dd_rm/imm_db boostfs _netdev 0 0

mount

(Only relevant part)

boostfs on /srv/dd_rm/imm_log type fuse.boostfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
boostfs on /srv/dd_rm/imm_altro type fuse.boostfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
boostfs on /srv/dd_rm/imm_db type fuse.boostfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0)

ls -la /srv/dd_rm/

drwxrwxrwx  6  500 users  420 Jun 15 09:05 imm_altro
drwxrwxrwx 10  500 users  543 Jun  8 08:37 imm_db
drwxrwxrwx  7  500 users  405 Mar 16 15:26 imm_log

cat /etc/fstab

(Only relevant part)

xxx:/imm_altro /srv/dd_rm/imm_altro boostfs _netdev 0 0
xxx:/imm_log /srv/dd_rm/imm_log boostfs _netdev 0 0
xxx:/imm_db /srv/dd_rm/imm_db boostfs _netdev 0 0

[kernbug]

mount

(Only relevant part)

boostfs on /srv/dd_rm/imm_log type fuse.boostfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
boostfs on /srv/dd_rm/imm_altro type fuse.boostfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
boostfs on /srv/dd_rm/imm_db type fuse.boostfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0)

Only for test purposes run Zabbix Agent as root, to be sure this is permission problems or not.

[stewie83]

Only for test purposes run Zabbix Agent as root, to be sure this is permission problems or not.

You're definitely right. It was a permission's problem because they are mounted with Fuse. Thank's you very much.