[Solved] Failed update v6.03 to 6.06
How Do I?
Hi EE folks,
I’m getting a Preflight error when starting to update EE from the CP, from 6.03 to 6.06 - this is on the production server, and I’ve not run a CP update from there yet.
Any pointers? Thanks.
Update Stopped (view stack trace) Oops, looks like the updater couldn’t complete. We stopped on Preflight check…
#0 ee/ExpressionEngine/Service/Updater/Runner.php(71): ExpressionEngine\Service\Updater\Downloader\Unpacker->verifyExtractedPackage()
#1 [internal function]: ExpressionEngine\Service\Updater\Runner->unpack()
#2 ee/ExpressionEngine/Service/Updater/SteppableTrait.php(94): call_user_func_array()
#3 ee/ExpressionEngine/Service/Updater/Runner.php(96): ExpressionEngine\Service\Updater\Runner->runStepParent()
#4 ee/ExpressionEngine/Controller/Updater/Updater.php(101): ExpressionEngine\Service\Updater\Runner->runStep()
#5 [internal function]: ExpressionEngine\Controller\Updater\Updater->run()
#6 ee/ExpressionEngine/Core/Core.php(251): call_user_func_array()
#7 ee/ExpressionEngine/Core/Core.php(111): ExpressionEngine\Core\Core->runController()
#8 ee/ExpressionEngine/Boot/boot.php(161): ExpressionEngine\Core\Core->run()
#9 httpdocs/admin.php(144): require_once('...')
#10 {main}
Kenny, Sorry you’re hitting this issue. Did you try to run the updater again after it failed to see if it was just a fluke? Also, is there anything not-default about this setup (i.e. system above web root, changed admin.php name, anything?) thanks
Thanks very much Andy. Yes indeed, system is above web root and renamed, and admin.php has been renamed. Update gave error on several attempts.
I can do a manual update but would prefer to get one-click working if possible.
ok. let me set up some tests and see if I can replicate the issue.
I set up a 6.0.3 site with system above webroot and admin.php renamed. I was able to 1-click up to 6.0.6 without issue. Let me ping this off the team and see if they have any thoughts or if anyone else on here chimes in that has ran into this lately.
oh. also. Do you see anything in your exp_update_log table that might suggest an error?
No lines in exp_update_log. Have tried renaming directory (and references in admin.php and index.php) back to default /system and cleared caches but no joy. Permissions look to be all 755 dirs / 644 files, CP and frontend works fine but anything to check specifically permissions-wise?
Tried loosening permissions but no. Nothing contradictory in config.php. A local install of the same site files and database gives the same error. Default /system and /admin.php names, location and references - same.
Found this in /system/user/cache/ee_update/update.log
[2021-May-24 16:46:56 +0100] Maximum execution time: 0
[2021-May-24 16:46:56 +0100] Memory limit: 256M
[2021-May-24 16:46:56 +0100] Checking file permissions needed to complete the update
[2021-May-24 16:46:56 +0100] Cleaning up upgrade working directory
[2021-May-24 16:46:56 +0100] Old zip archives found, deleting
[2021-May-24 16:46:56 +0100] Old extracted archives found, deleting
[2021-May-24 16:46:56 +0100] Checking free disk space
[2021-May-24 16:46:56 +0100] Free disk space (bytes): 55025393664
[2021-May-24 16:46:57 +0100] Downloading update package
[2021-May-24 16:47:00 +0100] Unzipping package
[2021-May-24 16:47:02 +0100] Package unzipped
[2021-May-24 16:47:02 +0100] Verifying integrity of unzipped package
[2021-May-24 16:47:02 +0100] There was a problem verifying the integrity of the extracted update file.
File not found: /var/www/vhosts/domain.co.uk/system/user/cache/ee_update/ExpressionEngine/system/ee/installer/updater/hash-manifest
Try again in a few minutes or contact support if the problem persists.In /ee_update:
- hash-manifest is present in the unpacked files.
- I tried deleting the ExpressionEngine directory and .zip then re-running but same error.
I know you said that hash-manifest does exist, but just to verify. this the correct full path? /var/www/vhosts/domain.co.uk/system/user/cache/ee_update/ExpressionEngine/system/ee/installer/updater/hash-manifest
Apologies Andy. I now see this issue must have been caused by a rogue global find-and-replace in the IDE, which affected files in /system… I’ve reverted this now and the offline upgrade has gone through fine.
Duh! Won’t blame the kids this time…
Appreciate your time.
oh man. good find. Glad you got it resolved.