Post AIoBBNRfTpYIW2J3OS by cjd@mastodon.social
(DIR) More posts by cjd@mastodon.social
(DIR) Post #AIo6JK3NTVrmXfuj4a by cjd@mastodon.social
2022-04-25T11:43:51Z
0 likes, 0 repeats
Pleroma Q:I'm getting:13:38:47.821 [info] Postgrex.Protocol (#PID<0.928.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.1040.0> exitedand then a crash running `mix phx.server`Connection to postgres works, postgres says:STATEMENT: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1)Then:DEBUG: unexpected EOF on client connectionIdeas ?
(DIR) Post #AIo6JKdXJ4n2LopbQu by cjd@mastodon.social
2022-04-25T11:47:06Z
0 likes, 0 repeats
Hmm, now it's still crashing but without the ConnectionError.Just this:13:44:37.240 [notice] Application pleroma exited: exited in: Pleroma.Application.start(:normal, []) ** (EXIT) an exception was raised: ** (RuntimeError) could not lookup Ecto repo Pleroma.Repo because it was not started or it does not exist
(DIR) Post #AIo6JLHau8pgM3Zas4 by helene@p.helene.moe
2022-04-25T12:06:50.890143Z
0 likes, 0 repeats
@cjd could it be a migration issue? (though i think it's done automatically, not sure)
(DIR) Post #AIo6QCEQxDpeJKMZRw by cjd@mastodon.social
2022-04-25T12:07:49Z
1 likes, 0 repeats
@helene New db so there's really no reason it should be having migration issues...
(DIR) Post #AIo6hiLOoYgapPyT56 by AIaYYAle4i1uKmKpqy.gme@bofh.social
2022-04-25T12:11:10.813529Z
0 likes, 0 repeats
@cjd Did you complete the step to setup the systemd service? If so, try rebooting the server.
(DIR) Post #AIo7RsZX7SXfs2bASO by a1ba@expired.mentality.rip
2022-04-25T12:19:34.758591Z
1 likes, 0 repeats
@pleb ultra pleroma pro tip:just create an alias to run pleroma from user pleroma and always set MIX_ENV=prod.$ alias pleromaalias pleroma='sudo -Hu pleroma MIX_ENV=prod':)Also, @cjd, double check that the db address, user and password in prod.secret.exs are correct, and that the role exist in postgres.
(DIR) Post #AIo7jiMJpX8bPKvEPY by a1ba@expired.mentality.rip
2022-04-25T12:22:48.294305Z
0 likes, 0 repeats
@cjd can you post full pleroma log?
(DIR) Post #AIo86OnuhWdDQ4e7cm by cjd@mastodon.social
2022-04-25T12:24:35Z
0 likes, 0 repeats
@a1ba Just what comes to the console when running phx.server or should I find it somewhere ?
(DIR) Post #AIo86RBjpusSoXoB2O by a1ba@expired.mentality.rip
2022-04-25T12:26:53.378602Z
0 likes, 0 repeats
@cjd yes, phx.server output.Also, did you execute?sudo -Hu postgres psql -f config/setup_db.psqlsudo -Hu pleroma MIX_ENV=prod mix ecto.migrate?
(DIR) Post #AIo8moaNEgV7XgXRei by cjd@mastodon.social
2022-04-25T12:13:40Z
0 likes, 0 repeats
@gme Alpine machine, so no systemd.Crashes running: MIX_ENV=prod mix phx.serverI created the db and ran the migration.
(DIR) Post #AIo8mp7LG6s9Bvxm2i by AIaYYAle4i1uKmKpqy.gme@bofh.social
2022-04-25T12:34:30.059914Z
0 likes, 0 repeats
@cjd Oh. I only use debian. Hmm. I’d still try rebooting then. If you followed the instructions for alpine then I assume you setup whatever you need to setup so the services will start automatically. Sounds like something hasn’t started yet.
(DIR) Post #AIo9T9WDnVuOcxmh7o by cjd@mastodon.social
2022-04-25T12:39:54Z
2 likes, 0 repeats
@gme I try to avoid rebooting
(DIR) Post #AIo9eILpIdApCpEeMC by AIaYYAle4i1uKmKpqy.gme@bofh.social
2022-04-25T12:44:10.481755Z
0 likes, 0 repeats
@cjd Suit yourself. Just telling you what’s worked for me in the past when I’ve seen those errors. ;-)
(DIR) Post #AIoA8B0dA2Et7gZO52 by thatguyoverthere@charlestown.social
2022-04-25T12:49:40.426888Z
0 likes, 0 repeats
@cjd not specific to pleroma but here’s your error in an elixir discussion with a proposed solution that worked for the app on question. I haven’t taken the dive to learn elixir, but seems maybe related.https://elixirforum.com/t/runtimeerror-could-not-lookup-ecto-repo-repo-because-it-was-not-started-or-it-does-not-exist/27935We just solved this problem. In our case, the test database had unexpected data. (!!) It might have had a slightly different schema than expected.The fix was to recreate the test database with MIX_ENV=test mix ecto.reset.It was a frustrating experienceThis seems to have helped the OP but not everyone but if maybe there is unexpected data in the db this could help. Are you able to run queries on the db via psql?
(DIR) Post #AIoAFozctt4v9pkHK4 by a1ba@expired.mentality.rip
2022-04-25T12:50:52.546560Z
1 likes, 0 repeats
@cjd can you also post prod.secret.exs?Do you use OTP or build from source?Do you store configuration in db or in text file?
(DIR) Post #AIoAi51IuDQayO0MAy by ceruds@bae.st
2022-04-25T12:56:10.443900Z
0 likes, 0 repeats
@a1ba @cjd It looks like, cjd uses from source code.
(DIR) Post #AIoBBNRfTpYIW2J3OS by cjd@mastodon.social
2022-04-25T12:57:20Z
0 likes, 0 repeats
@a1ba Check the bottom of the pad..Note:log: :debug,show_sensitive_data_on_connection_error: trueAre added by me (trying to debug).Followed these instructions: https://docs-develop.pleroma.social/backend/installation/alpine_linux_en/#installation up to the end of Install PleromaBE.However I put it in /home/pleroma and symlinked it to /opt/pleroma, in case that's relevant.
(DIR) Post #AIoBBPvsEUu0EISCki by a1ba@expired.mentality.rip
2022-04-25T13:01:24.334970Z
0 likes, 0 repeats
@cjd oh I'm blind.try to set this:config :pleroma, configurable_from_database: trueto false
(DIR) Post #AIoCTUHSu9hAskjXaC by cjd@mastodon.social
2022-04-25T13:07:54Z
0 likes, 0 repeats
@a1ba Wondering if it might be better to just run pleroma in a docker and volume-mount the media dir. I like to be able to hack on it as needed, but for fragile things I tend to prefer keeping them in their own bubbles...
(DIR) Post #AIoCTWnnWukMhbsOG0 by a1ba@expired.mentality.rip
2022-04-25T13:15:43.335349Z
0 likes, 0 repeats
@cjd pleroma isn't THAT fragile usually, at least on installing.I don't know what happened here.