Ad Widget

Collapse

Zabbix 6.0.5. - vfs.fs.size // Mount is unavailable

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • um3n
    Member
    • Aug 2021
    • 47

    #1

    Zabbix 6.0.5. - vfs.fs.size // Mount is unavailable

    Hello guys,

    we have a windows system with a zabbix agent installed. Currently the C: Mount does not have any data. The error "mount C: is unavailable" is shown.
    The other mounts are working as intended.

    Code:
    [root@ab-zbx-01 ~]# zabbix_get -s 192.168.200.70 -p 10050 -k vfs.fs.size[E:,used]
    96566136832
    [root@ab-zbx-01 ~]# zabbix_get -s 192.168.200.70 -p 10050 -k vfs.fs.size[D:,used]
    182693838848
    [root@ab-zbx-01 ~]# zabbix_get -s 192.168.200.70 -p 10050 -k vfs.fs.size[C:,used]
    ZBX_NOTSUPPORTED: mount 'C:' is unavailable
    Some ideas?

    Kind regards,

    Ulli
  • um3n
    Member
    • Aug 2021
    • 47

    #2
    Recently I had the chance to get hands on the logs of the Windowsserver.

    The Zabbix Agent 2 has a bunch of log entries like this:

    Code:
    2022/03/15 16:16:01.012011 Detected performance counter with negative denominator the second time after retry, giving up...
    2022/03/15 16:16:02.012086 Detected performance counter with negative denominator the second time after retry, giving up...
    2022/03/15 16:35:53.022987 Detected performance counter with negative denominator the second time after retry, giving up...
    2022/03/15 16:35:54.024129 Detected performance counter with negative denominator the second time after retry, giving up...
    2022/03/15 16:35:55.025238 Detected performance counter with negative denominator the second time after retry, giving up...
    2022/03/15 17:03:29.032622 Detected performance counter with negative denominator the second time after retry, giving up...
    2022/03/15 17:03:30.032897 Detected performance counter with negative denominator the second time after retry, giving up...
    2022/03/15 17:03:31.032962 Detected performance counter with negative denominator the second time after retry, giving up...
    After rebooting the agent we recieve new values for the C: mount.

    Any Ideas why this is happening?

    Kind regards!

    Comment

    Working...