Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Updater 17.0.0 Extracting Error during unpacking zipfile: No error - and now another Error #248

Closed
witzker opened this issue Oct 12, 2019 · 9 comments

Comments

@witzker
Copy link

witzker commented Oct 12, 2019

grafik

Problem discribed here:
https://help.nextcloud.com/t/error-updater-7-0-extracting-error-during-unpacking-zipfile-no-error/61865/2

pls give me Info how to solve this

@witzker
Copy link
Author

witzker commented Oct 14, 2019

No NEWS?

@witzker
Copy link
Author

witzker commented Oct 17, 2019

another TRY Now THIS
grafik

PLS Help

@witzker witzker changed the title Error Updater 7.0 Extracting Error during unpacking zipfile: No error Error Updater 17.0.0 Extracting Error during unpacking zipfile: No error - und jetzt anderer Error Oct 17, 2019
@witzker witzker changed the title Error Updater 17.0.0 Extracting Error during unpacking zipfile: No error - und jetzt anderer Error Error Updater 17.0.0 Extracting Error during unpacking zipfile: No error - and now another Error Oct 18, 2019
@devosthomas
Copy link

same issue with me

@mathieu-aubin
Copy link

mathieu-aubin commented Dec 23, 2019

Had the same issue, ended up being quota reached from a Webmin user (i hate frameworks an didn't think to check for quota restrictions)

Basically, make sure that you check for...

  • Sufficient free space on the system/partition (for both backup and new stuff)
  • Enough temporary free space on/in the system's temp directory (many of times, tmp folder is size restricted and/or on a partition of it's own -- so check for that)
  • Quotas. No set quotas for the user NextCloud run under/with or, that you are well within quota limits currently enforced for php process owner. As it should, optimally, not be a real user, disabling quota altogether will help preventing other quota-related issues that inevitably will arise and for which (as we discovered) verbosity is limited.
  • RAM/Memory availability
  • Directory ownership/permissions. This also goes for session storage folder, if you are -- and really should be -- using a folder other than /tmp

edit: made it clearer, more defined and added more of the same type of potential fixes. Also, it seems this is something that should be documented or at least handled. The things i mentionned are sometimes overlooked by a few, experienced dudes and dudesses of all planets alike.

@Relax-Roger
Copy link

Same happens when I try to update from 16.0.6. to 16.0.7.

@devosthomas
Copy link

Had the same issue, ended up being quota reached from a webmin user

Same case with me. Make space :)

@Relax-Roger
Copy link

Same case with me. Make space :)

Thanks for the advice! I have deleted some old Nextcloud backup folders from previous updates, et voilà problem solved.
Those folders keep piling up considerably. I really feel the updater should offer some help on managing/deleting old backups...

@mathieu-aubin
Copy link

check #248 (comment) for a potential fix

@joshtrichards
Copy link
Member

Let's cover disk space availability checking work in #523. Closing to centralize tracking there.

@joshtrichards joshtrichards closed this as not planned Won't fix, can't repro, duplicate, stale Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants