Running Nextcloud web part in a Ubuntu VM in ESXi and the backend is mounted from a FreeNAS server using NFS. FreeNAS is squashing all user access to the same www-data uid.
Running Nextcloud v12.0.5 ; forced it to the beta channel and tried to update to 13.0.0 (can’t wait for Talk
Update failed at step 4.
Did some research and the common solution did not fixed my case (deleting the .step file).
Error is about a directory that can not be removed. Even if I remove it manually using the shell and re-try the process, it does not help. The directory is updater-GARBAGE/backups/nextcloud-18.104.22.168
Before trying the update, I shutdown the VM and took a snapshot of it. FreeNAS is also taking snapshots all the time.
After a few failures, I restored the VM. I was surprise when the VM still noticed that it was at step 4 of the update process. I restored the FreeNAS server as well and that got rid of the temp files.
I can easily rollback both the VM and the FreeNAS to the previous state before my upgrade, so I can do as many test as I wish.
Nextcloud version from 12.0.5 to 13.0.0
Operating system and version ESXi 6.5 ; Ubuntu 16.4.3
Apache or nginx version : Apache 2.4.18
PHP version : 7.0
The issue you are facing: Update blocks at step 4
Is this the first time you’ve seen this error? : No. Update from 12.0.4 to 12.0.5 ended up problematic too, but deleting the .step file and other tricks mentioned in other posts did it.
Steps to replicate it:
- Start the updater from the Admin section of Nextcloud 12.0.5
- Have the process stop at step 4
- Delete the .step file to go a little further
- Receive the error message about not being able to rmdir the backup directory
The output of your Nextcloud log in Admin > Logging:
Any idea on how to fix that ?
Thanks for your help,