Upgrading from 5.3.2 to 5.4.1.1: long-running Apache process

Permalink
Attempted to upgrade my site from 5.3.2 to 5.4.1.1 while the site was hosted on my shared hosting provider and received a 500 Internal Error. Helpdesk couldn't provide me any details so I moved the database in it's current, partially upgraded form (did a mysqldump) and webroot to a micro instance on Amazon EC2 and attempted the upgrade again.

Now instead of (I'm assuming) timing out like it did on the shared host, it's still running, like 15 minutes later.

Funny thing is, show processlist in MySQL shows nothing: I'm not sure what Apache's doing right now but it's consuming a good 50-70% cpu, dropping down to 1%, but never idle. The apache error log for the site has nothing in it either; not sure what's going on.

The webroot is a good 1.1GB, the database is 43MB.

Running the latest version of MySQL/PHP5 from the Ubuntu 10.04 LTS repos.

 
Brainakazariua replied on at Permalink Reply
Brainakazariua
A 500 internal server error usually points towards the permissions on the files/folders.
either they are not opened up enough or closed up to much.

it's also possible that some folders/files have the wrong permissions.

I suggest you check those first.
gravyface replied on at Permalink Reply
Seems odd that permissions would all of a sudden be wrong on a working website...

Ran chmod -R 755 (www-data is the owner) on the site root, no difference: still running after 5 minutes. Running lsof to see what Apache's trying to do.
gravyface replied on at Permalink Reply
Getting some errors now in the Apache error log:

PHP Fatal error:  Uncaught exception 'Exception' with message 'Invalid task permission.' in /var/www/example.com/concrete/models/task_permission.php:169\nStack trace:\n#0 [internal function]: TaskPermission->__call('canAccessSitema...', Array)\n#1 /var/www/example.com/concrete/helpers/concrete/dashboard/sitemap.php(337): TaskPermission->canAccessSitemap()\n#2 /var/www/example.com/concrete/tools/page_controls_menu_js.php(87): ConcreteDashboardSitemapHelper->canRead()\n#3 /var/www/example.com/concrete/startup/tools.php(11): include('/var/www/exampl...')\n#4 /var/www/example.com/concrete/dispatcher.php(129): require('/var/www/exampl...')\n#5 /var/www/example.com/index.php(2): require('/var/www/exampl...')\n#6 {main}\n  thrown in /var/www/example.com/concrete/models/task_permission.php on line 169
Brainakazariua replied on at Permalink Reply
Brainakazariua
Sounds like something went wrong during the upgrade.
Upload a new core and then run the upgrade again to see if it solves the problem.
Brainakazariua replied on at Permalink Reply
Brainakazariua
The moment you changed the core you got new files, it then can happen that those files/folders have the wrong permissions.

Try downgrading the site to the previous version to see if it remains slow/stuck.

if it's fast again, upgrade one version at the time instead of skipping versions, it takes a bit longer but it'll give you a better idea of where it goed wrong.
gravyface replied on at Permalink Reply
I'm assuming by downgrading you mean I can mv the old concrete folder back in the webroot?
Brainakazariua replied on at Permalink Reply
Brainakazariua
correct.
place back the old concrete folder and then go to yoursite.com/tools/required/upgrade to downgrade it
gravyface replied on at Permalink Reply
Says:

Your site is already up to date! The current version of Concrete5 is 5.3.2. You should remove this file for security.

I also noticed some tables got renamed/prefixed with an underscore, others didn't.
Brainakazariua replied on at Permalink Reply
Brainakazariua
It also says: Click here if you would like to re-run this script.
of you re-run it you'll have downgraded
gravyface replied on at Permalink Reply
There's no other link.
gravyface replied on at Permalink Reply
Figured out that the link just appends ?force=1 onto the end of upgrade.php so put back the original (5.3.2) concrete folder and forced an "upgrade" to downgrade as you say. Finished with an error re: adding another AUTO key.

Stupidly I never backed up the the database before starting this upgrade, so I'm kind of boned I guess.