You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During cron, when using S3 as storage backend, some transfers are not expired, since the corresponding bucket cannot be found (it probably was already deleted, it actually does not exist on S3 storage)
We expected the cronjob to just close the transfer, especially since handing the "NoSuchBucket" error already seems to be attempted in StorageCloudS3's deleteFile():
The text was updated successfully, but these errors were encountered:
WebSpider
changed the title
S3: Deleting nonexistant file causes cron to give up on transfer
S3: Deleting non-existant file causes cron to give up on transfer
Dec 29, 2023
What software is in use
filesender 2.40
What happens
During cron, when using S3 as storage backend, some transfers are not expired, since the corresponding bucket cannot be found (it probably was already deleted, it actually does not exist on S3 storage)
What did you expect
We expected the cronjob to just close the transfer, especially since handing the "NoSuchBucket" error already seems to be attempted in StorageCloudS3's deleteFile():
filesender/classes/storage/StorageCloudS3.class.php
Line 244 in fb0c6b1
The text was updated successfully, but these errors were encountered: