Hi,
I've encountered an issue with the latest Zabbix 3.4.1.
on the client side, I have an ubuntu server with several NFS mounts, where I'm trying to monitor NFS hung mounts.
For that I've created an artificial hung mount (hard mount on the client and stopped the nfs-kernel-server daemon on the server side) in order to catch it with my script.
There I encountered a side affect (bug?), that causes Zabbix agent to become unreachable when there is a hung mount on the server.
It doesn't seems related to the check hung mount script that i'm running
Has anyone encountered this issue in the past? is there a solution to it? Shoot
-Moshe
I've encountered an issue with the latest Zabbix 3.4.1.
on the client side, I have an ubuntu server with several NFS mounts, where I'm trying to monitor NFS hung mounts.
For that I've created an artificial hung mount (hard mount on the client and stopped the nfs-kernel-server daemon on the server side) in order to catch it with my script.
There I encountered a side affect (bug?), that causes Zabbix agent to become unreachable when there is a hung mount on the server.
It doesn't seems related to the check hung mount script that i'm running
Has anyone encountered this issue in the past? is there a solution to it? Shoot
-Moshe
there was many bugfixes released so it is better to update.
Comment