2 Minute bandwidth chart - not collecting 2 minutes of data
-
Server
- FOG Version: 1.3.0 RC-14
- OS: CentOS 7 fully updated
Description
The 2 minute bandwidth chart doesn’t collect 2 minutes of data. The data comes in each second (it’s set to 1 second), and just blows by on the graph super fast without being collected up to the 2 minute mark.
10 minutes, 30 minutes, and 1 hour seem to work as expected.
-
This stopped happening.
Apparently it only happens when the main server is on RC-14, and other storage nodes are on RC-8 and some of them are in the process of going to RC-14.
-
It also appears that the bandwidth chart is not respecting the bandwidth chart frequency limiter in FOG Settings.
-
And the bandwidth chart not collecting 2 minutes of data seems intermittent.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
@Wayne-Workman I’m not seeing the problem so far. It appears to be collecting the right amount of data without any major issues. I don’t know what you mean it just blows past.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Tom-Elliott If there was a blip on the bandwidth chart, it scrolls by in about 5 seconds and disappeared into the abyss of the left side of the chart, instead of being collected in the 2 minute display.
-
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
@Wayne-Workman So I took a look and it’s due to the error of the ndoe being down.
This is now fixed in latest.
-
We’re on RC-18 now, and I’ve confirmed this issue is still present.
It appears the 2-minute bandwidth chart is only collecting and displaying about 8 seconds worth of information, exactly as the video I posted shows.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
@Wayne-Workman This doesn’t make sense. Considering when I’ve tested, I’ve purposely disabled one or both nodes that i have associated and am not seeing the issue.
Can you try a Hard refresh first? (CTRL + F5 or SHIFT + F% or CTRL + SHIFT + F5)
-
Ctrl + F5 forced the page to reload, the but the problem persisted. Ctrl + shift + F5 doesn’t seem to do anything, at least on my computer. I’m using Chrome at the moment.
-
@Wayne-Workman Since you’re using Chrome, check out http://superuser.com/questions/220179/how-can-i-do-a-cache-refresh-in-google-chrome/512833#512833
-
The F12 thing didn’t work for me. Ctrl + F5 seems to work.
I probably should have said this earlier but,
at my building, we have a stand-alone fog server. The bandwidth chart for it works perfectly as expected.
At our administration center, we have a large fog setup. The main server has two storage nodes defined for it, and there are 14 other storage nodes that are elsewhere but managed by this main server. Only one of the main server’s storage nodes is “graph enabled”. All other remote storage nodes have their graphs disabled. This is the system with the graph issue.
