File system discovery delivers no data

[XorroX]

Hey guys,

We currently have the issue, that file system discovery is not delivering any data on 2 hosts.
Discovery in general works perfectly fine on all other hosts.
File system on these specific hosts is "jfs2" which is also listed under Administration --> General --> Regular expressions.

If we connect directly onto the host and run "zabbix_agentd -p" we receive the following:

vfs.fs.discovery [s|{
"data":[
{
"{#FSNAME}":"\/",
"{#FSTYPE}":"jfs2"},
{
"{#FSNAME}":"\/usr",
"{#FSTYPE}":"jfs2"},
{
"{#FSNAME}":"\/var",
"{#FSTYPE}":"jfs2"},
{
"{#FSNAME}":"\/tmp",
"{#FSTYPE}":"jfs2"},
{
"{#FSNAME}":"\/home",
"{#FSTYPE}":"jfs2"},


So the filesystems are correctly identified on the host itself.

We have also tried deleting the host and recreating it directly on the zabbix master and not on a proxy.

Also the discovery for network ports is working fine.

Do you have any idea of what else we could try?

Thanks in advance for your feedback.

[Scanto]

Hi,

I am a colleague of XorroX.
In the zabbix-server.log I found
[Z3005] query failed: [1062] Duplicate entry '15213-vfs.fs.size[/fsNAME,total]' for key 'items_1'

after checking again the vfs.fs.discovery I found two filesystems with #FSNAME=fsname and the other one with #FSNAME=fsNAME.

I'm pretty sure the discovery doesn't work because of the same name of the filesystems just with different capital letters.

[Scanto]

I want to exclude /fsNAME from discovery via a sencond filter.
Therefore I have added {#FSNAME} match ^(?!\/fsNAME)$ AND {#FSTYPE} match @File systems for discovery

Now we don't get any error messages with duplicate keys anymore but the discovery still doesn't work. No new items are created.
Any ideas?

[kloczek]

Hi,

I am a colleague of XorroX.
In the zabbix-server.log I found
[Z3005] query failed: [1062] Duplicate entry '15213-vfs.fs.size[/fsNAME,total]' for key 'items_1'

after checking again the vfs.fs.discovery I found two filesystems with #FSNAME=fsname and the other one with #FSNAME=fsNAME.

I'm pretty sure the discovery doesn't work because of the same name of the filesystems just with different capital letters.

Probably you have conflict with some non-LLD item already present in host set up or LLD is adding duplicates items with te same keys.

[Scanto]

We are getting closer.
Now we have a new regex fsNAME with type /fsNAME [Result is FALSE] and added the filter to the host {#FSNAME} match @fsNAME.

Discovery works now as expected, but how can we monitor now the filesystem /fsNAME. I wanted to add it manually to the host but of course I still can't use the key with fsNAME because we already have items wit fsname in the key.