Ad Widget

Collapse

trigger turns UNKNOWN

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mkash28
    Junior Member
    • Oct 2015
    • 13

    #1

    trigger turns UNKNOWN

    i am not very much satisfied with the zabbix so far.
    I setup zabbix server in our lab so I can convince our customer to invest $ in this tool but somehow even I myself not convinced if this is a reliable tool.

    we missed few alert emails for "file system space less then 20% free" and noticed several of our hosts (not all) are showing trigger to be "unknown" with "Cannot obtain filesystem information: [13] Permission denied" message."

    when these were discovered first, these all showed enable green status. soon after that it turned "unknown".
    same thing happens with custom created trigger for the same (less then 20% free remaining) item. soon after it is created it turns unknown.

    zabbix_agentd -t vfs.fs.discovery
    returns full list of mounts.

    permissions are not any different then any other mounts on other systems that are no "unknown" almost all mounts have 755 chmod.
    OS centOS6.7, selinux enabled (but behaves the same way even if it is 'setenforce 0').

    do not want to add zabbix to the group. any other reasonable solution or troubleshooting i can do??
Working...