Post AQBfExKzz1P7av3bHM by shebang@freethinkers.lgbt
 (DIR) More posts by shebang@freethinkers.lgbt
 (DIR) Post #AQBDyaB3cyLMMtNJyq by shebang@freespeech.group
       2022-12-02T00:55:48.709282Z
       
       0 likes, 0 repeats
       
       Is it alive? @shebang @shebang
       
 (DIR) Post #AQBE8w3p7Y1R8Mvbpw by shebang@freethinkers.lgbt
       2022-12-02T00:57:38.947937Z
       
       0 likes, 0 repeats
       
       @shebang @shebang Yeah seems like it...:blobshrug2:
       
 (DIR) Post #AQBEGuhy27exFvVdzc by icedquinn@blob.cat
       2022-12-02T00:59:08.490702Z
       
       0 likes, 0 repeats
       
       @shebang @shebang @shebang :comfypeek:
       
 (DIR) Post #AQBEMgZ9WhKH8G8exM by shebang@freethinkers.lgbt
       2022-12-02T01:00:07.503695Z
       
       0 likes, 0 repeats
       
       @icedquinn @shebang @shebang Nope. It died again. It's spamming>Error fetching notifications: Unexpected token '<', "<html> <h"... is not valid JSONand pleroma crashed again. No errors in the log about this, of course.
       
 (DIR) Post #AQBEQqjLg2mToatRfU by shebang@freethinkers.lgbt
       2022-12-02T01:00:54.148118Z
       
       0 likes, 0 repeats
       
       @icedquinn It runs for a few minutes then barfs mysteriously
       
 (DIR) Post #AQBEUQQDQxNvNXeIfQ by icedquinn@blob.cat
       2022-12-02T01:01:35.030943Z
       
       0 likes, 0 repeats
       
       @shebang back up everything and flee to akkoma I guess? :comfycoffeewoozy:
       
 (DIR) Post #AQBEZCUMfEa7c7rnEG by shebang@freethinkers.lgbt
       2022-12-02T01:02:23.833611Z
       
       1 likes, 0 repeats
       
       @icedquinn Akkoma is unquestionably better. But I have no idea how  to smoothly migrate -- and migrating from something broken to Akkoma might just result in a broken Akkoma
       
 (DIR) Post #AQBEg0YtPGwseNEMsK by shebang@freethinkers.lgbt
       2022-12-02T01:03:37.793219Z
       
       0 likes, 0 repeats
       
       @icedquinn Yeah it just grinds the CPU for 10 minutes or so, catches up a bunch of stuff from the feed -- then dies without a clear reason why
       
 (DIR) Post #AQBElLiaAwNFiHJHQu by shebang@freethinkers.lgbt
       2022-12-02T01:04:36.016781Z
       
       0 likes, 0 repeats
       
       @icedquinn local0.err pleroma: [error] Process #PID<0.6696.1> on node :"pleroma@127.0.0.1" raised an exception ** (ArgumentError) unknown registry: Pleroma.Web.StreamerRegistry     (elixir 1.10.4) lib/registry.ex:1248: Registry.key_info!/1     (elixir 1.10.4) lib/registry.ex:458: Registry.dispatch/4unless you know what the flying fuck that shit means
       
 (DIR) Post #AQBFcpcthw8Tou9Ywq by icedquinn@blob.cat
       2022-12-02T01:14:17.360623Z
       
       0 likes, 0 repeats
       
       @shebang :revblobfoxkirbyinhale: :ablobfoxree: @shibao @lanodan
       
 (DIR) Post #AQBG8UX5fWs3fLX8vg by Prosirer@blazingopen.space
       2022-12-02T01:17:47.630252Z
       
       0 likes, 0 repeats
       
       @shebang @icedquinn Are you backing up the database then restoring on a fresh Akkoma install? PS It means that Pleroma's debugger is hot garbage and needs to be taken out.
       
 (DIR) Post #AQBGcUW0IZBIIbKXT6 by shebang@freethinkers.lgbt
       2022-12-02T01:25:19.182198Z
       
       1 likes, 0 repeats
       
       @Prosirer @icedquinn No, I'm just trying to figure out why Pleroma keeps crashing after a few minutes. I'm not switching or migrating anything at this point. Pleroma is just sitting here making me angry.
       
 (DIR) Post #AQBHEvARecsBxoZTCy by shibao@misskey.bubbletea.dev
       2022-12-02T01:32:23.020Z
       
       0 likes, 0 repeats
       
       @icedquinn@blob.cat @shebang@freethinkers.lgbt @lanodan@queer.hacktivis.me argument to one of the functions wasn't what one of them expected
       
 (DIR) Post #AQBHFbflcYspn7Y4rQ by Prosirer@blazingopen.space
       2022-12-02T01:30:17.163197Z
       
       0 likes, 0 repeats
       
       @shebang @icedquinn Okay, the error sounds a lot like this problem from a few months ago which got many Fedi admins in a bunch:https://gitlab.com/soapbox-pub/rebased/-/issues/102In which case, the fix was to add the following to prod.secret.exs:config :pleroma, :delete_context_objects, sleep_interval_ms: 3_000Might be worth a shot.
       
 (DIR) Post #AQBHejuA9Q8QYwGZbU by shebang@freethinkers.lgbt
       2022-12-02T01:37:00.568078Z
       
       0 likes, 0 repeats
       
       @Prosirer @icedquinn prod.secret?I don't have that. I think that only applies to source installs
       
 (DIR) Post #AQBHk8ramc87Pydkbg by w@arachnid.town
       2022-12-02T01:34:23.363924Z
       
       1 likes, 0 repeats
       
       @shebang @Prosirer @icedquinn Your config file then.
       
 (DIR) Post #AQBHsvbpQoLkuuSMCW by shebang@freethinkers.lgbt
       2022-12-02T01:39:32.992132Z
       
       0 likes, 0 repeats
       
       @w @Prosirer @icedquinn Yeah added it to config.exs Lets see what happens:blobshrug: Nice if this worked..
       
 (DIR) Post #AQBKQytLvtlIqt1DSS by shebang@freethinkers.lgbt
       2022-12-02T02:08:04.319624Z
       
       0 likes, 0 repeats
       
       @w @Prosirer @icedquinn nope, still dies.I'm just about ready to give up, I can't figure out what's the problem, so no way to even begin to guess what's wrong.
       
 (DIR) Post #AQBKWh9YnV4DZfK9rs by w@arachnid.town
       2022-12-02T02:05:33.642982Z
       
       0 likes, 0 repeats
       
       @shebang @Prosirer @icedquinn Maybe file an issue on the GitLab?
       
 (DIR) Post #AQBLdUxKe24Hj6Pd4q by Prosirer@blazingopen.space
       2022-12-02T02:19:25.376937Z
       
       0 likes, 0 repeats
       
       @shebang @w @icedquinn Seems like upstream has looked to solve a similar problem, where an internal process crashes and it may not be possible for a user to recover from it.https://git.pleroma.social/pleroma/pleroma/-/issues/2623But that was a year ago and nothing's happened since (Pleroma's known to be short on devs). If Pleroma can stay running long enough then a database backup would be a good idea. Also, maybe its time to say hello to Akkoma-land (it is cozy over here). For what it's worth, I've lost my instance many times so I get the butthurt.
       
 (DIR) Post #AQBM2IyELMdhnGf40O by icedquinn@blob.cat
       2022-12-02T02:26:07.580751Z
       
       0 likes, 0 repeats
       
       @Prosirer @shebang @w it should be possible to rescue the keys and data at least to do a migration without losing the instance and data :blobcatwaitwhat2:
       
 (DIR) Post #AQBQy61d1zSoG13yyG by shebang@freethinkers.lgbt
       2022-12-02T03:21:21.507066Z
       
       0 likes, 0 repeats
       
       @icedquinn @w @Prosirer Yeah, I think migration is the only possibility at this point. I'm not entirely sure what's involved though.
       
 (DIR) Post #AQBUBS82SigeR97cxc by Prosirer@blazingopen.space
       2022-12-02T03:55:11.548345Z
       
       0 likes, 0 repeats
       
       @shebang @w @icedquinn Following the commands in this link should do the trick: https://docs.akkoma.dev/develop/installation/migrating_to_akkoma/If the instance is still shaky for whatever reason, then a backup of the instance/restore on a new Akkoma install would work:https://docs.akkoma.dev/develop/administration/backup/
       
 (DIR) Post #AQBe5j3Fd7IWj4n4WO by shebang@freethinkers.lgbt
       2022-12-02T05:48:24.502289Z
       
       0 likes, 0 repeats
       
       @Prosirer @w @icedquinn Gave it a shot, but it's even more broken now. I just get a blank page.
       
 (DIR) Post #AQBeNtZRG65uYyVg1I by shebang@freethinkers.lgbt
       2022-12-02T05:51:42.352267Z
       
       0 likes, 0 repeats
       
       @Prosirer @w @icedquinn I made sure to install the front end, then also deleted the frontend config from the database.. but nope.syslog seems to report "something" is working though. But the frontend is b0rked.
       
 (DIR) Post #AQBfExKzz1P7av3bHM by shebang@freethinkers.lgbt
       2022-12-02T06:01:17.640617Z
       
       0 likes, 0 repeats
       
       @Prosirer @w @icedquinn Ok well actually a bit of progress. I have no idea whats up with the frontend. waaaaitI forgot I had some custom css in thereand .. maybe its working now? It looks like it! But we'll see if it dies again soon
       
 (DIR) Post #AQBk47rb0YNMpCxXCC by icedquinn@blob.cat
       2022-12-02T06:55:21.620374Z
       
       0 likes, 0 repeats
       
       @shebang @Prosirer @w :youmuclap: