Ad Widget

Collapse

Distributed Monitoring: Master not getting events

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • wlp1979
    Junior Member
    • Oct 2008
    • 1

    #1

    Distributed Monitoring: Master not getting events

    I have setup a two node distributed monitoring system. We are doing primarily web monitoring of several sites which are hosted on our co-location servers. Each node has a web scenario for each hosted site. Each node also has a trigger setup for each web scenario. The master node has been monitoring the sites for several weeks now and is sending out notifications when something goes wrong. I have just finished installing the node on a VPS.

    In order to test the child node's setup, I changed one of the web scenarios to force a failure. From the master node, I can see the triggers being fired on the child node, but it never shows up as an event. So, the action based on those triggers is never taken. Has anyone had this issue? If so, how did you solve it?

    My hope is to have all notifications come from the master server, and have the notifications only go out if both nodes fail to load the web pages. Is this even possible with zabbix?
  • oneye
    Junior Member
    • May 2008
    • 27

    #2
    I also have similar problem. I have a master node and one child node. I can see that there is a trigger on the child node but the master node has no events regading this trigger and it never does any actions. What's the problem...please help out.

    Regards

    Comment

    • Senator
      Junior Member
      • Feb 2009
      • 9

      #3
      I have same problem. I can reproduce this with version 1.6.2 and 1.6.4. Data and configuration is synchronized as it should be, but no events. When investigating the dashboard - the trigger has an age of 39 years. No actions are done and trigger doesn't appear in 'last 20 issues' window.
      the funny thing at this behaviour is, that we have multiple nodes and we checked configuration of other nodes - seems to be exactly the same. Some nodes report events others not.

      Best Regards
      Tobias

      Comment

      • Senator
        Junior Member
        • Feb 2009
        • 9

        #4
        Solution:

        After further investigation it seems to be a database issue. While comparing the database with other nodes we changed the nextid value of events table to following value
        <nodeid>00<nodeid>0000XXXX as the second <nodeid> was 0.
        After a short test it seems as this node synchronizes events like expected.

        Best Regards
        Tobias

        Comment

        • xs-
          Senior Member
          Zabbix Certified Specialist
          • Dec 2007
          • 393

          #5
          I will try this and report back
          (my post on this: http://www.zabbix.com/forum/showthread.php?t=12226)

          Comment

          • xs-
            Senior Member
            Zabbix Certified Specialist
            • Dec 2007
            • 393

            #6
            Didn't work for me.

            Sync still stops after 3 hours or so. The only log message i can relate to this is: NODE 10: Error while sending data to Node [30] error: ZBX_TCP_WRITE() failed [Connection reset by peer]

            Comment

            Working...