-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Cannot delete/unshare shared file with me when remote server is down #14797
Comments
cc @nextcloud/sharing |
Was about to post this issue again. Actual behaviour
Server configuration detailOperating system: Linux 4.8.8-040808-generic #201611150231 SMP Tue Nov 15 07:33:21 UTC 2016 x86_64 Webserver: Apache (fpm-fcgi) Database: mysql 5.7.27 PHP version: 7.2.21 Nextcloud version: 16.0.4 - 16.0.4.1 Updated from an older Nextcloud/ownCloud or fresh install: owncloud 8? Where did you install Nextcloud from: unknown Signing statusArray
) List of activated apps
Configuration (config/config.php)
Are you using external storage, if yes which one: local/smb/sftp/... Are you using encryption: Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/... Client configurationBrowser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 Operating system: LogsWeb server error log
Nextcloud log
Browser log |
For me it is not crashing, it just ignores it and shows a big error/warning in tray. |
I have one of those share in / and the client stops the synchronization every time it gets to that file so it never finishes syncing the rest of the files. Client version is 2.5.3 on windows 10 |
Could you modify the code like above? I hope we gain more information from the stack trace. Check the logs for |
|
|
Disabling Ransomware_protection does not work either:
|
@kesselb for me it is a file I got shared via federated share, but now the remote server is offline. I also cannot unshare it:
|
@kesselb does this help:
|
I hope ;) It's not possible to delete the share because of the |
Any update here? |
#14797 (comment) also didn't do a thing for me. The main issue is:
still returns false. So it throws in:
therefor later on in: we dont have an object which we could delete. But I found another bug on the way, which would not allow to load any remote shares if one was offline. |
One more detail: I'm hit by the same bug, but for me, the Linux client does not have a problem with the "stale" share, it still syncs everything else normally. However, the Android client completely breaks, and does not show any folders anymore. I see a request for |
I'm experiencing the same issue. Note that I think it may also be the cause of my iOS nextcloud client not showing me any folders... See nextcloud/ios#1348 Eventualy, this solved my issues:
|
Same problem here with Nextcloud 20. Can't delete a shared folder from an old, currently not existing server. The fix from @AMDG2 works. Hope to see a fix soon instead of the dirty manual database change. |
I had the same problem in Nextcloud 20.0.8 and tried to apply the fix from @AMDG2 detailed above but it seems the schema of the database changed since then. Here's what worked for me:
One notable difference could be that the broken share in my case was a directory instead of a file. |
Discussed with @blizzz, our "new" idea is that server should
|
seems the patch from @kesselb here #14797 (comment) cannot work, because once the exception is caught,
the way I see it we should only do this if and deleting the root of the mount point is the same as deleting the share maybe for some file operations we should not throw on the DAV layer I found this: https://github.com/nextcloud/server/blob/v21.0.5/apps/dav/lib/Connector/Sabre/ObjectTree.php#L158 however, the challenge is that we already have a need to find where the mount point itself is being adressed |
to make it read from the cache and not attempt to read metadata from the storage, we'd need to make this should then make I'll test my theory on #25332 which has acceptance tests that can confirm if it works or not (given that it's tricky to reproduce the issue consistently across environments) |
seems my last theory works, at least for the acceptance test. |
As part of another problem I just went through the process in #14797 (comment) :-/ Seems this is not fully fixed/back in NC 24.0.3. Sorry, I don't have any details here, I was actually trying to solve a different problem and didn't gather any logs. Maybe someone else ends up here again though, so I wanted to leave a note. 🤷 |
Since this bug is still persistent but the issue is closed, I created a new one some time ago: #29515 Would be great to get some support there to further escalate the topic to a higher priority. |
Is someone currently unable to delete/unshare a file or folder in Nextcloud in the latest version? Since I used the manual workaround, I cannot test it with the latest Nextcloud version. It would be great if someone could test the following to provide more info to the team: |
The same thing happens if you accept a share from a localhost url, that is not on same machine. Can this be looked into? |
How to use GitHub
Steps to reproduce
Expected behaviour
Unshare should work
Actual behaviour
Error message on top "error deleting file $file"
Server configuration
Nextcloud version: (see Nextcloud admin page) master
The text was updated successfully, but these errors were encountered: