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

    503 Service Unavailable Error

    Scheduled Pinned Locked Moved
    FOG Problems
    10
    67
    28.5k
    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 @flipwalker
      last edited by

      @flipwalker Just for clarity, can you confirm the steps you took to resolve (hopefully the issue)? I provided several steps here trying this and that to find a common thread.

      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!

      F 1 Reply Last reply Reply Quote 0
      • F
        flipwalker @george1421
        last edited by

        @george1421 I originally didn’t follow your guide to install and activate fpm, I had assume it was default. Once I followed the guide(not without cursing and much looking up of VIM guides), and got it installed and activated my web interface came back up and my clients waiting to image started communicating with FOG again.

        I’m still not 100% that it’s fixed or if the last step(restarting PHP and Apache) simply reset the problem and it’s going to reappear in a few hours. I’ve been watching it run for 45 mins or so now and it at least appears to be stable. But we’ll see if it completes overnight or not.

        Just wish I had remote capability so I could monitor from home instead of having to come to the office.

        Philip

        1 Reply Last reply Reply Quote 1
        • D
          Daniel Miller @george1421
          last edited by

          @george1421 This particular machine is only servicing about 30 units with 4 distinct named users and currently reporting about 375MB free. Looking through its history over the past 2 years (reported through snmp), it historically has had anywhere from 350MB to 500MB free, depending on the day of the week. Truncating the userTracking table does make it happy for now. If you are loading that table with PHP on every request, the behavior does make a lot of sense.

          @Tom-Elliott I completely understand that, and for this particular environment it is not an important feature. We have some other larger environments (250-ish) where the user tracking feature does get used from time to time (“Hey, was the account of student X used to log in yesterday?”), so It is something I check in my canary system.

          @flipwalker The box I have is also Ubuntu 16.04. Check to see if your config file is in /etc/php/7.1/fpm/pool.d/.

          1 Reply Last reply Reply Quote 0
          • H
            Hammett131
            last edited by

            Not sure if this is related I have an older post where my web ui stopped working but my error logs are just
            non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109 and 110.

            1 Reply Last reply Reply Quote 0
            • P
              pijltje
              last edited by pijltje

              Hi, it sounds like the same issue I have had.
              My solusion was to remove the www.conf in the /etc/php-fpm.d directory.
              this directory must contane one file only (fog.conf)

              george1421G H 2 Replies Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @pijltje
                last edited by

                @pijltje said in 503 Service Unavailable Error:

                Hi, it sounds like the same issue I have had.
                My solusion was to remove the www.conf in the /etc/php-fpm.d directory.
                this directory must contane one file only (fog.conf)

                FWIW, my instructions say to use fog.conf, the fog installer created the www.conf. So the fog installer owns www.conf and will be created each time the installer is run. You should remove the fog.conf file since that was hand created or you will have problems each time you upgrade fog.

                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
                • H
                  Hammett131 @pijltje
                  last edited by

                  @pijltje Hmm I don’t see that directory I am using Ubuntu (I know I know, first time fog when I have time I WILL switch been a pain honestly)

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

                  220

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project