Version-2.2.3 still have insues under DM mode

XMLWordPrintable

    • Type: Incident report
    • Resolution: Won't fix
    • Priority: Major
    • None
    • Affects Version/s: 2.2.3
    • Component/s: Server (S)
    • None
    • Environment:
      CentOS 6.4 X64

      Hi guys,
      I have a monitor system with zabbix 2.2.1 running well about 1 year.
      Then this May,we've decided to deploy a distributed monitor system with 7 nodes,with a node 199 as master and nodes 11/12/13/14/15/16 as childs.
      This system running without problem over 2 weeks,now it has a little issues.

      When a trigger was trigged,the frontend of the master node can receive the issue and displayed on dashborad.But when Im trying to check events history by clicking the events menu,there is nothing.
      After checking out all of the child nodes,I found that just node 13 and node 16 got that problem,by checking the log file with command tail -f /var/log/zabbix/zabbix_server.log,Ive got these messages on my screen:
      1733:20140627:215257.630 NODE 16: sending configuration changes to master node 199 for node 16 datalen 10
      1733:20140627:215300.612 NODE 16: Received configuration changes from master node 199 for node 16 datalen 11
      1733:20140627:215300.926 NODE 16: sending history_sync of node 16 to node 199 datalen 32868
      1733:20140627:215302.095 NODE 16: sending history_uint_sync of node 16 to node 199 datalen 10931
      1733:20140627:215302.740 NODE 16: sending events of node 16 to node 199 datalen 36741
      1733:20140627:215302.795 NOT OK
      1733:20140627:215305.827 NODE 16: sending history_sync of node 16 to node 199 datalen 30081
      1733:20140627:215306.636 NODE 16: sending events of node 16 to node 199 datalen 36741
      1733:20140627:215306.638 NOT OK
      1733:20140627:215315.654 NODE 16: sending history_sync of node 16 to node 199 datalen 33111
      1733:20140627:215316.600 NODE 16: sending history_uint_sync of node 16 to node 199 datalen 1231
      1733:20140627:215316.620 NODE 16: sending events of node 16 to node 199 datalen 36741
      1733:20140627:215316.621 NOT OK
      1723:20140627:215320.472 cannot send list of active checks to [127.0.0.1]: host [Zabbix server] not monitored
      1733:20140627:215325.635 NODE 16: sending history_sync of node 16 to node 199 datalen 9216
      1733:20140627:215325.810 NODE 16: sending history_uint_sync of node 16 to node 199 datalen 2911
      1733:20140627:215325.939 NODE 16: sending events of node 16 to node 199 datalen 36741
      1733:20140627:215325.941 NOT OK
      1733:20140627:215335.953 NODE 16: sending history_sync of node 16 to node 199 datalen 52197
      1733:20140627:215336.967 NODE 16: sending history_uint_sync of node 16 to node 199 datalen 9923
      1733:20140627:215337.303 NODE 16: sending events of node 16 to node 199 datalen 36741
      1733:20140627:215337.305 NOT OK

      And then,I googled this message and found a solution here:
      https://support.zabbix.com/browse/ZBX-7452

      this tips said that there's a patch for the issues,but when I was trying to apply the patch on my child nodes,I found that there's no such file"./src/zabbix_server/trapper/nodehistory.c",My zabbix was installed by command "yum install" from a rpm package,so there's not any source code on my server for this patch to patch it.

      Up to now,I still have no idea to fix that problem,that's why I'm asking for help here.
      BTW:I've just realized zabbix 2.4 has removed node mode,it means that the official team knows about this bug,so ,what the fxxx......

            Assignee:
            Unassigned
            Reporter:
            Derek Chow
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: