Does it have logs?
this post was submitted on 21 Apr 2024
20 points (95.5% liked)
Selfhosted
40313 readers
185 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
db. A lot of errors here, but I think I recall reading somewhere in the issues that it doesn't matter. I'd have to double check that.
I don't think postgres having fatal errors like that is normal. I'd check the user it's running as and the permissions on the files/directories/volumes.
You have a permissions issue with pg_logical/snapshots": Permission denied. Check that your volumes exist in /var/lib/docker/container (or something close) and that the user running docker can create a test file in the local directory (likely a db directory in the docker root)
What's your docker-compose.yml look like? Especially any volume mounts
I have the folder. I chown and chmod it as it should be. Looks like it reverts back to the wrong permissions though. Don't know why.
Spot on. You can’t self host without reading app and system logs.
Try to open the web developer tools in your web browser, to look if there is anything useful. It's different for every browser but on firefox:
≡ > more tools > Web Developer tools. Look into the network tab and refresh your page and try to login again. This can sometimes give you some hints what's going wrong.
Also have you tried to log every container from the compose?
When you ls all containers do they seem healthy or does one do not start?
docker container ls -a ?
Thanks for your answer. I'm not sure what to look for in the browser's logs but here it is.
I have logs for all containers here:
db. A lot of errors here, but I think I recall reading somewhere in the issues that it doesn't matter. I'd have to double check that.
I have one container exited, mediacms_migrations, but I noticed it stopped right after the stack's setup and thought it would be used only for startup.
Here are the logs for it
It looks like db is fried, I'd assume all the permission errors prevent it from running normally. Is there a healthcheck configured?
I just spinned up the docker compose bare bone without any modification just to see if it actually works on localhost. Just a checkup to see if by default it works, and yes I can login from my host IP:PORT without any issues.
https://github.com/mediacms-io/mediacms/blob/main/docs/admins_docs.md#installation
I just changed the default port, because 80 is already used and gave the admin account a password.
Maybe this github anwser can be helpful ??
The compose stack seems not that easy to customize, In your position I would mount it bare bone a change things one/one reading through their admin docs !
My guess would be that changing the volume a few things are missing? I don't know, docker issues a hard to troubleshoot when you're not infront of the computer.
Thanks for trying. The issue you mentioned helped me before to have it spinning. I feel like I've tried everything mentioned in the docs as well as what I am aware of and capable of 😅
Yeah, sorry about that... Seems alot of python is involved.
Can you check your permission on "pg_logical/snapshots" in your folder ?
drwx------ 1 70 root 512 Apr 21 15:40 postgres_data
drwx------ 1 70 70 0 Apr 21 14:41 pg_snapshots
I manually set it to 777 several times for testing purposes, but apparently, it switches back to 700
Here is something you can work on. You could try to mount your volumes as named volume as per this docker-compose file, so that docker takes care of permissions and ownership of the files.
If I understand it correctly you want to use an external drive or a drive partition ? You can't directly use those partitions as named volume. You can also mount a SAMBA/CIF mounted volume from your external drive/drive partition or NFS (read here).
Do not change this part in the docker-compose I shared above. This files needs to be located where It can find it.
volumes:
- ./deploy/docker/local_settings.py:/home/mediacms.io/mediacms/deploy/docker/local_settings.py
This is what I would give a try. Apart from that, I can't help you any further, maybe someone else would come up with a better idea :/.
This seems like a stupid permission issue ˆˆ'. Hope you will find your way arround !
Okay so I tried again, but only changing port. It worked. I really wish I could figure out this permission issues and bond volumes. Thanks again for your help :)
Still no luck, but thanks for trying :)