When I attempt and upgrade from 4.3.1 to 4.3.2 the upgrade runs, then the popover appears and seems to be running (message changes), then the popover message box disappears and the Upgrade Center page is unchanged. Checking the version I see the upgrade did not happen.
More specifically I see "Processing" in the popover message box then "Upgrade progress" with sub-message "Backing up data for cscart_products_categories". Then the popover message box goes away with nothing changed.
I did try a database backup using Administration | Backup/Restore and this worked fine. I also checked server error logs and nothing is shown.
The failure happens after roughly 3:20 (380 seconds) so considerably past the 120 second PHP execution timeout or default Apache timeout (I'm not sure of the actual Apache timeout in my host).
Thanks Tool, good ideas there. Unfortunately none solved my problem.
It appears - looking at core_log.txt - that the upgrade always stops at "backup files and Database". In fact, backups using Administration | Backup/Restore also quietly fails when I back up both files and database. They works fine when I backup the database only.
I tried setting all var/cache, var/backups, and /var/upgrade folders to open permissions, changing the compress setting in App.php (per the other post), resetting ownership recursively for all project folders, clearing out the /var/upgrade folder (except for restore.php, which was required). In all cases the upgrade stops before finishing with no obvious error. It does seem to consistently stop on or after "Backing up data for cscart_products_categories".
So, I'm thinking this is a backup issue and will start looking at it from that perspective, but any other suggestions are most appreciated.
For a 4.3.1 -> 4.3.2 upgrade, check the file: var/upgrades/upgrade.log. It probably ends on backup. If so, follow the instrucitons here for commenting out the backup (but do your site and DB backups manually FIRST)
You should also check the Apache configuration value for Timeout. It should be set to 300 (seconds) or higher. Some hostings set this to an unrealistically low value.
But most likely, you will have to do the comment discussed in the other post and you will have to do this for the next upgrade (4.3.3) as well.
And I'd suggest you search the forum for solutions before posting new threads.
You'll have to describe in more detail exactly what steps have completed and where things are at when you believe it's failed. Have you checked the Timeout value in Apache (note this is wall clock time for last PHP output to apache).
Here is the message. Sometimes it fails on different schemas, but it always fails and then takes me back to the upgrade center where I get the install button to install the version that just failed to install
If so, you are probably either exceeding memory or time limits imposed by your hosting.
First check your error_log file that should be in the root of your store. If nothing there about timeout or exceeding memory, contact your hosting and have them check your Apache logs to see if they can identify the problem
And also, if it is returning to the upgrade center, then the issue is NOT with an Apache Timeout but instead with exceeeding either a PHP resource setting or one imposed by your hosting.