[bug] Error migrating from Pleroma #467
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#467
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
OTP
Extra details
Alpine Linux stable in a vm
Version
pleroma 2.5.0
PostgreSQL version
14.7
What were you trying to do?
I started the migration process with
su pleroma -s $SHELL -lc "./bin/pleroma_ctl update --zip-url https://akkoma-updates.s3-website.fr-par.scw.cloud/stable/akkoma-amd64-musl.zip"
.What did you expect to happen?
A successful migration to Akkoma.
What actually happened?
Upon executing the migrate (
su pleroma -s $SHELL -lc "./bin/pleroma_ctl migrate"
) command, I got these errors:I have no clue what the issue might be. Maybe it doesn't like the version of musl libc (
musl-1.2.3-r2
) installed? I've upgraded Alpine just in case. Don't know how to revert back to Pleroma either. Hope my database isn't corrupted or anything.Logs
Severity
I cannot use the software
Have you searched for this issue?
just checked that the update zip wasn't corrupted on download
which architecture are you on? standard amd64?
not an arm processor or anything?
can't say I've ever seen an error like this
yeah, regular amd64 on an old sandy bridge thinkpad. i'll try a regular install without any migrations and see if it works at all
right now i seem to have successfully reverted back to pleroma by manually copying the release folder from the zip and it's working but it's fucked up to the point the migrate command isn't working (
[info] Migrations already up
). ehhhhhhhhhhhhhok i can replicate your error in a docker container
i'm going to try building a new version to see if something hecked up on build day
updating the docker container made it work, which implies it's just an alpine compatibility issue, building on an older alpine now, give it 15 mins
built, try updating now
sorry i was asleep but i got to it now and it works :D im so happy :D