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

Around 100% cpu usage constantly

Scheduled Pinned Locked Moved Solved
Linux Problems
6
25
8.2k
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.
  • X
    x23piracy
    last edited by May 29, 2016, 2:45 PM

    @Tom-Elliott even if i try to run the script via sudo bash -c ‘script.sh’ high load still remains, that doesn’t fix it. and the problem wasnt there with older trunk versions.

    ║▌║█║▌│║▌║▌█

    T 1 Reply Last reply May 29, 2016, 2:46 PM Reply Quote 0
    • T
      Tom Elliott @x23piracy
      last edited by May 29, 2016, 2:46 PM

      @x23piracy The code that’s running the 100% cpu hasn’t changed.

      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

      X 1 Reply Last reply May 29, 2016, 2:54 PM Reply Quote 0
      • X
        x23piracy @Tom Elliott
        last edited by x23piracy May 29, 2016, 9:14 AM May 29, 2016, 2:54 PM

        @Tom-Elliott what should i do i cannot get away from the cpu burning. Any suggestions?
        Also i cannot use systemctl like you suggested for 14.04:

        root@fog-image:/home/fog# systemctl stop FOGMulticastManager
        systemctl: Befehl nicht gefunden.
        

        Ubuntu 14.04 uses Upstart as the init system, the plan to switch to systemd is planned for 14.10+. There are parts of “systemd” that have been used in Ubuntu for a long time, but for most intents and purposes when people say “systemd” they mean systemd-as-init.

        And it burns for me can someone borrow a fire extinguisher? It’s hot here 🙂

        Regards X23

        ║▌║█║▌│║▌║▌█

        W 1 Reply Last reply May 29, 2016, 6:18 PM Reply Quote 0
        • C
          coco65 @Tom Elliott
          last edited by May 29, 2016, 5:50 PM

          @Tom-Elliott - I got tired of sudo so enabled root login. Does sudo -i make any difference then? Tried it.
          0_1464544102361_2016-05-29_19-44-27.jpg
          0_1464544113171_2016-05-29_19-45-18.jpg

          1 Reply Last reply Reply Quote 0
          • T
            Tom Elliott
            last edited by May 29, 2016, 6:03 PM

            I need solid proof if possible.

            If you can find a revision where all is working properly and when it stops, I can probably be of more help.

            Seeing as this seems a sporadic thing and only, to me, seems to appear on Debian based OS’s, I can guess maybe it’s got something to do with the session crontab?

            Just a guess.

            I haven’t made a change to the fog services that would cause this to sporadically occur.

            Normally, when I do see the issue, it’s stuck in a forever loop (the services). This happens when it fails to read data from the database and get’s a 0 data.

            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
            • W
              Wayne Workman @x23piracy
              last edited by May 29, 2016, 6:18 PM

              @x23piracy If you have time, I can find out exactly what’s happening via TeamViewer and make a bug report afterwards.

              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/

              X 1 Reply Last reply May 29, 2016, 7:33 PM Reply Quote 0
              • X
                x23piracy
                last edited by x23piracy May 29, 2016, 12:57 PM May 29, 2016, 6:35 PM

                @Tom-Elliott got it fixed, it’s embarrassing for myself, mysql wasn’t rechable outside 127.0.0.1, some automatic installed security patch (i have this enabled) must caused it (it worked before) i changed the bind in my.cnf away from 127.0.0.1 to 0.0.0.0 you can also use machines current ip address on eth you are using. 0.0.0.0 binds to every network device.

                No need for any postprocessing script

                Just an idea, the installer could check the bind address while installing/updating and warn if bind is 127.0.0.1 or localhost.

                EDIT:

                Not fully solved my fog master is now burning, maybe 0.0.0.0 is not making it reachable to 127.0.0.1 (localhost)… i get back
                ok that was not the problem, 0.0.0.0 really binds all access worked via mysql client, so i restarted services on the fog master with the script and it worked, i will try reboots and so on…

                Regards X23

                ║▌║█║▌│║▌║▌█

                1 Reply Last reply Reply Quote 0
                • X
                  x23piracy @Wayne Workman
                  last edited by x23piracy May 29, 2016, 1:35 PM May 29, 2016, 7:33 PM

                  @Wayne-Workman ok we can do this later

                  i did the following and it helped.
                  to installfog.sh at last line i added a call to restart_services.sh
                  additionally i added (as root) to cron (crontab -e) a call to restart_services.sh, use @reboot in front if the crontab line.

                  Regards X23

                  ║▌║█║▌│║▌║▌█

                  1 Reply Last reply Reply Quote 1
                  • X
                    x23piracy
                    last edited by x23piracy May 30, 2016, 3:00 AM May 30, 2016, 8:52 AM

                    Hi, after thinking it is fixed, i found this that morning:

                    alt text

                    Now the Multicast Service is burning like hell.
                    After another service restart via script it’s silent again, i will report back tomorrow morning if the hell comes back.

                    Regards X23

                    ║▌║█║▌│║▌║▌█

                    T 1 Reply Last reply May 30, 2016, 1:43 PM Reply Quote 0
                    • T
                      Tom Elliott @x23piracy
                      last edited by May 30, 2016, 1:43 PM

                      @x23piracy just a guess that this goes crazy when updating.

                      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 May 30, 2016, 6:40 PM Reply Quote 0
                      • F
                        fry_p Moderator @Tom Elliott
                        last edited by May 30, 2016, 6:40 PM

                        @Tom-Elliott said in Around 100% cpu usage constantly:

                        @x23piracy just a guess that this goes crazy when updating.

                        That’s the case for me.

                        Like open source community computing? Why not do it for a good cause?
                        Use your computer/server for humanitarian projects when it is idle!
                        https://join.worldcommunitygrid.org?recruiterId=1026912

                        1 Reply Last reply Reply Quote 0
                        • T
                          Tom Elliott
                          last edited by May 31, 2016, 11:15 AM

                          I’ve added some code in hopes to prevent runaway services such as this. With any luck the 100% cpu do to FOG services will be no more.

                          The Defaults, in case of issues:

                          FOGImageReplicator = 600 seconds (10 Minutes)
                          FOGSnapinReplicator = 600 seconds (10 Minutes)
                          FOGPingHosts = 300 seconds (5 Minutes)
                          FOGScheduler = 60 seconds (1 Minute)
                          FOGMulticastManager = 10 seconds
                          

                          The writing to log files isn’t as important as the timing. It’s the timing that’s causing the run away CPU cycles as they’re running infinitely. Without a sleep to slow it all down, the services will keep doing work without a break, causing the spikes you’re describing.

                          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

                          C 1 Reply Last reply May 31, 2016, 4:03 PM Reply Quote 0
                          • C
                            coco65 @Tom Elliott
                            last edited by May 31, 2016, 4:03 PM

                            @Tom-Elliott

                            Just updated both the fog-server and the fog-node to 7945 on debian 8 both. Nothing has changed I am afraid. The fog server runs fine but the storage node is at a constant 100% processor load. The 4 FOG services (ImageReplicator etc) keep using every processor cycle they can get.

                            T 1 Reply Last reply May 31, 2016, 4:27 PM Reply Quote 0
                            • T
                              Tom Elliott @coco65
                              last edited by May 31, 2016, 4:27 PM

                              @coco65 Run the script as it was designed earlier.

                              service FOGMulticastManager stop && sleep 5 && service FOGMulticastManager start
                              service FOGPingHosts stop && sleep 5 && service FOGPingHosts start
                              service FOGImageReplicator stop && sleep 5 && service FOGImageReplicator start
                              service FOGSnapinReplicator stop && sleep 5 && service FOGSnapinReplicator start
                              service FOGScheduler stop && sleep 5 && service FOGScheduler start
                              

                              OR:

                              systemctl stop FOGMulticastManager && sleep 5 && systemctl start FOGMulticastManager
                              systemctl stop FOGPingHosts && sleep 5 && systemctl start FOGPingHosts
                              systemctl stop FOGImageReplicator && sleep 5 && systemctl start FOGImageReplicator
                              systemctl stop FOGSnapinReplicator && sleep 5 && systemctl start FOGSnapinReplicator
                              systemctl stop FOGScheduler && sleep 5 && systemctl start FOGScheduler
                              

                              This is going to make sure the services have enough time to restart. The Installer appears to not satisfy the “timing” properly.

                              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

                              C 1 Reply Last reply May 31, 2016, 6:32 PM Reply Quote 0
                              • C
                                coco65 @Tom Elliott
                                last edited by May 31, 2016, 6:32 PM

                                @Tom-Elliott : Thank you that works (the second version with systemctrl)

                                1 Reply Last reply Reply Quote 0
                                • T
                                  Tom Elliott
                                  last edited by May 31, 2016, 9:21 PM

                                  That’s why I post both. I have no idea what type your system is going to use so I just brute force them all.

                                  In either case, this shouldn’t be a problem even on subsequent updates now.

                                  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
                                  • 2
                                  • 2 / 2
                                  2 / 2
                                  • First post
                                    19/25
                                    Last post

                                  159

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project