Bandwidth chart - and Location plugin
Morning, I’m using trunk 8529 in this case.
Right now we have one site imaging two computers at once. We have the location plugin setup. Every storage node is in it’s own building, and every node is set as a location. Computers in each of the buildings are also assigned their corresponding location.
In Task Management, I can see two hosts running, and I can see they have a location set which matches their building, but the bandwidth chart is reporting that their local storage node is not being used.
1 of 2 possible things is happening.
- The bandwidth chart isn’t writing the correct colors for bandwidth, like the legend colors don’t match the bandwidth line that is drawn.
- The location plugin isn’t working, and these two computers are actually imaging using another building’s storage node.
I’ve solved this for now as the other thread is also reporting as solved since switching to ksort from asort.
I guess I forgot to mention the tool I used to verify the correct node is sending the data.
iftop, available on Debian, Ubuntu, CentOS 7, Fedora, and probably others.
sudo apt-get install iftop -yor
sudo yum install iftop -yor for Fedora
sudo dnf install iftop -y
For monitoring network, run it as:
You’ll get a very nice CLI graphic showing top-talkers, total data sent, rates, and interface rates overall.
@Tom-Elliott Ok then. Long as locations are working properly, I’m not overly concerned - but yeah it is an issue. Moving to bug reports.
I added failsafe yesterday, though I don’t know what version it was that had it. I think what you’re seeing is the “failsafe” acting improperly. It’s not a huge issue and I will try to get to it shortly, but it’s not high on the “to do” list.
I have confirmed that the correct location is indeed sending the data.
It’s the bandwidth chart reporting wrong.
The same location, same tech, is continuing to image his building.
Bandwidth chart keeps showing bandwidth coming from nodes other than the one it’s supposed to be coming from - and not always the same wrong node.