Ad Widget

Collapse

Zabbix 1.6.4 Missing nodes in drop down

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • side_control
    Member
    • Mar 2008
    • 37

    #1

    Zabbix 1.6.4 Missing nodes in drop down

    I have 1 master node and 2 child nodes. Two nodes are working flawlessly but the third node refuses to show up in the drop down on the master node.

    MASTER NODE:
    Code:
    mysql> SELECT * FROM nodes;
    +--------+------------+----------+---------------+-------+---------------+--------------+----------+----------+
    | nodeid | name       | timezone | ip            | port  | slave_history | slave_trends | nodetype | masterid |
    +--------+------------+----------+---------------+-------+---------------+--------------+----------+----------+
    |      1 | Jawbrkr  |       -5 | X.X.X.X | 10052 |            15 |           15 |        1 |        0 |
    |      2 | Production |       -5 | X.X.X.X | 10051 |            15 |           15 |        0 |        1 |
    |      3 | Sandbox    |       -5 | X.X.X.X | 10051 |            15 |           15 |        0 |        1 |
    +--------+------------+----------+---------------+-------+---------------+--------------+----------+----------+
    3 rows in set (0.00 sec)
    The problem is node 3,

    Below is the same SQL query on both child nodes.

    Code:
    mysql> select * from nodes;
    +--------+-----------+----------+---------------+-------+---------------+--------------+----------+----------+
    | nodeid | name      | timezone | ip            | port  | slave_history | slave_trends | nodetype | masterid |
    +--------+-----------+----------+---------------+-------+---------------+--------------+----------+----------+
    |      1 | Jawbrkr |       -5 | X.X.X.X | 10052 |            15 |           15 |        0 |        0 |
    |      3 | Sandbox   |       -5 | X.X.X.X | 10051 |            15 |           15 |        1 |        1 |
    +--------+-----------+----------+---------------+-------+---------------+--------------+----------+----------+
    2 rows in set (0.00 sec)
    Code:
    mysql> select * from nodes;
    +--------+------------+----------+---------------+-------+---------------+--------------+----------+----------+
    | nodeid | name       | timezone | ip            | port  | slave_history | slave_trends | nodetype | masterid |
    +--------+------------+----------+---------------+-------+---------------+--------------+----------+----------+
    |      1 | Jawbrkr  |       -5 | X.X.X.X | 10052 |            15 |           15 |        0 |        0 |
    |      2 | Production |       -5 | X.X.X.X | 10051 |            15 |           15 |        1 |        1 |
    +--------+------------+----------+---------------+-------+---------------+--------------+----------+----------+
    2 rows in set (0.00 sec)
    Below are the logs of the nodes communicating.

    MASTER NODE
    Code:
    zabbix_server.log:  2720:20090414:211437 NODE 1: Received history from node 2 for node 2 datalen 352511
    zabbix_server.log:  2721:20090414:211504 NODE 1: Received history_uint from node 2 for node 2 datalen 336593
    zabbix_server.log:  2719:20090414:211529 NODE 1: Received history_str from node 2 for node 2 datalen 1416
    zabbix_server.log:  2719:20090414:211530 NODE 1: Received events from node 2 for node 2 datalen 69
    zabbix_server.log:  2723:20090414:211531 NODE 1: Received alerts from node 2 for node 2 datalen 868
    zabbix_server.log:  2721:20090414:211533 NODE 1: Received history from node 2 for node 2 datalen 352924
    zabbix_server.log:  6172:20090414:211555 NODE 1: Received history from node 2 for node 2 datalen 352924
    zabbix_server.log:  6170:20090414:211556 NODE 1: Received history from node 3 for node 3 datalen 344392
    zabbix_server.log:  6173:20090414:211657 NODE 1: Received history_uint from node 3 for node 3 datalen 337228
    zabbix_server.log:  6174:20090414:211719 NODE 1: Received history_uint from node 2 for node 2 datalen 336595
    zabbix_server.log:  6171:20090414:211720 NODE 1: Received history_str from node 3 for node 3 datalen 3108
    zabbix_server.log:  6172:20090414:211722 NODE 1: Received auditlog from node 3 for node 3 datalen 278
    zabbix_server.log:  6171:20090414:211745 NODE 1: Received data from slave node 3 for node 3 datalen 4119999
    zabbix_server.log:  6172:20090414:211913 NODE 1: Received history_str from node 2 for node 2 datalen 1114
    zabbix_server.log:  6172:20090414:211915 NODE 1: Received events from node 2 for node 2 datalen 171
    zabbix_server.log:  6174:20090414:212521 NODE 1: Received data from slave node 2 for node 2 datalen 13207
    zabbix_server.log:  6170:20090414:212526 NODE 1: Received alerts from node 2 for node 2 datalen 7120
    zabbix_server.log:  6172:20090414:212528 NODE 1: Received history from node 2 for node 2 datalen 352416
    zabbix_server.log:  6174:20090414:212633 NODE 1: Received history_uint from node 2 for node 2 datalen 336664
    zabbix_server.log:  6172:20090414:212742 NODE 1: Received history_str from node 2 for node 2 datalen 3712
    zabbix_server.log:  6172:20090414:212744 NODE 1: Received events from node 2 for node 2 datalen 120
    zabbix_server.log:  6173:20090414:212754 NODE 1: Received data from slave node 2 for node 2 datalen 13207
    zabbix_server.log:  6174:20090414:212808 NODE 1: Received history from node 2 for node 2 datalen 351915
    NODE 3 (PROBLEM NODE)
    Code:
    zabbix_server.log: 12991:20090414:165821 NODE 3: Sending history_sync of node 3 to node 1 datalen 748
    zabbix_server.log: 12991:20090414:165823 NODE 3: Sending history_uint_sync of node 3 to node 1 datalen 595
    zabbix_server.log: 12991:20090414:165832 NODE 3: Sending history_sync of node 3 to node 1 datalen 678
    zabbix_server.log: 12991:20090414:165833 NODE 3: Sending history_uint_sync of node 3 to node 1 datalen 521
    zabbix_server.log: 12991:20090414:165842 NODE 3: Sending history_sync of node 3 to node 1 datalen 748
    zabbix_server.log: 12991:20090414:165842 NODE 3: Sending history_uint_sync of node 3 to node 1 datalen 366
    zabbix_server.log: 12991:20090414:165852 NODE 3: Sending history_sync of node 3 to node 1 datalen 749
    zabbix_server.log: 12991:20090414:165852 NODE 3: Sending history_uint_sync of node 3 to node 1 datalen 590
    zabbix_server.log: 12991:20090414:165901 NODE 3: Sending history_sync of node 3 to node 1 datalen 679
    zabbix_server.log: 12991:20090414:165903 NODE 3: Sending history_uint_sync of node 3 to node 1 datalen 571
    zabbix_server.log: 12991:20090414:165911 NODE 3: Sending history_sync of node 3 to node 1 datalen 678
    zabbix_server.log: 12991:20090414:165911 NODE 3: Sending history_uint_sync of node 3 to node 1 datalen 395
    zabbix_server.log: 12991:20090414:165926 NODE 3: Sending configuration changes to master node 1 for node 3 datalen 4219140
    zabbix_server.log: 12991:20090414:170433 NODE 3: Sending history_sync of node 3 to node 1 datalen 22495
    zabbix_server.log: 12991:20090414:170436 NODE 3: Sending history_uint_sync of node 3 to node 1 datalen 15444
    zabbix_server.log: 12991:20090414:170455 NODE 3: Sending configuration changes to master node 1 for node 3 datalen 4219140
    zabbix_server.log: 15923:20090414:211410 NODE 3: Sending configuration changes to master node 1 for node 3 datalen 4120000
    NODE 2 (Good node)
    Code:
    zabbix_server.log.old:  2248:20090414:174302 NODE 2: Sending history_uint_sync of node 2 to node 1 datalen 336531
    zabbix_server.log.old:  2248:20090414:174438 NODE 2: Sending history_str_sync of node 2 to node 1 datalen 1944
    zabbix_server.log.old:  2248:20090414:174534 NODE 2: Sending configuration changes to master node 1 for node 2 datalen 45921
    zabbix_server.log.old:  2248:20090414:174548 NODE 2: Sending alerts of node 2 to node 1 datalen 756
    zabbix_server.log.old:  2248:20090414:174553 NODE 2: Sending history_sync of node 2 to node 1 datalen 352486
    zabbix_server.log.old:  2248:20090414:174729 NODE 2: Sending history_uint_sync of node 2 to node 1 datalen 336605
    zabbix_server.log.old:  2248:20090414:174902 NODE 2: Sending history_str_sync of node 2 to node 1 datalen 1856
    zabbix_server.log.old:  2248:20090414:174904 NODE 2: Sending events of node 2 to node 1 datalen 120
    zabbix_server.log.old:  2248:20090414:174938 NODE 2: Sending configuration changes to master node 1 for node 2 datalen 45921
    zabbix_server.log.old:  2248:20090414:174955 NODE 2: Sending alerts of node 2 to node 1 datalen 1678
    zabbix_server.log.old:  2248:20090414:174957 NODE 2: Sending history_sync of node 2 to node 1 datalen 352940
    zabbix_server.log.old:  2248:20090414:175115 NODE 2: Sending history_uint_sync of node 2 to node 1 datalen 336381
    zabbix_server.log.old:  2248:20090414:175257 NODE 2: Sending history_str_sync of node 2 to node 1 datalen 1750
    zabbix_server.log.old:  2248:20090414:175258 NODE 2: Sending events of node 2 to node 1 datalen 120
    zabbix_server.log.old:  2248:20090414:175401 NODE 2: Sending configuration changes to master node 1 for node 2 datalen 45941
    zabbix_server.log.old:  2248:20090414:182459 NODE 2: Received data from master node 1 for node 2 datalen 1415
    zabbix_server.log.old:  2248:20090414:182614 NODE 2: Sending alerts of node 2 to node 1 datalen 19002
    zabbix_server.log.old:  2248:20090414:182621 NODE 2: Sending history_sync of node 2 to node 1 datalen 352349
    zabbix_server.log.old:  2248:20090414:182648 NODE 2: Sending history_uint_sync of node 2 to node 1 datalen 336684
    zabbix_server.log.old:  2248:20090414:182711 NODE 2: Sending history_str_sync of node 2 to node 1 datalen 14528
    And here is a screenshot of the missing node. I apologize for everything being blacked out but it's a company policy. If you look at the drop down in the url, you'll find that the node drop is blacked out but it's the same value 'Jawbrkr' aka master node.

    warning 1920x1200 picture.


    any suggestion or advice would be very helpful, thank you for your time.
  • Aly
    ZABBIX developer
    • May 2007
    • 1126

    #2
    You should look to this thread http://www.zabbix.com/forum/showthread.php?t=12180
    Zabbix | ex GUI developer

    Comment

    Working...