Open elhananjair opened 1 year ago
Please verify if your cron is running properly, this background job is designed to delete shares where a file does not exist any more: https://github.com/nextcloud/server/blob/stable25/apps/files_sharing/lib/DeleteOrphanedSharesJob.php#L57
You can check the oc_jobs table for this name and check if the last_run is recent.
If it ran fine, then perhaps the file is not properly/fully deleted or in a weird state, so might need to look in the database. Maybe first run an "occ files:scan --all" to make sure the filecache is alright.
@PVince81 The cron is running properly.
I have executed occ files:scan --all
too
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.
@PVince81 this issue is about to close automagically 🙂
you have already provided the info so I should have removed the "needs info" label.
so this tells us that there is no background job that cleans up this kind of shares
this will need someone to dig into the code and implement a fix
Hi @elhananjair - Can you confirm the background job that handles these is actually running:
Either:
./occ background-job:list -l 100 | grep Orphan
Or as @PVince81 noted:
You can check the oc_jobs table for this name and check if the last_run is recent.
./occ background-job:list -l 100 | grep Orpha
This doesn't output anything.
The cron job is running fine.
You can check the oc_jobs table for this name and check if the last_run is recent.: This is the output I get checking the oc_jobs table
id | class | argument | last_run | last_checked | reserved_at | exe cution_duration | argument_hash | time_sensitive --------+-----------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------+------------+--------------+-------------+---- ----------------+----------------------------------+---------------- 167362 | OC\Security\VerificationToken\CleanUpJob | "{\"userId\":\"NCuserl\",\"subject\":\"lostpassword\",\"pp\":\"user@gmail.com\",\"notBefore\":1693895744}" | 0 | 1693375391 | 0 |
0 | 8de6d669ca4e13d0a4b62809bd933dd0 | 1
@PVince81 Hello there, time flies I see some changes on this issue, running the latest Nextcloud instance on a different server, if I share a file from one usera to userb and delete the file before the user rejects or accepts it, the share notification won't appear on the notification or on pending shares category.
But on my another Nextcloud instance which I referred to here on this issue, I still couldn't reject shares that are very old and might not even exist.
⚠️ This issue respects the following points: ⚠️
Bug description
There are pending shares listed that I haven't either rejected or accepted for a long time. When I tried to reject those shares, it shows, "Something happened. Unable to reject the share."
Those files don't exist anymore or might be moved that's the reason behind it.
Steps to reproduce
Expected behavior
Such pending shares shouldn't be shown in the first place.
Installation method
Community Manual installation with Archive
Operating system
RHEL/CentOS
PHP engine version
PHP 8.0
Web server
Apache (supported)
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
No response
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info