MySQL and PDO upgrade problem

[lth2h]

We attempted to upgrade from MySQL 5.0 to 5.5. After some trouble (with rubygems which we removed ruby). We got the upgrade to work. During the apache (2.2)and php(5.4) recompiles, I went into the complete list of options and made sure PDO and mysql_pdo were checked.

Everything appears to have compiled. However all of our sites that use the PDO MySQL error out with "Class 'PDO' not found"

The extensions pdo.so and pdo_mysql.so are enabled in php.ini (and exist in the extensions directory). php -m lists PDO and pdo_mysql. phpinfo claims PDO is enabled and says:
PDO drivers sqlite, mysql
pdo_mysql
PDO Driver for MySQL enabled
pdo_mysql.default_socket /var/lib/mysql/mysql.sock /var/lib/mysql/mysql.sock

Everything looks right to me and we've tried everything we can think of including recompiling, restaring, and rebooting. We still end up with the same error.

What might we be doing wrong?

 

[cPanelMichael]

Hello

Check to see if the account experiencing this issue is using an individual php.ini file. It's possible that the user's php.ini file is not setup correctly.

Thank you.

 

[lth2h]

Thanks for the reply. None of the accounts in question are using an individual php.ini file.

We also found the box seems to have not upgraded php from 5.3 to 5.4. At least phpinfo was reporting 5.3 was the version number. We found in a directory of "failed" upgrades the libphp5.so and moved that into place. Sites now are reporting that they're using 5.4.

We are now seeing a new error:

Warning: PDO::__construct(): The server requested authentication method unknown to the client [mysql_old_password] in DatabaseConnection->__construct()


So the questions now are:
1) why did cPanel report that the upgrade succeeded when it apparently didn't
2) (and more importantly) how do we fix this new error?

Thanks in advance.

 

[cPanelMichael]

1. Feel free to open a support ticket so we can review the EasyApache build logs on your system to determine why it reported success during a failure. Post the ticket number here so we can update this thread with the outcome.

2. This seems like a separate problem. Assuming EasyApache now completes successfully, please open a new thread for this so we can investigate further.

Thank you.