First of all, mea culpa for deleting the S3 bucket in use for phorge… (more of that I deleted the AWS account, thinking I had no AWS dependency anymore while retaining phorge on AWS)
So, I'm now stuck in a limbo for missing files, profile images (it seems that uploading same file again doesn't work to restore the previous profile image), etc etc. I'm fine with losing it but it seems that there's some more gotcha for staying in limbo, so is there some ways to escape from the limbo without… starting from scratch?
Sorry for the late reply; was busy IRL.
- Call Amazon: It's been few months (yes, I didn't really access the site for few months, given it was mostly for my personal task DB and I had other problems to deal with)
- StackTrace: P19 (this one with a bit different context (I'll post below at avivey's answer) but same one with the error.log)
Now reading thru the log I guess it might be having a bad time with R2's S3 api (or B2 for that matter because I saw the same error string over there) and the Phorge's S3 api client, but not sure if that's really a task (not that I can file one anyway)…
While thinking of this I thought of installing phorge at my home server (so I can start fresh — again, after all, I was using it mostly for 'this is a big list of 'things I should be doing but ended up 'NOPE'' personal phab) but caught with … php8 deprecation warning became 'Fatal' so I'm probably going to stick with status quo for a while more.
It kinds of depends on exactly which limbo you're in, but there's some tools in bin/ to help you recover.
bin/files rebuild looks like it mostly recreates mime data from actual file content, but bin/files compact has a chance of actually recovering the broken files if you re-upload them.
bin/cache purge has some caches that might help from clearing - specifically builtin-file.
bin/garbage might help collect metadata of broken files.
Hey, the result of the commands:
- bin/files rebuild — as soon as the tool enters the pre-doomsday files (I mean the original S3 files), it emits the following error and kills itself: P19. (As said above) sorta thinking it might be something with Cloudflare R2's S3 API and Phorge's S3 API client but not sure)
- compact — did nothing. Every counter at 0.
- cache purge — it did work well at least to rebuild the builtin-files. Much better.
- garbage collection also did nothing.
You could also try deleting the files from db using bin/remove, which will at least remove them from limbo... assuming you know which files are missing their data.
The "not a string" error is probably because the data is null.