Problem during upgrade from 1.5.0 to 1.5.2

[lebrun78]

Yes only one fog server on this computer (libvirt virtual machine)

[Wayne Workman]

@george1421 said in Problem during upgrade from 1.5.0 to 1.5.2:

@lebrun78 it doesn’t even display just the php code? That IS very strange.

Permissions…

@lebrun78 Set the ownership of the file to apache:apache and see what happens. Also, you put the file inside of /var/www/html right? Or was it just /var/www on centos 6? idk.

[lebrun78]

@wayne-workman
For the test /var/www/html/fog/phpinfo.php I set apache.apache and 775.
It did not work better

[Wayne Workman]

@lebrun78 Try to temporarily turn off SELinux with setenforce 0

[george1421]

I confirmed that this happens with FOG 1.5.1 or 1.5.2 running on Centos 6.9. I didn’t have time this weekend to fully debug but I have a short term work around.

1. Install FOG until it says to connect to the web management page to update the database.

2. Open a second connection to your fog server, for example using putty. The idea is to keep the installer waiting for you to update the database while you make this adjustment.

3. Update the following file: /etc/httpd/conf.d/fog.conf

4. Update the code to look like this. We need to comment out instruction to use php-fpm and to reenable the apache internal php engine.

<VirtualHost *:80>
    <FilesMatch "\.php$">
        #SetHandler "proxy:fcgi://127.0.0.1:9000/"
        SetHandler application/x-httpd-php
    </FilesMatch>
    KeepAlive Off
    ServerName 148.60.15.217

5. Save and exit your text editor
6. Restart apache service httpd restart
7. Return to the web browser and access the management page to update the database as normal.
8. Finish the FOG setup in the first window where you started the FOG installation.
9. Done.

I’m going to look into why this is happening. I just didn’t have as much extra time this weekend to understand why.

[lebrun78]

Thank you George, it works.
I have just add the line “SetHandler application/x-httpd-php”

[george1421]

@lebrun78 Make sure you comment out the “proxy:fcgi://127.0.0.1:9000/” entire line or you may get unexpected results. The pound (hashtag) at the start of the line indicates it commented out.

[lebrun78]

@george1421
Hello,
This problem reapair updating to 1.5.3 on my test server running with centos 6.9.
The solution you proposed is always available.

Thank you for you work

[george1421]

@lebrun78 Just to let you know the developers added this function to what will be FOG 1.5.4 (when it is released) so you will not have to do this patch in the future.

[lebrun78]

@george1421
Ok great