v7.10.3 / 1.75.1 lost/erased all files from S3
-
@girish both - the bucket is empty and S3 connection is broken.
Yeah - I don’t consider that could be Cloudron issue in any way - I’ve seen the only thing that’s changed on the packaging - it’s a patch version update.
Retention policy - not on Mattermost side, but I didn’t think of that, thanks for a new vector of thoughts!
-
@potemkin_ai nah, too much drama
-
@potemkin_ai nope just regular backups
-
In my specific case, Exoscale's support was quite helpful - they checked the logs of the script that calculates the bucket size and they pointed out that the bucket was always empty.
After additional checks, I realized that Mattermost doesn't respect file's storage settings and doesn't upload files to s3, even if S3 connection works; I believe something goes wrong with using those settings which leads Mattermost to silently default to work with local storage. I understand it shall be reported upstream, but I have no capacity for that right now, so just leaving this note here for now - in case if someone will encounter this issue as well.