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

    Web GUI error after clicking List Hosts

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    25
    4.4k
    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.
    • T
      tesparza @george1421
      last edited by

      @george1421 process.PNG

      2000 + clients

      Interval checkin time it 60 seconds

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @tesparza
        last edited by george1421

        @tesparza For testing lets change the check in interval to 300 seconds (5 minutes) and then lets wait 15 minutes to see if things settle down. This isn’t the answer at the moment, its just to see if having 2000 hosts hit (if we lineralize it, 34 per second) is a bit too much for your hardware.

        The screen shot you shown is indicative of what a myisam engine configuration will give us. We know we already fixed that.

        Looking at top, it also appears you only have 4GB of ram. Can you do a uname -a and post the results here?

        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!

        T 1 Reply Last reply Reply Quote 0
        • T
          tesparza @george1421
          last edited by

          @george1421 Okay interval changed to 300

          uname.PNG

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @tesparza
            last edited by george1421

            @tesparza well that’s a good thing you have a 64 bit OS. Since you are telling me 8GB is installed but top is reporting only 4GB then I was thinking a 32 bit OS.

            If the 300 second check in doesn’t settle things down, then please confirm you have 8GB installed. Since is a 7010 you might be able to find some old memory to top it out at 16GB. I know I have at least 10 sticks of 4GB 7010 memory in the bottom of my junk bin. I’m hoping you have similar.

            Again when things settle down a bit we’ll check also disk performance. Right now the sql sever is having a high cpu load. This could be either disk, or not enough free ram for caching to happen. We need to make small changes to see where things pick up the most.

            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!

            T 1 Reply Last reply Reply Quote 0
            • T
              tesparza @george1421
              last edited by

              @george1421 Okay it seems to be running smoother, I will add more RAM, eventually I will transfer to a server.

              george1421G 1 Reply Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @tesparza
                last edited by

                @tesparza I made a post a few years ago to test different hardware and its impact on imaging speed. We may need to reference it as we work through this.

                https://forums.fogproject.org/topic/10459/can-you-make-fog-imaging-go-fast

                If your fog server has a sata spinning hard drive that may also be the culprit. But again testing will show us.

                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!

                T 1 Reply Last reply Reply Quote 1
                • T
                  tesparza @george1421
                  last edited by

                  @george1421 Okay I have upgraded the RAM to 16gb. Will see how it goes. Thank you.

                  george1421G 1 Reply Last reply Reply Quote 0
                  • george1421G
                    george1421 Moderator @tesparza
                    last edited by

                    @tesparza Did you have 4GB in there when you opened the machine? Does top now show 16GB of ram? I’m kind of interested in why things were reporting as they were.

                    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!

                    T 1 Reply Last reply Reply Quote 0
                    • T
                      tesparza @george1421
                      last edited by

                      @george1421 16gb.PNG

                      Running smooth so far. Yes it had 4GB before.

                      george1421G 1 Reply Last reply Reply Quote 0
                      • george1421G
                        george1421 Moderator @tesparza
                        last edited by

                        @tesparza Its good we can point our finger at low memory as the problem. The small cache space on 4GB is only left 800MB of room so mysql had to commit everything to disk instead of caching it for later. (speculation) I did find it surprising that in the previous top screen shot, you had 4GB of swap space but none was used even when the system was low on ram. It wouldn’t have really helped in your case, but I find it strange that no swap space was used.

                        Now that you found an acceptable level you can start decreasing your fog client check in time till you find a happy balance between speed and frequency. The only issue I can think of by keeping the check in time to 5 minutes would be during post imaging if the fog client was used to rename the system, connect to AD, or do a scheduled reboot. Its possible the client computer wouldn’t react to the command for about 5 minutes.

                        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!

                        T 1 Reply Last reply Reply Quote 1
                        • T
                          tesparza @george1421
                          last edited by

                          This post is deleted!
                          1 Reply Last reply Reply Quote 0
                          • 1
                          • 2
                          • 2 / 2
                          • First post
                            Last post

                          185

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project