We have some servers with NFS or CIFS mounts. We started noticing that when we have issues with the NFS mount, we sometimes get alerts indicating all our local mounts are missing. For example, if the NFS mount hangs (i.e. can't connect to the NFS server) we will start getting alerts indicating all local mounts are missing (i.e. /usr is missing).
I don't know how the mount checking works in Zabbix, but the behavior mimics the behavior of running a 'df' on all file systems. Since NFS is hanging, you don't get any data for any of the file systems. Based on the behavior, it looks like you're missing all your local mounts. Is Zabbix doing something similar? Is it trying to collect data on all mounts, including the NFS mount, then failing to get any data because the NFS mount hangs? If so, is there a way to tell Zabbix to exclude the NFS mounts so it can get the data for the other mounts?
I don't know how the mount checking works in Zabbix, but the behavior mimics the behavior of running a 'df' on all file systems. Since NFS is hanging, you don't get any data for any of the file systems. Based on the behavior, it looks like you're missing all your local mounts. Is Zabbix doing something similar? Is it trying to collect data on all mounts, including the NFS mount, then failing to get any data because the NFS mount hangs? If so, is there a way to tell Zabbix to exclude the NFS mounts so it can get the data for the other mounts?

Comment