• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Bandwidth chart - and Location plugin

Scheduled Pinned Locked Moved Solved
Bug Reports
2
7
1.6k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W
    Wayne Workman
    last edited by Jul 13, 2016, 2:15 PM

    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.

    1. The bandwidth chart isn’t writing the correct colors for bandwidth, like the legend colors don’t match the bandwidth line that is drawn.
    2. The location plugin isn’t working, and these two computers are actually imaging using another building’s storage node.

    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/

    1 Reply Last reply Reply Quote 0
    • W
      Wayne Workman
      last edited by Jul 13, 2016, 4:55 PM

      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.

      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/

      1 Reply Last reply Reply Quote 0
      • W
        Wayne Workman
        last edited by Jul 13, 2016, 4:59 PM

        I have confirmed that the correct location is indeed sending the data.

        It’s the bandwidth chart reporting wrong.

        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/

        1 Reply Last reply Reply Quote 1
        • T
          Tom Elliott
          last edited by Jul 13, 2016, 5:01 PM

          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.

          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

          W 1 Reply Last reply Jul 13, 2016, 5:02 PM Reply Quote 0
          • W
            Wayne Workman @Tom Elliott
            last edited by Jul 13, 2016, 5:02 PM

            @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.

            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/

            1 Reply Last reply Reply Quote 0
            • W
              Wayne Workman
              last edited by Wayne Workman Jul 13, 2016, 9:32 PM Jul 14, 2016, 3:30 AM

              I guess I forgot to mention the tool I used to verify the correct node is sending the data.

              It’s called iftop, available on Debian, Ubuntu, CentOS 7, Fedora, and probably others.

              Install as:
              sudo apt-get install iftop -y or sudo yum install iftop -y or for Fedora sudo dnf install iftop -y

              For monitoring network, run it as:
              iftop -n

              You’ll get a very nice CLI graphic showing top-talkers, total data sent, rates, and interface rates overall.

              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/

              1 Reply Last reply Reply Quote 0
              • T
                Tom Elliott
                last edited by Jul 14, 2016, 5:52 PM

                I’ve solved this for now as the other thread is also reporting as solved since switching to ksort from asort.

                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

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                1 / 1
                • First post
                  6/7
                  Last post

                219

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project