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

    Issues with Fog 1.5.2

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    44
    6.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.
    • george1421G
      george1421 Moderator @K.Hays
      last edited by

      @k-hays Ok so you’ve confirmed that from the 10.10.0.x subnet you can ping the fog server? If so then it may be that double backslash in the url after fog. If that is the case, please check the fog settings as well as the storage node configuration to see if you have a training backslash.

      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!

      K 1 Reply Last reply Reply Quote 0
      • K
        K.Hays @george1421
        last edited by

        Welp i goofed. I’m going to have to get that website file again for you because apparently i forgot to reinstall 1.5.2 before getting the file. If there are any differences between the two i will let you know. As far as your most recent question yes, we can ping from that subnet( The clients also do still connect, see second picture). There was not a second / in the storage node but there was under TFTP PXE KERNEL DIR

        1 Reply Last reply Reply Quote 0
        • K
          K.Hays
          last edited by

          Due to hardware changes and accompanying issues (and time restraints) we are just reloading our fog server on a different machine. Sorry for the delay, summer is our busiest time and of course when we run into the most issues :,D Thank you though!

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by

            @K-Hays So is this solved from your point of view?

            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

            K 1 Reply Last reply Reply Quote 0
            • K
              K.Hays @Sebastian Roth
              last edited by

              @sebastian-roth Yessir!

              1 Reply Last reply Reply Quote 0
              • K
                K.Hays
                last edited by

                Welpppp, I suppose not. We were running this server on a hyper v and decided to just try out to separate options. We had a new computer we were going to try and load it on, as well as setting up a new hyper v with debian instead. Both fresh installs had the same error when we tried to test either of them. I went ahead and checked the file the George mentioned prior ( On the Hyper V server) and this is the outcome.

                0_1529673120560_FogForum.PNG

                1 Reply Last reply Reply Quote 0
                • K
                  K.Hays @george1421
                  last edited by

                  @george1421 I adjusted the file to match what you put in this post https://forums.fogproject.org/topic/11797/updated-from-fog-v1-50-to-v1-52-issue/25

                  Will test soon. Any other ideas?

                  Q 1 Reply Last reply Reply Quote 0
                  • Q
                    Quazz Moderator @K.Hays
                    last edited by Quazz

                    @k-hays Can you deploy an image to a single client without issue?

                    This seems to me like an issue with PHP-FPM getting overloaded.

                    On debian the pm.max_children directive is often stuck on 5 which is generally too low for most people. (40 is a good starting point for testing)

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      K.Hays @Quazz
                      last edited by K.Hays

                      @quazz Yes. Single client works fine. I don’t know the specific number in which it starts to fail; but in a lab we image anywhere from 20 - 35ish computers and it seems to fail whenever we try those numbers. The issue also persisted when we started with ubuntu.

                      Q 1 Reply Last reply Reply Quote 0
                      • Q
                        Quazz Moderator @K.Hays
                        last edited by Quazz

                        @k-hays There’s currently some known issues with PHP-FPM settings/getting overloaded, particularily on debian based systems.

                        I definitely recommend checking the pm.max_children value (not 100% sure where it is on debian)

                        You should be able to check the PHP-FPM logs on the WebUI to see if it’s been complaining about not enough max_children or memory exhaustion or timeouts I think.

                        K 1 Reply Last reply Reply Quote 0
                        • K
                          K.Hays @Quazz
                          last edited by

                          @quazz I’ll go digging. Any ideas?

                          Q 1 Reply Last reply Reply Quote 0
                          • Q
                            Quazz Moderator @K.Hays
                            last edited by

                            @k-hays Try grep -irl pm.max_children /etc

                            K 1 Reply Last reply Reply Quote 0
                            • K
                              K.Hays @Quazz
                              last edited by

                              @quazz Ok I found it! Now, what do you think the max i should put there is. Sometimes we might image up to two, maybe three labs at a time. would 90 be a stretch?

                              Q 1 Reply Last reply Reply Quote 0
                              • Q
                                Quazz Moderator @K.Hays
                                last edited by

                                @k-hays It depends on how many resources your server has available to itself.

                                We haven’t done a ton of testing on the exact numbers. The value will depend on the amount of RAM and how much the average PHP-FPM uses.

                                Start with 40 as a safe value and go from there, imo.

                                K 1 Reply Last reply Reply Quote 0
                                • K
                                  K.Hays @Quazz
                                  last edited by

                                  @quazz Ok will do. I’ll end up testing this today as well. We’re using a server that has a lot of unused resources so we can devote a good bit to it. I also want to say that we are on the current dev-branch, so 1.5.4. These were all fresh builds as well, even on ubuntu. Does it automatically set the max children to 5 now?

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

                                    @k-hays said in Issues with Fog 1.5.2:

                                    . would 90 be a stretch?

                                    Don’t do that much you could run into a situation of resource exhaustion. Under normal imaging you shouldn’t see more than 10 worker thread. For max children I would set it to 40.

                                    If you are using FOG 1.5.2 or later here is what I would change in the www.conf file for php-fpm.

                                    php_admin_value[memory_limit] = 256M
                                    pm.max_requests = 2000
                                    pm.max_children = 40
                                    pm.min_spare_servers = 6
                                    pm.start_servers = 5
                                    

                                    Update those settings then restart php-fpm.

                                    Queue up your multicast then on the fog server linux console start top then press P to sort by CPU usage. Watch, you should have 5-7 php-fpm worker threads running, they should be the top cpu users.

                                    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!

                                    K 1 Reply Last reply Reply Quote 1
                                    • K
                                      K.Hays @george1421
                                      last edited by

                                      @george1421 Ok, does it make a difference if we do unicast? Just wondering

                                      george1421G 1 Reply Last reply Reply Quote 0
                                      • george1421G
                                        george1421 Moderator @K.Hays
                                        last edited by george1421

                                        @k-hays The memory setting will help the unicast imaging too

                                        But just to be sure none of your conditions have changed since your original post of 2 months ago? You are still having the same exact condition?

                                        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!

                                        1 Reply Last reply Reply Quote 0
                                        • K
                                          K.Hays
                                          last edited by

                                          In terms of network yes. The server itself is the same, but it’s been reloaded to debian 9 and 1.5.4 as opposed to ubuntu and 1.5.2.

                                          K 1 Reply Last reply Reply Quote 0
                                          • K
                                            K.Hays @K.Hays
                                            last edited by K.Hays

                                            @k-hays Also if you meant the error, then yes. It is the exact same issue (or at least extremely similar). I made the changes and will test it again shortly.

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

                                            137

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project