Mastodon backups listed in a Cloudron-wide backup, but aren't actually backed up!?
-
@girish No, actually, I was just looking, saw that this app is listed in my full cloudron backup, but isn't present in the actual Minio bucket. I downloaded the individual app's backup configuration which also says it was backed up to that bucket. When I then choose to download the backup (from the apps dashboard) it starts something, then fails, and actually a get a humungusly long url on a page that says
This app is currently not responding. Please try refreshing the page in a few minutes..What in the world? Why is this app NOT getting backed up, while all the records say it is?? It can't be the S3_ENABLED=true in the env file because when i check that bucket (same Minio server) there is only the data, not the app.
Where did the app go?? If I hadn't had a full disk backup at SSDNodes I would have lost this app, and who knows what else.
A life lived in fear is a life half-lived
-
@girish No, actually, I was just looking, saw that this app is listed in my full cloudron backup, but isn't present in the actual Minio bucket. I downloaded the individual app's backup configuration which also says it was backed up to that bucket. When I then choose to download the backup (from the apps dashboard) it starts something, then fails, and actually a get a humungusly long url on a page that says
This app is currently not responding. Please try refreshing the page in a few minutes..What in the world? Why is this app NOT getting backed up, while all the records say it is?? It can't be the S3_ENABLED=true in the env file because when i check that bucket (same Minio server) there is only the data, not the app.
Where did the app go?? If I hadn't had a full disk backup at SSDNodes I would have lost this app, and who knows what else.
-
Makes me wonder if you hit a bug that I fixed last week related to s3 api copy errors. The copy fails but the backup code incorrectly flags it as a success. (https://git.cloudron.io/cloudron/box/-/commit/40bcfdba76bde24b7e9e50613b99c51889b30d00 is the fix).
-
Makes me wonder if you hit a bug that I fixed last week related to s3 api copy errors. The copy fails but the backup code incorrectly flags it as a success. (https://git.cloudron.io/cloudron/box/-/commit/40bcfdba76bde24b7e9e50613b99c51889b30d00 is the fix).
-
@scooke before that, we should determine if that is actually the bug.
Do you see the app backed up under snapshot/ ? My fix was for the situation where the upload itself succeeds (into snapshot/) but the remote copy fails (thus no timestamped directories).
-
@scooke before that, we should determine if that is actually the bug.
Do you see the app backed up under snapshot/ ? My fix was for the situation where the upload itself succeeds (into snapshot/) but the remote copy fails (thus no timestamped directories).
-
@girish I
s this /snapshot/, or /home/yellow/snapshot/? Thank you.Yes, it is in /snapshot (in the Minio bucket). Is this good?
@scooke Right, in the minio snapshot directory. So, is it also correct that there are no backups of any app, not just mastodon ?
The issue (I fixed) is that the minio URL entered in backups -> configure is incorrect. Did you put the bucket name at the end of the "minio url" ?
-
@scooke Right, in the minio snapshot directory. So, is it also correct that there are no backups of any app, not just mastodon ?
The issue (I fixed) is that the minio URL entered in backups -> configure is incorrect. Did you put the bucket name at the end of the "minio url" ?
-
@scooke Right, in the minio snapshot directory. So, is it also correct that there are no backups of any app, not just mastodon ?
The issue (I fixed) is that the minio URL entered in backups -> configure is incorrect. Did you put the bucket name at the end of the "minio url" ?
-
@girish the bucket name has its own box in which to enter. So no, i didn't add the bucket name as part of the url. But since everything else is backing up, how would this affect just the one app?
