aranym

The instance you make your account on doesn't matter, as they're federated you can see and interact with posts from anywhere else.

You can check out the Lemmy community browser to see a list of the most visited communities, then search for them in https://lemmy.world/search to subscribe/post/comment. (note: beehaw.org communities arent accessible from lemmy.world, so ignore those)

Wiped the VPS clean, new 22.04 server install.

Deployed using that installer.

Exact same issue. The lemmy container cannot reach the database and continually restarts.

It is honestly far too late for me to keep troubleshooting - I'll be back here tomorrow afternoon (CDT). Until then!

Ran those commands successfully, then the playbook again. Playbook has zero errors or warnings.

The postgres container was remade.. with the same broken database. Went into it with psql like before, did \c lemmy, same error - did not find any relations.

No errors of any kind in the ansible script. nginx is running, and it's at https://lemmy.name - I get some gateway timeout errors once in a while, but that's all. I assume this is because the lemmy container keeps restarting (as I mentioned in my original post) because it can't access the database.

\c lemmy does return "You are now connected to database "lemmy" as user "lemmy""

Running \dt after connecting returns "Did not find any relations"

Thanks for the help so far y'all, but I'm heading to sleep. Will continue working on this tomorrow.

docker exec -it lemmyname_postgres_1 /bin/bash returns the bash prompt as expected: 2ab8c789fdcd:/#

psql -U lemmy -d lemmy successfully opens psql:

psql (15.3)
Type "help" for help.

lemmy=# 

ran select name from person; from the psql shell, it does look empty (haven't created any users yet):

ERROR:  relation "person" does not exist
LINE 1: select name from person;

Yes, I can log into the psql shell on the container and connect to the database with no issue. I guess it is a network issue, I'll look into it further tomorrow

Yes, I posted the docker status info and logs from the container in my reply to Veraticus

The postgres container appears to be running.

sudo docker ps output:

CONTAINER ID   IMAGE                        COMMAND                  CREATED          STATUS                            PORTS                                 NAMES
e305af2b91c8   dessalines/lemmy-ui:0.17.4   "docker-entrypoint.s…"   27 minutes ago   Up 27 minutes                     127.0.0.1:12074->1234/tcp             lemmyname_lemmy-ui_1
3978157ef390   dessalines/lemmy:0.17.4      "/app/lemmy"             27 minutes ago   Restarting (101) 34 seconds ago                                         lemmyname_lemmy_1
626d7792534b   asonix/pictrs:0.3.1          "/sbin/tini -- /usr/…"   27 minutes ago   Up 27 minutes                     6669/tcp, 127.0.0.1:21166->8080/tcp   lemmyname_pictrs_1
65eab82adee9   mwader/postfix-relay         "/root/run"              27 minutes ago   Up 27 minutes                     25/tcp                                lemmyname_postfix_1
2ab8c789fdcd   postgres:15-alpine           "docker-entrypoint.s…"   27 minutes ago   Up 27 minutes                     5432/tcp                              lemmyname_postgres_1

Container logs: ...

PostgreSQL init process complete; ready for start up.

2023-06-18 01:57:16.112 UTC [1] LOG:  starting PostgreSQL 15.3 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-06-18 01:57:16.112 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-06-18 01:57:16.112 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-06-18 01:57:16.113 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-06-18 01:57:16.117 UTC [53] LOG:  database system was shut down at 2023-06-18 01:57:16 UTC
2023-06-18 01:57:16.123 UTC [1] LOG:  database system is ready to accept connections
2023-06-18 02:02:16.215 UTC [51] LOG:  checkpoint starting: time
2023-06-18 02:02:20.329 UTC [51] LOG:  checkpoint complete: wrote 44 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=4.110 s, sync=0.003 s, total=4.115 s; sync files=12, longest=0.002 s, average=0.001 s; distance=252 kB, estimate=252 kB

They can't be replaced in this case - unless Reddit wants to spend lots of $$$ hiring moderators. As long as they leave that power to community mods, it is impossible for them to stop this type of protest.

I do think there is a real possibility Reddit will consider this a long-term risk and replace them with paid mods.