error when upgrading to 1.5.2



  • Upgrading from last release to 1.5.2 (skipped 1.5.1) shows an error in browser when accessing the database upgrade during installation:

    • @license http://opensource.org/licenses/gpl-3.0 GPLv3 * @link https://fogproject.org / /* * The main index presenter * * @category Index_Page * @package FOGProject * @author Tom Elliott * @license http://opensource.org/licenses/gpl-3.0 GPLv3 * @link https://fogproject.org */ require ‘…/commons/base.inc.php’; $FOGPageManager = FOGCore::getClass(‘FOGPageManager’); if (session_status() != PHP_SESSION_NONE) { if (isset($_SESSION[‘delitems’]) && !in_array($sub, array(‘deletemulti’, ‘deleteconf’)) ) { unset($_SESSION[‘delitems’]); } } FOGCore::getClass(‘ProcessLogin’)->processMainLogin(); require ‘…/commons/text.php’; $Page = FOGCore::getClass(‘Page’); $nodes = array( ‘schema’, ‘client’, ‘ipxe’ ); if (!in_array($node, $nodes) && ($node == ‘logout’ || !$currentUser->isValid()) ) { $currentUser->logout(); $Page ->setTitle($foglang[‘Login’]) ->setSecTitle($foglang[‘ManagementLogin’]) ->startBody(); FOGCore::getClass(‘ProcessLogin’) ->mainLoginForm(); $Page ->endBody() ->render(); } else { if (FOGCore::$ajax) { $FOGPageManager->render(); exit; } $Page->startBody(); $FOGPageManager->render(); //if ($FOGPageManager->getFOGPageName() !== $FOGPageManager->getFOGPageTitle()) { $Page ->setTitle($FOGPageManager->getFOGPageTitle()); //} $Page->setSecTitle($FOGPageManager->getFOGPageName()); $Page ->endBody() ->render(); }

    Running Centos 6.9. No changes has been made to my server config.


  • Moderator

    @sebastian-roth There seems to be an issue with php-fpm and apache on Centos 6.9. For now the quick fix is to disable the link between php-fpm and apache to return php control back to apache. ref: https://forums.fogproject.org/topic/11722/problem-during-upgrade-from-1-5-0-to-1-5-2/18


  • Developer

    @pmonstad Well this is the PHP code not being executed on the server. Is PHP still installed and enabled on your server? rpm -qa | grep php and httpd -M might shed a light on this.


Log in to reply
 

396
Online

6.1k
Users

13.4k
Topics

126.4k
Posts