Preflight failed 6.03 > 6.4.3 - No error
How Do I?
I have two sites that are more or less identical and run on the same account. Had no issues updating them from EE 2 > EE 6 a while back.
Completed the one click install for site 1 with no problem. With site 2, I get a preflight check fail, and then nothing. No error message, just the option to Continue (which takes the site offline) or go back to Control Panel (which means I just have to delete the update directory).
I’ve checked the update_logs in /cache/ - no clues there either.
Any pointers on how to troubleshoot and get a update trace output?
Thanks!
Have you retried the update at all? I have had a preflight fail before but when I ran the updater again it worked.
Thanks Rob. Yes I retried multiple times but still no joy unfortunately.
Enabling “Enable debugging?” doesn’t show any output on the updater process either. Bit stumped.
The update_log says this which is accurate (it does take the site offline) but then nothing:
[2022-Dec-21 13:31:36 +0000] Maximum execution time: 0
[2022-Dec-21 13:31:36 +0000] Memory limit: 256M
[2022-Dec-21 13:31:36 +0000] Checking file permissions needed to complete the update
[2022-Dec-21 13:31:36 +0000] Cleaning up upgrade working directory
[2022-Dec-21 13:31:36 +0000] Old zip archives found, deleting
[2022-Dec-21 13:31:36 +0000] Old extracted archives found, deleting
[2022-Dec-21 13:31:38 +0000] Checking free disk space
[2022-Dec-21 13:31:38 +0000] Free disk space (bytes): 934298263552
[2022-Dec-21 13:31:38 +0000] Downloading update package
[2022-Dec-21 13:31:40 +0000] Unzipping package
[2022-Dec-21 13:31:46 +0000] Package unzipped
[2022-Dec-21 13:31:46 +0000] Verifying integrity of unzipped package
[2022-Dec-21 13:31:46 +0000] Package contents successfully verified
[2022-Dec-21 13:31:46 +0000] Checking server requirements of new ExpressionEngine version
[2022-Dec-21 13:31:46 +0000] Server requirements check passed with flying colors
[2022-Dec-21 13:31:46 +0000] Moving the updater micro app into place
[2022-Dec-21 13:31:46 +0000] Taking the site offlineI could do a manual update but that’s harder to roll back from.
Decided to do a manual update in the end which worked.