Ad Widget

Collapse

Active checks empty list from server

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • gentunian
    Junior Member
    • Apr 2014
    • 6

    #1

    Active checks empty list from server

    Hi,

    I'm working with zabbix 2.0. I have defined a log item as an active check in a host called HOSTA. The log item monitors a file in /tmp/zabbix.test. /tmp directory is accesible for every user and the file /tmp/zabbix.test is chowned to be for zabbix user.

    My zabbix_agentd.conf has the Hostname parameter set:

    Code:
    Hostname=HOSTA
    The ServerActive parameter is:

    Code:
    ServerActive=<ZabbixServerIP>
    From HOSTA I've done a telnet to zabbix server:

    Code:
    telnet <ZabbixServerIp> 10051
    Trying <ZabbixServerIp>...
    Connected to <ZabbixServerIp>.
    Escape character is '^]'.
    And from zabbix server to HOSTA:

    Code:
    telnet <HOSTA_IP> 10050
    Trying <HOSTA_IP>...
    Connected to <HOSTA_IP>.
    Escape character is '^]'.
    But still I got an empty active check list:
    Code:
     23764:20140908:121348.325 refresh_active_checks() host:'<ZabbixServerIp>' port:10051
     23764:20140908:121348.326 sending [{
            "request":"active checks",
            "host":"HOSTA"}]
     23764:20140908:121348.326 before read
     23764:20140908:121348.331 got [{
            "response":"success",
            "data":[]}]
    I have another server (HOSTB) in another vlan that I have configured an active check log item successfully. I need to diagnose the problem, because HOSTA is a production server and HOSTB is a QA server.

    Where to look at? I have exhausted all places, debuglevels, etc...

    Maybe it's a firewall issue. I really can't figured out what I'm missing. Can you please help?

    Best Regards,
    Last edited by gentunian; 08-09-2014, 17:16.
  • gentunian
    Junior Member
    • Apr 2014
    • 6

    #2
    As a side note... the item became supported for a while, as I can see data logged. But it's unsupported now.

    Why can something like that happen? Collected data, nothing changes, the item is NOT SUPPORTED now... any ideas?
    Code:
    3788:20140908:153247.978 item [HOSTA:log[/usr/local/jboss/server/profile2/log/server.log, "Replication timeout"]] became supported
    3811:20140908:153258.833 item [HOSTA:log[/usr/local/jboss/server/profile2/log/server.log, "Replication timeout"]] became not supported: ZBX_NOTSUPPORTED
    3789:20140908:153313.271 item [HOSTA:log[/usr/local/jboss/server/profile2/log/server.log, "Replication timeout"]] became supported
    3789:20140908:153323.478 item [HOSTA:log[/usr/local/jboss/server/profile2/log/server.log, "Replication timeout"]] became not supported: ZBX_NOTSUPPORTED
    3769:20140908:161249.922 item [HOSTA:log[/usr/local/jboss/server/profile4/log/server.log, "Replication timeout"]] became supported
    3769:20140908:161249.923 item [HOSTA:log[/usr/local/jboss/server/profile1/log/server.log, "Replication timeout"]] became supported
    3789:20140908:161304.939 item [HOSTA:log[/usr/local/jboss/server/profile4/log/server.log, "Replication timeout"]] became not supported: ZBX_NOTSUPPORTED
    3789:20140908:161304.940 item [HOSTA:log[/usr/local/jboss/server/profile1/log/server.log, "Replication timeout"]] became not supported: ZBX_NOTSUPPORTED
    3772:20140908:161314.952 item [HOSTA:log[/usr/local/jboss/server/profile1/log/server.log, "Replication timeout"]] became supported
    3784:20140908:161324.969 item [HOSTA:log[/usr/local/jboss/server/profile1/log/server.log, "Replication timeout"]] became not supported: ZBX_NOTSUPPORTED
    Last edited by gentunian; 08-09-2014, 21:32.

    Comment

    • gentunian
      Junior Member
      • Apr 2014
      • 6

      #3
      [SOLVED] Active checks empty list from server

      It turns out that the template was applied to a bunch of servers that forms a cluster.

      Those servers were cloned. Some of those, didn't have the configuration parameter: Hostname changed.

      So, after hours and hours of debugging and working with emmanux we find a log in a HOSTX that received the active checks for HOSTA.

      Finally, I've found 11 hosts misconfigured with Hostname=HOSTA...

      No easy to find, as the host configuration was ok. It's an interesting thing to note. Everything in the host was well configured. From file access to agent config. But other hosts were misconfigured!

      Thanks emmanux for your time and support!

      Comment

      Working...