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

Updated from Fog v1.50 to V1.52 issue

Scheduled Pinned Locked Moved Solved
FOG Problems
4
27
4.3k
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.
  • G
    george1421 Moderator @Bigsease30
    last edited by Apr 28, 2018, 9:12 PM

    @bigsease30 How did you install FOG on your server? Did you download the tarball or use the preferred github method?

    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!

    B 1 Reply Last reply Apr 28, 2018, 9:16 PM Reply Quote 0
    • G
      george1421 Moderator
      last edited by george1421 Apr 28, 2018, 3:15 PM Apr 28, 2018, 9:14 PM

      If you used the tarball method, make sure your fog server has internet access and then use this process to create a local fog repo on your fog server.

      sudo -i
      git clone https://github.com/FOGProject/fogproject.git /root/fogproject
      cd /root/fogproject
      git checkout working
      cd bin
      ./installfog.sh
      

      Then when FOG 1.5.3 is released you would do this to switch back to the main release.

      cd /root/fogproject
      git checkout master
      cd bin
      ./installfog.sh
      

      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!

      B 2 Replies Last reply Apr 28, 2018, 9:18 PM Reply Quote 0
      • B
        Bigsease30 @george1421
        last edited by Apr 28, 2018, 9:16 PM

        @george1421 Hello George,

        I used the following steps:

        1. wget https://github.com/FOGProject/fogproject/archive/1.5.2.tar.gz (https://fogproject.org/download)
        2. tar -xzvf 1.5.2.tar.gz
        3. cd fogproject-1.5.2/bin
        4. sudo ./installfog.sh
        5. Followed all steps to completion.
        G 1 Reply Last reply Apr 28, 2018, 9:18 PM Reply Quote 0
        • G
          george1421 Moderator @Bigsease30
          last edited by Apr 28, 2018, 9:18 PM

          @bigsease30 Yeah, that is the tarball approach, its not as flexible as the github route. I would follow my steps to build a local fog repo and then reinstall FOG from there. That is the only way you can get hot fixes between releases.

          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
          • B
            Bigsease30 @george1421
            last edited by Apr 28, 2018, 9:18 PM

            @george1421 I can re-install using this method if you think that would assist in finding the issue?

            G 1 Reply Last reply Apr 28, 2018, 9:20 PM Reply Quote 0
            • G
              george1421 Moderator @Bigsease30
              last edited by george1421 Apr 28, 2018, 3:20 PM Apr 28, 2018, 9:20 PM

              @bigsease30 What Tom has said is that he thinks your issue was addressed in the prerelease version of 1.5.3. He would like you to install this prerelease version of 1.5.3 to see if your problems are resolved. If they are not resolved then I suspect they will hold up 1.5.3 (stable) until the devs find the root of your issue.

              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
              • B
                Bigsease30 @george1421
                last edited by Bigsease30 Apr 28, 2018, 4:30 PM Apr 28, 2018, 10:29 PM

                @george1421 OK, Reinstalled everything again. Following the instructions provided. I am now looking at V1.5.2.11. Same issues are present.

                Should I switch from Ubuntu and move to CentOS?

                G 1 Reply Last reply Apr 29, 2018, 1:54 PM Reply Quote 0
                • G
                  george1421 Moderator @Bigsease30
                  last edited by Apr 29, 2018, 1:54 PM

                  @bigsease30 I can duplicate the issue with 1.5.2 and ubuntu 16.04. Now to understand why…

                  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
                  • G
                    george1421 Moderator
                    last edited by george1421 Apr 29, 2018, 8:35 AM Apr 29, 2018, 2:34 PM

                    I found what the installer did incorrectly.

                    This is the default config file /etc/apache2/sites-enabled/001-fog.conf.

                    <VirtualHost *:80>
                        <FilesMatch "\.php$">
                            SetHandler "proxy:fcgi://127.0.0.1:9000/"
                        </FilesMatch>
                        KeepAlive Off
                        ServerName 10.0.0.6
                        DocumentRoot /var/www/
                        RewriteEngine On
                        RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)
                        RewriteRule .* - [F]
                        <Directory /var/www/fog/>
                            DirectoryIndex index.php index.html index.htm
                            RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
                            RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-d
                            RewriteRule ^/(.*)$ /fog/api/index.php [QSA,L]
                        </Directory>
                    </VirtualHost>
                    

                    The closing </Directory> directive is in the wrong place. It should look like this:

                    <VirtualHost *:80>
                        <FilesMatch "\.php$">
                            SetHandler "proxy:fcgi://127.0.0.1:9000/"
                        </FilesMatch>
                        KeepAlive Off
                        ServerName 10.0.0.6
                        DocumentRoot /var/www/
                        RewriteEngine On
                        RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)
                        RewriteRule .* - [F]
                        <Directory /var/www/fog/>
                            DirectoryIndex index.php index.html index.htm
                        </Directory>
                        RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
                        RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-d
                        RewriteRule ^/(.*)$ /fog/api/index.php [QSA,L]
                    </VirtualHost>
                    

                    Note: I also indent corrected the rewrite rules
                    If you correct your /etc/apache2/sites-enabled/001-fog.conf how I listed above FOG 1.5.2 will work correctly.

                    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!

                    B W 2 Replies Last reply Apr 29, 2018, 7:57 PM Reply Quote 3
                    • B
                      Bigsease30 @george1421
                      last edited by Apr 29, 2018, 7:57 PM

                      @george1421 Thanks for your assistance George. This resolved both issues that I was experiencing. Nice catch.

                      1 Reply Last reply Reply Quote 0
                      • W
                        wouwie @george1421
                        last edited by Apr 30, 2018, 3:12 PM

                        @george1421 Thanks George. That solved my problem.

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 2 / 2
                        2 / 2
                        • First post
                          26/27
                          Last post

                        221

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project