Ad Widget

Collapse

zabbix central node show very wrong and different graph from child node

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jing
    Junior Member
    • Oct 2010
    • 9

    #1

    zabbix central node show very wrong and different graph from child node

    I have a weird problem. I’m not sure it’s a bug of zabbix 1.8.3 or not. In my environment there are two zabbix child nodes and a zabbix central root node. they are all 1.8.3 version. I created graphs in the child node and I can see it in the central node. if I want to see a graph in one day duration, fine, they are all correct in both child node and central root node. But unfortunately, if I want to see the graph in a week or a month duration, some of them didn’t show correctly in the central root node. they are very different from each other. In the central root node the graph seems absolutely ridiculous.
    In child node:
    [IMG]C:\Documents and Settings\jfang\Desktop\child node graph.jpg[/IMG]
    In central root node:
    [IMG]C:\Documents and Settings\jfang\Desktop\root node graph.jpg[/IMG]
    Then I tied to review the raw data in database, so I check the same item history table data in two nodes
    In child node:
    mysql> select * from history_uint where itemid='1101100000038938' limit 10;
    +------------------+------------+--------+
    | itemid | clock | value |
    +------------------+------------+--------+
    | 1101100000038938 | 1292314959 | 425216 |
    | 1101100000038938 | 1292315019 | 344304 |
    | 1101100000038938 | 1292315078 | 352744 |
    | 1101100000038938 | 1292315140 | 301440 |
    | 1101100000038938 | 1292315199 | 293400 |
    | 1101100000038938 | 1292315258 | 311288 |
    | 1101100000038938 | 1292315321 | 348552 |
    | 1101100000038938 | 1292315378 | 304984 |
    | 1101100000038938 | 1292315440 | 254312 |
    | 1101100000038938 | 1292315498 | 205656 |
    +------------------+------------+--------+
    10 rows in set (0.06 sec)

    mysql> select * from trends_uint where itemid='1101100000038938' limit 10;
    +------------------+------------+-----+-----------+-----------+-----------+
    | itemid | clock | num | value_min | value_avg | value_max |
    +------------------+------------+-----+-----------+-----------+-----------+
    | 1101100000038938 | 1292313600 | 38 | 205656 | 317660 | 425216 |
    | 1101100000038938 | 1292317200 | 60 | 118840 | 261418 | 415752 |
    | 1101100000038938 | 1292320800 | 60 | 50152 | 140950 | 313112 |
    | 1101100000038938 | 1292324400 | 60 | 12728 | 52381 | 97152 |
    | 1101100000038938 | 1292328000 | 60 | 8488 | 44897 | 82904 |
    | 1101100000038938 | 1292331600 | 60 | 2728 | 28631 | 103960 |
    | 1101100000038938 | 1292335200 | 60 | 1296 | 9998 | 35760 |
    | 1101100000038938 | 1292338800 | 60 | 856 | 5704 | 19456 |
    | 1101100000038938 | 1292342400 | 60 | 856 | 863 | 912 |
    | 1101100000038938 | 1292346000 | 60 | 840 | 861 | 912 |
    +------------------+------------+-----+-----------+-----------+-----------+
    10 rows in set (0.00 sec)

    In central root node:
    mysql> select * from history_uint where itemid='1101100000038938' limit 10;
    +------------------+------------+--------+
    | itemid | clock | value |
    +------------------+------------+--------+
    | 1101100000038938 | 1292314959 | 425216 |
    | 1101100000038938 | 1292315019 | 344304 |
    | 1101100000038938 | 1292315078 | 352744 |
    | 1101100000038938 | 1292315140 | 301440 |
    | 1101100000038938 | 1292315199 | 293400 |
    | 1101100000038938 | 1292315258 | 311288 |
    | 1101100000038938 | 1292315321 | 348552 |
    | 1101100000038938 | 1292315378 | 304984 |
    | 1101100000038938 | 1292315440 | 254312 |
    | 1101100000038938 | 1292315498 | 205656 |
    +------------------+------------+--------+
    10 rows in set (0.07 sec)

    mysql> select * from trends_uint where itemid='1101100000038938' limit 10;
    +------------------+------------+-----+-----------+-----------+------------+
    | itemid | clock | num | value_min | value_avg | value_max |
    +------------------+------------+-----+-----------+-----------+------------+
    | 1101100000038938 | 1292313600 | 38 | 0 | 40788 | 1405034 |
    | 1101100000038938 | 1292317200 | 59 | 0 | 94412 | 5044015 |
    | 1101100000038938 | 1292320800 | 60 | 0 | 71722672 | 4294967295 |
    | 1101100000038938 | 1292324400 | 60 | 0 | 2227 | 97550 |
    | 1101100000038938 | 1292328000 | 60 | 0 | 71587431 | 4294967295 |
    | 1101100000038938 | 1292331600 | 60 | 0 | 4515 | 97577 |
    | 1101100000038938 | 1292335200 | 60 | 0 | 4514042 | 270242752 |
    | 1101100000038938 | 1292338800 | 60 | 0 | 10188 | 180845 |
    | 1101100000038938 | 1292342400 | 60 | 0 | 192445 | 9362891 |
    | 1101100000038938 | 1292346000 | 60 | 0 | 129385621 | 7757393920 |
    +------------------+------------+-----+-----------+-----------+------------+
    10 rows in set (0.00 sec)

    As we see, the history data are same. But trends data are different. I guess this is the reason why two nodes show different graph. Can anyone tell me how to solve this problem? Thank you for your help.

    Central node zabbix server program version:
    Zabbix Server v1.8.3 (revision 13093) (29 March 2010)
    Compilation time: Jun 29 2010 15:41:27

    Child node zabbix server program version:
    Zabbix Server v1.8.3 (revision 13093) (29 March 2010)
    Compilation time: Jun 29 2010 16:54:06
  • jing
    Junior Member
    • Oct 2010
    • 9

    #2
    these are two graphs from child node and root node. hope someone can help me.

    Click image for larger version

Name:	child node graph.jpg
Views:	1
Size:	100.7 KB
ID:	309377

    Click image for larger version

Name:	root node graph.jpg
Views:	1
Size:	84.6 KB
ID:	309378

    Comment

    • jing
      Junior Member
      • Oct 2010
      • 9

      #3
      Does anyone can help me?

      Comment

      Working...