[PHP Questions On Move From CentOS 5.x To CentOS 6.x]

Home » CentOS » [PHP Questions On Move From CentOS 5.x To CentOS 6.x]
CentOS No Comments

—————————- Original Message ————————–

PHP Questions On Move From CentOS 5.x To CentOS 6.x

Home » CentOS » PHP Questions On Move From CentOS 5.x To CentOS 6.x
CentOS 4 Comments


A malfunctioning disk this past week accelerated a lingering decision to move to CentOS 6.x from CentOS 5.x.

Most of our content is functioning and being presented as it should be.

However, there appear to be php-related issues.

Basic squirrelmail (a php-dependent package) works correctly.

However, drupal, and other php-dependent parts that call PostgreSQL and mysql databases of our site are not being presented.

Apache’s log files show a 503 (for PostgreSQL) and 500 (for mysql) errors

I’m troubleshooting this through obvious channels (looking at logfiles, searching google, sdiff’ing configuration files).

However, if someone has suggestions or answers, please do speak up!

Much thanks,

Max Pyziur pyz@brama.com

4 thoughts on - PHP Questions On Move From CentOS 5.x To CentOS 6.x

  • The php versions in CentOS-5 and CentOS-6 are different. You don’t say what version you are using and what version you moved to WRT php.

    However, if you were running the default, the versions of software that run on CentOS-5 might have to be upgraded to run on the newer php in CentOS-6. (from php-5.1.6 to php-5.3.3)

    You might also need to follow the upgrade procedures when moving from the older version of mysql and PostgreSQL in CentOS-5 to the newer versions in CentOS-6. (mysql-5.0.95 to mysql-5.1.67, PostgreSQL-8.1.23
    to PostgreSQL-8.4.13)

    Upgrading for major versions (ie, from CentOS-5.x to CentOS-6.x) is a major undertaking and data/configuration files usually have to upgraded.

    This is unlike moving between point releases within the same major version (ie, moving from 5.8 to 5.9 or 6.3 to 6.4). This is because
    “minor version” upgrades are designed to just work because of backporting and freezing ABI/API changes inside the Major version … whereas changing Major versions is a major upgrade and should be planned and testing accordingly.

  • […]

    Thank you.

    I’m basically on a stock CentOS 6 system; for clarification, here’s what rpm returns:
    rpm -q php PostgreSQL mysql php-5.3.3-22.el6.x86_64

    One correction that took place is to add .php in the Apache directive like this (for a mysql-enabled website); it’s a virtual host:
    AddHandler server-parsed .html .php

    Now at least somethings shows, but the screen is also littered with all of the variable settings (sometimes typical with mysql/php misconfigurations).

    I know of upgrading database issues when moving to postgres 9.1; I also know of *major* issues when moving from postgis 1.5.x to 2.0.x


  • […]

    In both mysql and PostgreSQL I dumped to text and restored on the new CentOS 6 box/server.

    For PostgreSQL, that’s the recommendation.

    So far from command line and their respective command-line monitors, the mysql and PostgreSQL databases are correctly functioning.

    It’s the php-enabled interfaces that are the issue for me.

    Max Pyziur pyz@brama.com

  • On CentOS 5
    phpmyadmin- php-mysql-5.1.6-39.el5_8

    On CentOS 6
    php-IDNA_Convert-0.8.0-1.el6.noarch php-ldap-5.3.3-22.el6.x86_64
    phpMyAdmin-3.5.7-1.el6.noarch php-mysql-5.3.3-22.el6.x86_64
    php-pear-1.9.4-4.el6.noarch php-pgsql-5.3.3-22.el6.x86_64
    php-php-gettext-1.0.11-3.el6.noarch php-PHPMailer-5.2.2-1.el6.noarch php-process-5.3.3-22.el6.x86_64
    php-simplepie-1.3.1-3.el6.noarch php-xml-5.3.3-22.el6.x86_64

    Diffing php -m results:
    sdiff -s phpM-CentOS6.txt phpM-CentOS5.txt Core < dom | dbase enchant < ereg < fileinfo < filter < json < > mime_magic Phar < readline | pspell sqlite3 < xmlreader < xmlwriter < xsl < zip < >

    Please clarify; what extensions?