Thread

Hello,
I am having a lot of trouble updating a site. It starts to run the database updates, but get stucks on a step. The ajax keeps reloading:
admin.php?C=wizard&M=do_update&agree=yes&progress=no&ajax_progress=yes&language=english

It does run some db query updates: member queries, custom fields and weblog to channel. Then it gets stuck.

I started trying to update it from 1.6.8 to 2.3.1, but I kept having this happen. So I updated to 1.7.1 with no problem and have been trying to update to 2.3.1 multiple times, with the same result.

I upgraded all the modules (playa, freeform, fresh variables, Reeorder). And tried to upgrade again, no change.

I saw some forum posts on it and it seemed mostly to be a environmental thing, but I am working locally and have updated sites before locally. My memory_limit is at 99. Any ideas on what else I can do to troubleshoot? I am out of ideas. Thanks.

Hi Kelly,

Sorry to see you’re running into this. Do you know on which step the update wizard gets stuck? After a failed update, if you look at the config.php file, it should tell you. Just look for the $config[‘app_version’] variable and post its value back here.

If you feel comfortable trying to continue the update, here’s how. If the file says, for example,

$config['app_version'] = "214";

...that means it stalled while trying to run the update to 2.1.5, and that set of updates is located at /system/installer/updates/ud_215.php.

If you want to have a look at your database and compare it against whichever update file was being run when it stalled, you can usually tell on which query the update wizard stalled. Just comment out the queries before that query (since they’ve already been successfully run against the DB), and run the update wizard again. It will start on this particular update file again (thanks to the version number config variable in config.php).

Does that help?

Hi Kevin,
Thanks for the help. I ran the update again and it still gets stuck in the browser on what is says is 2.0.0, but when I open the config is still says 1.7.1. It’s weird sometimes when I run the update some queries run (as listed in the browser) and sometimes it immediately gets stuck on 2.0.0. I can’t tell which query it gets stuck on.

It’s odd that it keeps stalling, but it makes sense that the config.php file would say 1.7.1 while the update wizard is stuck on 2.0.0. (After all, the update wizard would only change config.php to read 2.0.0 after it successfully completed the 2.0.0 update.)

Unfortunately for the sake of troubleshooting, the 2.0.0 upgrade was one of the single biggest updates.

Be on the lookout for an email from me. I’d like you to try your upgrade again (with a freshly imported DB, of course), and this time after you stall, export your DB’s structure (meaning without the data) and send it to me privately. I want to examine it to see where it’s stalling exactly during the upgrade.

Thanks for your patience on this!

I’m basically having the same issues as Kelly did. Apparently you worked with Kelly to resolve this off-forum. I’d be grateful if someone could provide guidance. I’ve tried the usual approaches to troubleshooting the upgrade (e.g. disabling javascript, clean database etc).

I am upgrading a relatively complex MSM install (30+ sites) with a database weighing in around 400+ MB.

Thanks for any assistance you provide. Let me know what I can provide to you.

Would appreciate some help here please. Thanks.

Hi web@sewanee,

With a database that large, the installer should be triggering a “large database update” warning. Are you not seeing this? The warning generates a shell script with instructions on how to use that script to update the database outside of the installer proper.

Can you give us an indication of where along the way the updater stalls?

Thanks!