Selfhosted

40040 readers

804 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Issues hosting Lemmy (via ansible) (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by aranym@lemmy.world to c/selfhosted@lemmy.world

22 comments fedilink hide all child comments

(Using https://github.com/LemmyNet/lemmy-ansible)

The ansible-playbook command itself connected to the VPS and completed without any errors or warnings. This is on a completely fresh VPS with Ubuntu Server 22.04.

I created all directories needed in the guide, and the only file I modified was the inventory/hosts file - filling in the username/domain for SSH, domain name, contact email and adding the location of the private key for SSH.

The guide didn't note any changes to config.hjson I needed to make, so I copied that file as requested but left it with the default content. I'm thinking if I missed something it's most likely there.

I couldn't access the web UI and with some investigation I found the dessalines/lemmy:0.17.4 (backend) container is continually restarting, apparently because it can't reach the database - sudo docker container logs <id> returns the following:

thread 'main' panicked at 'Error connecting to postgres://lemmy:PasswordRedacted@postgres:5432/lemmy', crates/db_schema/src/utils.rs:161:56

I'm not sure what to do at this point, so I would be very appreciative of any help with this issue.

you are viewing a single comment's thread
view the rest of the comments

[–] aranym@lemmy.world 1 points 1 year ago (7 children)

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.

[–] fuser@quex.cc 1 points 1 year ago (6 children)

Ok so I ran a clean install and confirmed that the database objects exist. So that's definitely the problem. Your database is munted. An interesting thing happened when I re-ran the playbook - I noticed it didn't rebuild the postgres container. Very suspicious! Let's try blowing it away completely and re-running your script:

docker stop lemmyname_postgres_1

docker rm lemmyname_postgres_1

now re run the ansible playbook and let's see if that works.

[–] aranym@lemmy.world 0 points 1 year ago (5 children)

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.

[–] aranym@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

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

load more comments (4 replies)