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

    1.3.4 - high cpu load - client login

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    7
    90
    34.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.
    • F
      Florent @Tom Elliott
      last edited by

      @Tom-Elliott
      Thanks for your response (my english is not very good).

      Yes we have high CPU usage since we have deploy the new client (0.11.9) with GPO.

      We have try to modify FOG_CLIENT_CHECKIN_TIME but we think value over 60 seconds are no effects.
      In our client log we see in general a contact server every 60-200 seconds.
      We have more than 1500 clients.

      If the problem is here is it possible to modify checkin time to 15 minutes ?

      Or if the problem is not this where i can find informations for identify in detail the source of the problem ?

      Regards

      Florent
      Bretagne, FRANCE

      1 Reply Last reply Reply Quote 0
      • UWPVIOLATORU
        UWPVIOLATOR @UWPVIOLATOR
        last edited by

        @Florent

        Do you see something like this in your processes on your FOG server?

        We Disabled IMAGEREPLICATORGLOBALENABLED until Tom fixes the image checking in the next RC.

        F 1 Reply Last reply Reply Quote 0
        • F
          Florent @UWPVIOLATOR
          last edited by

          @UWPVIOLATOR
          Just do this on Web interface / fog settings or after restart apache ?

          Florent
          Bretagne, FRANCE

          Tom ElliottT 1 Reply Last reply Reply Quote 0
          • Tom ElliottT
            Tom Elliott @Florent
            last edited by

            @Florent In the GUI.

            FOG Configuration Page->FOG Settings->FOG Linux Service Enabled

            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

            F 1 Reply Last reply Reply Quote 0
            • A
              ablohowiak
              last edited by

              Tom,
              We added back about 75% of our clients and the load has remained stable and UI responsive. I was trying to update to 1.3.5-RC10, but the install failed.

              • Downloading inits, kernels, and the fog client…Failed!

              Feb 28 12:47:24 FogDB systemd[1]: Starting MySQL Community Server…
              Feb 28 12:47:26 FogDB systemd[1]: Started MySQL Community Server.
              mysql: [Warning] Using a password on the command line interface can be insecure.
              ERROR 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: YES)
              mysql: [Warning] Using a password on the command line interface can be insecure.
              ERROR 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: YES)

              At this point there’s basically no fog site in apache. I’m reverting back to my last snapshot.

              1 Reply Last reply Reply Quote 0
              • F
                Florent @Tom Elliott
                last edited by

                @Tom-Elliott Yes imagereplicatorglobalenabled is not checked

                Florent
                Bretagne, FRANCE

                1 Reply Last reply Reply Quote 0
                • F
                  Florent @UWPVIOLATOR
                  last edited by

                  @UWPVIOLATOR said in 1.3.4 - high cpu load - client login:

                  Increased MaxRequestWorkers from 150 to 500 in mpm_prefork_module
                  Hi,
                  Where you have put this parameter because i try in my apache2.conf in prefork module but not valid after i restart apache2

                  Florent
                  Bretagne, FRANCE

                  1 Reply Last reply Reply Quote 0
                  • A
                    ablohowiak
                    last edited by

                    So no improvement with imagereplicatorglobalenabled off?

                    With this issue I’ve increase my client communication up to 30 minutes. I will reduce when I know things have stabilized.

                    In Ubuntu, see which mpm you have enabled. There should only be one in /etc/apache2/mods-enabled. That’s the file you would edit to increase the MaxRequestWorkers. Make a copy of the file before editing.

                    F 1 Reply Last reply Reply Quote 0
                    • F
                      Florent @ablohowiak
                      last edited by

                      @ablohowiak said in 1.3.4 - high cpu load - client login:

                      So no improvement with imagereplicatorglobalenabled off?

                      No 😞

                      With this issue I’ve increase my client communication up to 30 minutes. >I will reduce when I know things have stabilized.

                      Where you have up to 30 minutes your client communication , “checkin time parameter” ?

                      Florent
                      Bretagne, FRANCE

                      1 Reply Last reply Reply Quote 0
                      • A
                        ablohowiak
                        last edited by

                        Yes.
                        0_1488311359134_upload-489b07bb-a854-4310-a7a9-8990ae16e77d

                        F 2 Replies Last reply Reply Quote 0
                        • F
                          Florent @ablohowiak
                          last edited by

                          @ablohowiak
                          Oh very thanks it’s works !
                          I was thinking test this before but maybe not with “imagereplicatorfogenabled” at off.
                          After few minutes cpu is ok.

                          Thanks.

                          Florent
                          Bretagne, FRANCE

                          1 Reply Last reply Reply Quote 0
                          • F
                            Florent @ablohowiak
                            last edited by

                            @ablohowiak @Tom-Elliott

                            Hi,

                            Today it’s better but all the 30 minutes we have pic of 2 minutes.

                            In wiki it’s write (https://wiki.fogproject.org/wiki/index.php?title=FOG_Client😞

                            The frequency of the checkin-time determines how quickly the FOG Client will receive instructions from the FOG Server. If an image deployment is scheduled for a computer that is turned on, with a checkin-time of 60 seconds, means the FOG Client may begin initiating the task anywhere from 0 to 60 seconds + the random staggering time that is added. This same concept would apply to immediate power management tasks, snapin tasks, capture tasks, and so on. Scheduled tasks are not affected by this behavior, and if the target system is on when the scheduled task is to be ran, this will happen on time

                            How it’s possible to modify the random staggering range for spread over 10 minutes for example ?

                            Thanks.

                            Florent
                            Bretagne, FRANCE

                            Wayne WorkmanW 1 Reply Last reply Reply Quote 0
                            • Wayne WorkmanW
                              Wayne Workman @Florent
                              last edited by Wayne Workman

                              @Florent said in 1.3.4 - high cpu load - client login:

                              How it’s possible to modify the random staggering range for spread over 10 minutes for example ?

                              The staggering is not meant to be adjustable, what’s meant to be adjustable is the FOG_CLIENT_CHECKIN_TIME, this governs how often the FOG Client should check with the server. Assuming 10,000 computers power on all at exactly the same moment, over the course of the day the random staggering will cause all clients to spread out evenly with their check-ins. But nobody has 10,000 systems all powering on at the same second. Generally, organizations either A. leave their computers on all the time or B. allow the end-users to power them on.

                              Also asking @Joe-Schmitt if he could give further explanation.

                              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/

                              F 1 Reply Last reply Reply Quote 0
                              • A
                                ablohowiak
                                last edited by

                                1.3.5-RC 10 and working fine.

                                All clients are back on, I’ve already reduced the client check in time, and the load was fine for the start of the school day.

                                The Image replicator service is still off.

                                1 Reply Last reply Reply Quote 2
                                • F
                                  Florent @Wayne Workman
                                  last edited by

                                  @Wayne-Workman
                                  Hi,
                                  Ok i understand.
                                  Actually majority off our classroom reboot at the same time for software update in night (same time is residual effect with green fog on old version).
                                  I will adjust power management (good amelioration in this version) for spread out this reboot.

                                  Thanks.

                                  Florent
                                  Bretagne, FRANCE

                                  1 Reply Last reply Reply Quote 0
                                  • 1
                                  • 2
                                  • 3
                                  • 4
                                  • 5
                                  • 5 / 5
                                  • First post
                                    Last post

                                  142

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project