Joey Posted September 4 Share Posted September 4 Hey everyone, Our update failed after upgrading files and before updating the database and modules. We ran a test update on our test site which ran smoothly, but when attempting our live site we got the following: 2025-09-04 13:28:13] INFO - UpdateFiles - All files updated. Now updating database... [2025-09-04 13:28:14] INFO - UpdateDatabase - Cleaning file cache [2025-09-04 13:28:14] DEBUG - CacheCleaner - Directory "/app/cache/" does not exist and cannot be emptied. [2025-09-04 13:28:14] DEBUG - CacheCleaner - Directory /home2/xxxxxxx/public_html/cache/smarty/cache/ emptied [2025-09-04 13:28:14] DEBUG - CacheCleaner - Directory /home2/xxxxxxx/public_html/cache/smarty/compile/ emptied [2025-09-04 13:28:14] CRITICAL - ErrorHandler - /home2/xxxxxxx/public_html/modules/autoupgrade/vendor/symfony/filesystem/Filesystem.php line 180 - Symfony\Component\Filesystem\Exception\IOException: Failed to remove directory "/home2/xxxxxx/public_html/var/cache/prod": rmdir(/home2/xxxxxxx/public_html/var/cache/prod): Directory not empty Now.. we removed the cache manually and our shop seems fine... updated to 8.2.3 when we log into our back office and everything in the front office seems to work as well. Our question is should we be concerned that the database didn't seem to be updated? Is there a way we can run just the database update scripts? It won't allow us to re-apply the 8.2.3 upgrade and we didn't make a backup since the test site upgrade went smoothly and it was just a minor version. We're not concerned about the modules as we always kept them up to date anyway. Also... why did this fail? Lol Link to comment Share on other sites More sharing options...
Joey Posted September 4 Author Share Posted September 4 Just a follow up to this. We checked the upgrade log for the successful upgrade and there were only 2 minor sql queries that needed to be run which we ran manually. We think then that this would be fine to consider this a successful upgrade. Let us know if there are other areas we should be checking and if anyone has a commentary on the error it would be appreciated! Link to comment Share on other sites More sharing options...
WisQQ Posted September 4 Share Posted September 4 1 godzinę temu, Joey napisał: Just a follow up to this. We checked the upgrade log for the successful upgrade and there were only 2 minor sql queries that needed to be run which we ran manually. We think then that this would be fine to consider this a successful upgrade. Let us know if there are other areas we should be checking and if anyone has a commentary on the error it would be appreciated! What you did is totaly fine. Usually when there are some problems related to autoupgrade module you can do the upgrade manually. Just remember to make a backup before you update next time If you want to be 100% sure that upgrade was 100% successfull go see changelog on github or prestashop site. Link to comment Share on other sites More sharing options...
Knowband Plugins Posted September 5 Share Posted September 5 15 hours ago, Joey said: 2025-09-04 13:28:13] INFO - UpdateFiles - All files updated. Now updating database... [2025-09-04 13:28:14] INFO - UpdateDatabase - Cleaning file cache [2025-09-04 13:28:14] DEBUG - CacheCleaner - Directory "/app/cache/" does not exist and cannot be emptied. [2025-09-04 13:28:14] DEBUG - CacheCleaner - Directory /home2/xxxxxxx/public_html/cache/smarty/cache/ emptied [2025-09-04 13:28:14] DEBUG - CacheCleaner - Directory /home2/xxxxxxx/public_html/cache/smarty/compile/ emptied [2025-09-04 13:28:14] CRITICAL - ErrorHandler - /home2/xxxxxxx/public_html/modules/autoupgrade/vendor/symfony/filesystem/Filesystem.php line 180 - Symfony\Component\Filesystem\Exception\IOException: Failed to remove directory "/home2/xxxxxx/public_html/var/cache/prod": rmdir(/home2/xxxxxxx/public_html/var/cache/prod): Directory not empty According to this log, the database is already completed. After the database upgrade, the next step is cache clean, which throws an error. And after that, the next step is upgrading the module (which can be upgraded manually from the Module Manager tabs). Upgrade the default theme/email content is also the next step if you choose to upgrade the same from the initial upgrade screen. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now