Failed update from v6.0.3 to v6.0.6 - another example.
How Do I?
Hi, EE.
I am also experiencing difficulty in updating from v6.0.3 to v6.0.6 using the one-click updater.
I have tried using an empty database with a fresh install of v6.0.3 to the webroot folder, without moving the system folder or renaming admin.php. The update stops part-way through, with a message that preflight check has failed.
The update log shows the following:
[2021-May-31 16:57:28 +0000] Maximum execution time: 0
[2021-May-31 16:57:28 +0000] Memory limit: 256M
[2021-May-31 16:57:28 +0000] Checking file permissions needed to complete the update
[2021-May-31 16:57:28 +0000] Cleaning up upgrade working directory
[2021-May-31 16:57:28 +0000] Checking free disk space
[2021-May-31 16:57:28 +0000] Free disk space (bytes): 1763252633600
[2021-May-31 16:57:29 +0000] Downloading update package
[2021-May-31 16:57:35 +0000] Unzipping package
[2021-May-31 16:57:46 +0000] Package unzipped
[2021-May-31 16:57:46 +0000] Verifying integrity of unzipped package
[2021-May-31 16:57:46 +0000] Package contents successfully verified
[2021-May-31 16:57:46 +0000] Checking server requirements of new ExpressionEngine version
[2021-May-31 16:57:46 +0000] Server requirements check passed with flying colors
[2021-May-31 16:57:46 +0000] Moving the updater micro app into place
[2021-May-31 16:57:46 +0000] Taking the site offlineThe update stops at this point. I have to delete the installer folder to regain access to the Control Panel.
I would appreciate your advice.
Thanks,
Syd.
P.S. Sorry, I couldn’t figure out how to get Markdown to work.
Do you see anything in your exp_update_log table or /system/user/cache/ee_update/update.log that might suggest an error?
If you see any file paths, I’d ensure that you verify those full paths exist and permissions are correct.
Also, make sure you haven’t modified any core files (files in system/ee ).
Thanks, Andy.
No, there’s nothing to indicate an error in the update logs. They also don’t show any file paths.
I haven’t modified any core files, as all I did was to install EE, then immediately attempt to update the version.
Am I missing something?
When you delete the installer folder, is the site upgraded?
No, the site is still v6.0.3.
ok. trying to troubleshoot some more based on feedback from the team. A few questions:
- Is
is_site_onbeing set? If so is the site turned off via the config.php file before you start the upgrade? This would be something like$config['is_site_on']in your config.php OR$assign_to_config['is_site_on']in your index.php or admin.php. - Is the site off via the CP before you start the upgrade?
- After the failed upgrade, is the site on or off either via the config file or via the toggle in the CP?
thanks
A1:
$config[‘is_system_on_before_updater’] = ‘y’; in config.php file.
There is no equivalent assignment in either the index.php or the admin.php files.
The setting does not appear to change if I turn the site off via the CP.
A2:
I have tried the upgrade both with the site off and on via the CP.
A3:
After the failed upgrade, the CP setting of the site on/off remains as it was.
The config.php assigment remains $config[‘is_system_on_before_updater’] = ‘y’; in either case.
Syd,
I’m pretty sure that $config[‘is_system_on_before_updater’] = ‘y’ is left over from the updater. Try removing that from config.php and run it again.
Thanks, Andy.
I’ve tried deleting $config[‘is_system_on_before_updater’] = ‘y’ from config.php, then running the updater. The same problem occurs, and the deleted line reappears in config.php.