Thread

I’m having a problem upgrading from EE 2.1.3 to 2.3.1. When the installer gets to this step it keeps refreshing and never finishes:

Please Stand By…
We are currently updating your ExpressionEngine installation.
Do not close your browser until the update routine is finished.
2.2.0

I have tried stopping the upgrade, and restarting. That seems to let it progress to the next step. However, at the end of the process I get a “Patch unsuccessful” message. So I restored from backup and tried again only to get the same messages again. Any ideas?

Hi DavidG,

I’m sorry this update is being a problem for you. I’ll do everything I can to troubleshoot this.

So I restored from backup and tried again…

Is that to mean that you restored the database as well? Are you seeing any other PHP or MyAQL related errors as part of the upgrade process? Please read through the Wiki on Troubleshooting Upgrade Errors.

Yes, I wiped the database and restored from backup. The second time I did this the update was still hanging up at the 2.2.0 step. I let it run about 10 minutes and then restarted the process manually. This time it started at 2.2.1 and finished the upgrade. So this instance is solved.

However, I am having this problem quite often on 2 different hosts so I’d like to find out what is causing it. I don’t receive errors - just the endless upgrade step it hangs on. The only solution I’m finding is starting the process over manually and I’m not sure if that’s very safe given the warnings the upgrader presents. I have checked through all the upgrade documentation and troubleshooting but haven’t found an answer yet.

Hi David,

I understand your frustrations with the updater. Are you noticing any anomalies after the update when using the Control Panel? What browser have you been using to run the updates?

Just updated two sites from 2.1.3 to 2.3.1 and experienced this exact same issue. Each point release would just hang and continually refresh without moving forward. Interestingly, it always reported 2.2.0 during the upgrade routine, but the config file upnumbered correctly. Kept restarting the upgrade routine until it was up to 2.3.1.

I normally do updates locally and haven’t had this problem in that case. Also, both hosted on Rackspace Cloud and updated via Safari.

All seems fine now too.

I continue to have the problem but the upgrades do complete after restarting them manually. I’m crossing my fingers that there are no issues with the systems after upgrading.

Hi David,

I’m glad you were able to push through on this. Keep us posted if you run into any trouble.

Cheers!