[ZBX-6416] Exception problems on Javascript related to node ID and MAPS Created: 2013 Mar 20  Updated: 2017 May 30  Resolved: 2013 Sep 19

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 2.0.4, 2.0.5, 2.0.6rc1
Fix Version/s: None

Type: Incident report Priority: Blocker
Reporter: Adail Horst Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: distributed, javascript, links, maps
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentoS 5.8 or Debian 6

Attachments: PNG File bug_mapas.png     XML File test_bug_link_map.xml    
Issue Links:
Duplicate
duplicates ZBX-6993 Is not possible link Template with ho... Closed

 Description   

Steps to reproduce the error:
1) Configure the zabbix with nodeid bigger than 100 (in my lab I test with node ID 101, 102, 121, 998)
2) Create a MAP with many links between hosts (in my lab I test with 5 hosts and 6 links)
3) Save and close the map
4) Open the map
5) Try to edit a link
The edition not works with message (on browser console):
"TypeError: that.links[that.currentLinkId] is undefined
var linkData = that.links[that.currentLinkId].getData();
" (on line 507 of - /jsLoader.php?ver=2.0.6rc1&lang=en_US&showGuiMessaging=1&files[]=class.cmap.js&files[]=class.cviewswitcher.js&files[]=servercheck.js

We test this in 6 zabbix servers.
In 4 of this servers apear the same problem, in 2 not apear.
The 2 "box" without problems have Low NodeID (2 and 11)

I will attach the screenshot and XML for tests.

We test using Chrome and Firefox and Windows and Linux.

 Comments   
Comment by richlv [ 2013 Mar 20 ]

might be related to ZBX-6402

Comment by Oleksii Zagorskyi [ 2013 Mar 21 ]

See also ZBX-6318. Reporter is the same.

Comment by Ivo Kurzemnieks [ 2013 Sep 19 ]

There is an issue with jQuery that incorrecly gets high value IDs. This problem exists in few other places and will be fixed under ZBX-6993 in ZABBIX 2.2.
Closing this as duplicate.

Generated at Fri Mar 14 17:08:17 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.