Updated from Fog v1.50 to V1.52 issue

[Tom Elliott]

@bigsease30 mind installing the working branch? There issues and most likely they’re somewhat related to how storage nodes are tested. I’ve made a few changes and also fixed an api related issue that directly handled dealing with the rewrite rules.

cd /path/to/fog/repo
git checkout working
git pull
cd bin
./installfog.sh -y

[Bigsease30]

@tom-elliott Hello Tom. I am not familiar with the instructions that you provided. From looking it up I was able to find this GitHub Group but it references v1.5.1 and not the current version. Could you kindly point me in the correct direction?

Regards,

[george1421]

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

[george1421]

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

[Bigsease30]

@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.

[george1421]

@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.

[Bigsease30]

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

[george1421]

@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.

[Bigsease30]

@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?

[george1421]

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

[george1421]

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.

[Bigsease30]

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

[wouwie]

@george1421 Thanks George. That solved my problem.