Updating to c5 5.2.1 hangs website - help needed urgently!!

Permalink
Howdy!

I did a test upgrade from 5.4.2 to 5.5.2.1 on a test site on the same webserver as my live site and everything went well using Greg Joyce's how-to. So I backed my live website up, put it in maint. mode and proceeded to install 5.4.2.2 ran it and everything is good. Then the upgrade to 5.5.2.1 and when I come back up I get the rotating clock icon with "checking updates" going in an infinite loop! So I ssh'd into the webserver and checked the error_Log and I'm seeing a ton of these error messages:
[04-Aug-2012 19:40:34 UTC] PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo_mysql.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo_mysql.so: undefined symbol: php_pdo_unregister_driver in Unknown on line 0
[04-Aug-2012 19:40:34 UTC] PHP Warning:  PHP Startup: PDO: Unable to initialize module
Module compiled with module API=20060613
PHP    compiled with module API=20090626
These options need to match
 in Unknown on line 0
[04-Aug-2012 19:40:34 UTC] PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo_sqlite.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo_sqlite.so: undefined symbol: php_pdo_unregister_driver in Unknown on line 0


How can I stop this from the cmdline?

Any thoughts? MTIA - Jeff.

Dinosaur
 
JohntheFish replied on at Permalink Reply
JohntheFish
You can switch off the check for updates with a define in config/site.php (there is a howto on whitelabelling with details).

With that solved, maybe you can get into the dashboard and sort out the connection.
Dinosaur replied on at Permalink Reply
Dinosaur
Howdy JTF,

Sorry for the delayed reply, but had to deal with a urgent issue. I tried adding the config.site with no luck. I looked at a white labelling how-to doc, but is incomplete and didn't give any help on where to find a complete listing of all the options.

I think the problem was with the version of shared object that it was trying to find. I tried doing the downgrade and had issues, so I ended up starting over with 5.5.2.1. The think I got a little too confident when the test server went so smoothly - WCPGW!?! I think next time (which won't be anytime soon), I'll backup the entire site as a precaution.

Thanks for the help! Jeff.
JohntheFish replied on at Permalink Reply
JohntheFish
For future reference, Matt has published a howto thta may be of use:
http://www.concrete5.org/documentation/how-tos/developers/troublesh...