discovery not adding mounts, and free space on mounts unsupported

[captainmish]

Hi

I've got a server with zabbix agent 2.2.1 installed, and am getting most details through fine, apart from some disks. It is not adding any disks mounted with more than one directory level for the mount point it seems eg / and /boot are discovered, but /export/data01 is not.

Ive tried to add a manual item for free space, but this just changes to unsupported. I can get the item with zabbix_get, but it breaks when creating an item:

zabbix_get -s x.x.x.x -k vfs.fs.size[/export/data01,free]
# returns expected result, as does (nothing), pfree for second arg

Is there some kind of escaping in the gui that changes the slash in the directory arg? anyone ran into this before?

Thanks!

[captainmish]

I've done some digging in the logs, and it seems like the server gets a different discovery reply to what zabbix_get gets:

21175:20131220:160948.250 In get_value_agent() host:'xxxx' addr:'127.0.0.1' key:'vfs.fs.discovery'
21175:20131220:160948.250 Sending [vfs.fs.discovery
]
21175:20131220:160948.250 get value from agent result: '{
"data":[
{
"{#FSNAME}":"\/",
"{#FSTYPE}":"rootfs"},
{
"{#FSNAME}":"\/sys",
"{#FSTYPE}":"sysfs"},
{
"{#FSNAME}":"\/proc",
"{#FSTYPE}":"proc"},
{
"{#FSNAME}":"\/dev",
"{#FSTYPE}":"devtmpfs"},
{
"{#FSNAME}":"\/dev\/pts",
"{#FSTYPE}":"devpts"},
{
"{#FSNAME}":"\/run",
"{#FSTYPE}":"tmpfs"},
{
"{#FSNAME}":"\/",
"{#FSTYPE}":"ext4"},
{
"{#FSNAME}":"\/sys\/fs\/fuse\/connections",
"{#FSTYPE}":"fusectl"},
{
"{#FSNAME}":"\/sys\/kernel\/debug",
"{#FSTYPE}":"debugfs"},
{
"{#FSNAME}":"\/sys\/kernel\/security",
"{#FSTYPE}":"securityfs"},
{
"{#FSNAME}":"\/run\/lock",
"{#FSTYPE}":"tmpfs"},
{
"{#FSNAME}":"\/run\/shm",
"{#FSTYPE}":"tmpfs"},
{
"{#FSNAME}":"\/boot",
"{#FSTYPE}":"ext2"}]}'
21175:20131220:160948.250 End of get_value():SUCCEED

But if I use zabbix_get:

zabbix_get -s xxxx -k vfs.fs.discovery
{
"data":[
{
"{#FSNAME}":"\/",
"{#FSTYPE}":"rootfs"},
{
"{#FSNAME}":"\/",
"{#FSTYPE}":"ext3"},
{
"{#FSNAME}":"\/dev",
"{#FSTYPE}":"tmpfs"},
{
"{#FSNAME}":"\/proc",
"{#FSTYPE}":"proc"},
{
"{#FSNAME}":"\/sys",
"{#FSTYPE}":"sysfs"},
{
"{#FSNAME}":"\/proc\/bus\/usb",
"{#FSTYPE}":"usbfs"},
{
"{#FSNAME}":"\/dev\/pts",
"{#FSTYPE}":"devpts"},
{
"{#FSNAME}":"\/boot",
"{#FSTYPE}":"ext3"},
{
"{#FSNAME}":"\/dev\/shm",
"{#FSTYPE}":"tmpfs"},
{
"{#FSNAME}":"\/export\/data01",
"{#FSTYPE}":"ext3"},
....<snip about 20 more mountpoints>....

Is there a limit to the number of discovered filesystems? Anything I'm missing?

[captainmish]

retrying the item on a new mountpoint with no "extra" slashes results in the same "unsupported" issue