-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
[BUG] occ maintenance:repair --include-expensive without sucess #466
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
just found on nextcloud forum: |
I also have this issue, is there any news? |
It's a nextcloud bug which has been fixed in their next point release. |
Can you refer to the resources confirming this? |
Here is a comment that mentions a fix for Nextcloud v28 and v29. |
@Kapujino Looks like this will also be patched in the next rolling update, looking at the merge status. |
Good to hear. I've ran the command about 7 times. Driving me nuts. |
Same problem with my instance. Guess we'll have to wait for next patch. |
Have the same problem on Nextcloud Hub 8 (29.0.5) |
Same problem with all our Nextcloud 29 installation. |
fixed for me with latest docker release. |
Did you pull the official nextcloud image? |
I can also verify that this issue is fixed with image linuxserver/nextcloud:29.0.6 |
Exactly what is the difference between the LinuxServer version, and the official. I just pull the LinuxServer version because they host numerous images I use. But I've never seen an official list of what makes them different, or LinuxServer being better. |
fixed with the web updater. |
official one. |
Is this fixed? |
Have you tried updating? |
Yes, but can the author mark this solved? |
I can close the issue but note the bug was with nextcloud, not specifically the container. |
Is there an existing issue for this?
Current Behavior
First seen on update from 28.04 to 28.08, but tre repair does work.
Now after upgrade to 29.05 the error still remains after the repair command.
One or more mimetype migrations are available. Occasionally new mimetypes are added to better handle certain file types. Migrating the mimetypes take a long time on larger instances so this is not done automatically during upgrades. Use the command
occ maintenance:repair --include-expensive
to perform the migrations.Expected Behavior
i try to fix this with the occ command above listed.
Steps To Reproduce
??
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: