Bandwidth chart not reporting

[Tom Elliott]

not a bug, in the sense that you need to probably check your fogurlrequests file and make the edits to adjust the timeout values.

I don’t know how much delay is the “goldilocks” value yet. I will likely be adding a timeout setting (in milliseconds) to the db for this timeout value to operate against.

[Wayne Workman]

@Tom-Elliott said in Bandwidth chart not reporting:

you need to probably check your fogurlrequests file and make the edits to adjust the timeout values.

I edited /var/www/html/fog/lib/fog/fogurlrequests.class.php and I just added another zero onto private $_timeout = 864000; but it didn’t make a difference. Then I stuck two more zeros onto that and that didn’t make a difference. Then I just set it to zero and that didn’t change anything either.
So I put it back to the original value, 86400.

I’ve changed the below setting to 1, 5, and 10 and it does the same for each.
Web Interface -> FOG Configuration -> FOG Settings -> General Settings -> FOG_BANDWIDTH_TIME

[Tom Elliott]

@Wayne-Workman not that timeout.

The one in the CONNECTTIMEOUT_MS. Those are what need editing. The maintimeout is not what’s causing these things not to display.

[Tom Elliott]

@Wayne-Workman There’s two parts. I just can’t tell you the lines right now.

[Wayne Workman]

Possible similar issue:
https://forums.fogproject.org/topic/8914/activity-dashboard

[Tom Elliott]

Can you repull and try again?

[Wayne Workman]

@Tom-Elliott On svn 6011, still same behavior.

[Tom Elliott]

@Wayne-Workman All nodes are on the same version?

[Wayne Workman]

@Tom-Elliott No… I just updated the main. I figured that’s the one that matters since it’s the only one that has it’s graph enabled.

[Tom Elliott]

@Wayne-Workman Any word?

[Tom Elliott]

Just pushing to top of the list.

[Wayne Workman]

As of RC-23 this is partially fixed. The graph now collects 2 minutes of data on the 2 minute tab, however the main server in the bandwidth chart still isn’t reporting the interface name beside the node name like it should.

[Wayne Workman]

Ok, so the interface name wasn’t showing because somehow it was wrong in the storage node’s settings.

I never changed that… so that’s probably something broken with the auto-registering auto-correcting stuff @Tom-Elliott