Bug #7656
closed
TypeError: n is undefined JavaScript error in status_monitoring.php
0%
Description
I'm using 2.3.4-RELEASE (i386) and when I open the Staus->Monitoring page, I get a JavaScript error (below). It appears that on line 1087 of status_monitoring.php, when determining the timeFormat, the step property of the first data element is used. In my case it is 1800, which is not in the timeLookup dictionary. By adding an entry for "1800" to the timeLookup dictionary on line 490, I can get the page to render correctly.
TypeError: n is undefined
t()d3.min.js:1
draw_graph/Co.text/<()d3.min.js:3
Co.each/<()d3.min.js:3
Y()d3.min.js:1
Co.each()d3.min.js:3
Co.text()d3.min.js:3
n/<()d3.min.js:5
Yl.each/<()d3.min.js:5
Y()d3.min.js:1
Yl.each()d3.min.js:5
n()d3.min.js:5
Co.call()d3.min.js:3
chart/<()nv.d3.js:1628
Yl.each/<()d3.min.js:5
Y()d3.min.js:1
Yl.each()d3.min.js:5
chart()nv.d3.js:1612
Co.call()d3.min.js:3
chart/<()nv.d3.js:9571
Yl.each/<()d3.min.js:5
Y()d3.min.js:1
Yl.each()d3.min.js:5
chart()nv.d3.js:9379
Co.call()d3.min.js:3
draw_graph/render/renderLoop()nv.d3.js:99
1d3.min.js:1:14696
Updated by Jim Pingle over 4 years ago
- Status changed from New to Closed
Old report and no recent recurrences (plus I can't reproduce it). Lots of things in this area have changed, so most likely it's either fixed no longer relevant.
Updated by Shaun Currier almost 4 years ago
I believe this is related to my issue here that I can reliably reproduce in 2.4.5-RELEASE-p1.
Updated by Shaun Currier almost 4 years ago
I root caused this pretty far as described in this post:
https://forum.netgate.com/post/926097
The step property ultimately comes from the RRD file itself. It seems values that were not anticipated are possible.