-
Welcome to the Chevereto User Community!
Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.
Please keep in mind:
- This community is user-driven. Always be polite and respectful to others.
- Support development by purchasing a Chevereto license, which also gives you priority support.
- Go further by joining the Community Subscription for even faster response times and to help sustain this space
Chevereto v4.5.9 announcement
- Thread starter Rodolfo
- Start date
-
- Tags
- elevado elevado-m9
Fixed bug with FTP storage not creating date folders
FTP folder errors were being silently ignored, so missing date folders were never created. Files were uploaded to the last folder that already existed, and their URLs returned 404. Missing folders are now created, and if that fails the upload stops with an error.
FTP folder errors were being silently ignored, so missing date folders were never created. Files were uploaded to the last folder that already existed, and their URLs returned 404. Missing folders are now created, and if that fails the upload stops with an error.
Improved FTP storage error handling
FTP errors gave no reason, and one failed delete could stop the rest of the delete queue. Errors now include the message from the FTP server. Files that are already gone count as deleted, and failed deletes are logged and retried without blocking the queue.
FTP errors gave no reason, and one failed delete could stop the rest of the delete queue. Errors now include the message from the FTP server. Files that are already gone count as deleted, and failed deletes are logged and retried without blocking the queue.
Fixed bug with database update failing on older installations
Upgrading from older versions could fail with database errors. The update created the tag tables with their final structure and then tried to change them again, and it tried to drop a column that might not exist. These steps now check the database first and only run when needed.
Upgrading from older versions could fail with database errors. The update created the tag tables with their final structure and then tried to change them again, and it tried to drop a column that might not exist. These steps now check the database first and only run when needed.
Fixed bug with local storage delete queue stopping on errors
If one file in a batch couldn't be deleted from local storage, the whole batch stopped and the remaining files were left in the queue. Each file is now deleted on its own. A file that fails is retried later and no longer blocks the rest of the batch.
If one file in a batch couldn't be deleted from local storage, the whole batch stopped and the remaining files were left in the queue. Each file is now deleted on its own. A file that fails is retried later and no longer blocks the rest of the batch.
Fixed bug with SFTP storage marking failed deletes as done
SFTP storage marked every file in a batch as deleted, even when the delete failed. Those files were removed from the queue but stayed on the server, and the freed disk space was overcounted. Now only files that were actually removed, or were already gone, count as deleted. Files that fail are retried later.
SFTP storage marked every file in a batch as deleted, even when the delete failed. Those files were removed from the queue but stayed on the server, and the freed disk space was overcounted. Now only files that were actually removed, or were already gone, count as deleted. Files that fail are retried later.
Fixed bug with storage delete queue stopping when a storage is unreachable
If one storage couldn't be reached, the delete queue stopped and files on every other storage were left waiting. The unreachable storage is now skipped and retried later, and the rest of the queue keeps going.
If one storage couldn't be reached, the delete queue stopped and files on every other storage were left waiting. The unreachable storage is now skipped and retried later, and the rest of the queue keeps going.
Fixed bug with failed S3 deletes retrying forever
On S3, a file that failed to delete stayed in the queue without the attempt being counted, so it was retried forever. Each failure now counts as an attempt, the error is logged, and the file is marked as failed after a few tries.
On S3, a file that failed to delete stayed in the queue without the attempt being counted, so it was retried forever. Each failure now counts as an attempt, the error is logged, and the file is marked as failed after a few tries.
Fixed bug with single failed deletes stopping the storage delete queue
On Azure, Backblaze B2, Google Cloud, FTP and OpenStack, one failed delete stopped the whole batch, and on some of these a file that was already gone also counted as an error. Each file is now handled on its own, files that are already gone count as deleted, and failed files are retried later. OpenStack now deletes files one at a time and only removes them from the queue once they're actually deleted.
On Azure, Backblaze B2, Google Cloud, FTP and OpenStack, one failed delete stopped the whole batch, and on some of these a file that was already gone also counted as an error. Each file is now handled on its own, files that are already gone count as deleted, and failed files are retried later. OpenStack now deletes files one at a time and only removes them from the queue once they're actually deleted.
Fixed bug with OSS storage delete queue handling
The Alibaba OSS delete queue didn't handle the delete response correctly. A file in the response that didn't match a queued file could break the run, and files that failed to delete were retried forever. Files that don't match are now skipped. Failed deletes count as attempts and are retried until they're marked as failed.
The Alibaba OSS delete queue didn't handle the delete response correctly. A file in the response that didn't match a queued file could break the run, and files that failed to delete were retried forever. Files that don't match are now skipped. Failed deletes count as attempts and are retried until they're marked as failed.
Fixed bug with cron job locks not being released on errors
When a cron job failed, its lock wasn't released, so the job showed as "now locked" and was skipped until the lock expired. Locks are now always released when a job finishes, even if it fails.
When a cron job failed, its lock wasn't released, so the job showed as "now locked" and was skipped until the lock expired. Locks are now always released when a job finishes, even if it fails.
Chevereto Cloud
