Post 9xCY1MrXzyXl0FdngO by jbauer@social.paritybit.ca
(DIR) More posts by jbauer@social.paritybit.ca
(DIR) Post #9xCN8lsoGys18LYjNw by jbauer@social.paritybit.ca
2020-07-18T03:41:57Z
0 likes, 0 repeats
New Blog Post: My Attempts to Fix My Mastodon Instancehttps://www.paritybit.ca/blog/my-attempts-to-fix-my-mastodon-instance"I've been having strange issues with my Mastodon instance but every attempt to diagnose, fix, or understand the issue has been met with failure. Here are the issues I've encountered and what I've tried to fix them."#100DaysToOffload
(DIR) Post #9xCN8mZhhVBJHNczFA by x@toot.icyphox.sh
2020-07-18T04:02:12Z
0 likes, 0 repeats
@jbauer How do you plan on migrating?
(DIR) Post #9xCNSQ9EnDj1W0c35k by jbauer@social.paritybit.ca
2020-07-18T04:05:44Z
0 likes, 0 repeats
@x I would basically just set up a single-user pleroma instance like I have with Mastodon then tell people to go follow me over there. After a certain amount of time I'll decommission this mastodon instance and the pleroma instance will become social.paritybit.ca
(DIR) Post #9xCOZQ4Batb5FB9Q9Y by x@toot.icyphox.sh
2020-07-18T04:18:16Z
0 likes, 0 repeats
@jbauer Ah lol, I'd assumed you'd be using a migration script. If you want, you can take a look at @alex's migrator—https://gitlab.com/soapbox-pub/migrator.
(DIR) Post #9xCP6ZShgPFnwJQWAq by jbauer@social.paritybit.ca
2020-07-18T04:24:13Z
0 likes, 0 repeats
@x @alex I did try that out on this instance just to see if it would work but encountered an error trying to export data from the Mastodon db :/ I wasn't trying very hard to get it to work though, so I will give it some more effort before resorting to just telling people to go follow me on pleroma. It would make the whole thing a lot easier if I can get it to work for me.Currently running v3.1.2 of masto and the script says it supports v2.8.4 so that might be the cause of my errors.
(DIR) Post #9xCPGKb7noTEjd1HnM by x@toot.icyphox.sh
2020-07-18T04:26:03Z
1 likes, 0 repeats
@jbauer @alex Yeah it doesn't work for me either, heh. Also, it supports only Plerasstodon (https://git.pleroma.social/alexgleason/pleroma/-/tree/plerasstodon), so probably look into that too.
(DIR) Post #9xCPH1jnPRxMWyPJmS by alex@gleasonator.com
2020-07-18T04:26:11.222507Z
0 likes, 0 repeats
@jbauer @x Maybe you forgot to put RAILS_ENV=production in front of the export command, I should document that
(DIR) Post #9xCPKT6A8hPOG1VgiO by x@toot.icyphox.sh
2020-07-18T04:26:47Z
0 likes, 0 repeats
@alex @jbauer This too!
(DIR) Post #9xCY1MPtemQRcUhiaG by jbauer@social.paritybit.ca
2020-07-18T04:42:06Z
0 likes, 0 repeats
@alex @x That worked, thanks! :DI'm going to set up a pleroma instance and see if I can successfully import it now.
(DIR) Post #9xCY1MrXzyXl0FdngO by jbauer@social.paritybit.ca
2020-07-18T05:48:55Z
0 likes, 0 repeats
@alex Ah darn. I keep running into the error:** (Mix) The task "migrator.import" could not be foundWhen trying either `sudo -Hu pleroma MIX_ENV=prod yarn pleroma import` or `sudo -Hu pleroma MIX_ENV=prod mix migrator.import` from within /opt/pleroma.The file /opt/pleroma/migrator/pleroma/lib/mix/tasks/migrator/import.ex does exist though.Sorry if I'm missing something obvious again!@x
(DIR) Post #9xCY1NMO9JDIXu4Qkq by x@toot.icyphox.sh
2020-07-18T06:04:06Z
0 likes, 0 repeats
@jbauer @alex That's precisely where I'm stuck.
(DIR) Post #9xCbQiB6BYkwDIYvoG by jbauer@social.paritybit.ca
2020-07-18T06:42:20Z
0 likes, 0 repeats
@x @alex I wrote up a quick document detailing my environment and what I did:https://ftp.paritybit.ca/masto-to-pleroma-process.txtLet me know if I should open a GitLab issue or send an email for further diagnosing, I know social media isn't really the best place for support :P
(DIR) Post #9xDCoDMA7xibsNo824 by alex@gleasonator.com
2020-07-18T13:41:14.179915Z
0 likes, 0 repeats
@jbauer @x all the yarn task does is copy the "pleroma" folder in the repo into your local Pleroma folder. See do_migration.sh for an alternative way to do it. Also look at Gulpfile.esm.js do understand what's happening when you run a yarn task.
(DIR) Post #9xDglXMmGuhbgxjcNE by jbauer@social.paritybit.ca
2020-07-18T18:41:43Z
0 likes, 0 repeats
@alex @x Hm, I'm a little confused. I followed what was in that script and I have an "/opt/pleroma/migrator" folder with both the migrated data and the "pleroma/" folder inside of it (as well as whatever else is in the git repo, I just copied the entire migrator/ folder from ~/live to /opt/pleroma). Any time I try to run the mix task though I get that error, no matter where I run it or how I try to run it.See https://ftp.paritybit.ca/masto-to-pleroma-process.txt for more detailed info. All of this is on one machine.
(DIR) Post #9xDglYIYo4vIaAllRI by alex@gleasonator.com
2020-07-18T19:16:53.396100Z
0 likes, 0 repeats
@jbauer @x /opt/pleroma/migrator/pleroma/I think this is your problem. That pleroma directory should be merged into /opt/pleroma.
(DIR) Post #9xDna20VDwUkvVmCvo by jbauer@social.paritybit.ca
2020-07-18T19:25:44Z
0 likes, 0 repeats
@alex @x I took the contents of the migrator/pleroma/ dir and copied them into /opt/pleroma/ so I now have an /opt/pleroma/lib/mix/ dir which contains migrator.ex and tasks/. However, it still gives me that error (using yarn or running mix manually).Looking at the output of the yarn command, it should execute everything as needed right (it seems to copy the export, copy the pleroma/ folder, then run mix)? Even with that I still get the error.
(DIR) Post #9xDna2YBCjQwbxX6QK by alex@gleasonator.com
2020-07-18T20:33:14.762203Z
0 likes, 0 repeats
@jbauer @x That's weird. Maybe permission issue on the files? If you have /opt/pleroma/lib/mix/tasks/migrator/import.ex, it should work.
(DIR) Post #9xEAqro8hDnNA7zTGa by jbauer@social.paritybit.ca
2020-07-19T00:41:51Z
1 likes, 0 repeats
@alex @x Hm, that's alright, I'll keep trying different things. Thanks for the help!