-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not open file "postmaster.pid": Permission denied; continuing anyway #107
Comments
Hi, I can not help you a lot with the provided information but many thanks for the logs. It would be nice to also see your
As you can see above the correct way is to map the local volume If this is done wrong, the database will not work correctly since the way the Postgresql official container works is to run through some scripts at startup and setting some permissions. This process will not work correctly if PGDATA is not set correctly. See this link for more information. (Make sure you read this section very closely to understand it.) |
Thanks for the response this is my compose
|
It appears It's owned by 70 for some reason ? |
Just tested and all the postgres files are owned by 70:70 here.
Since postmaster.pid will be removed on a clean shutdown of the container (docker compose down) I can see no problem.
As you can see with a coordinated shutdown postmaster.pid is gone! How do you startup the container? Do you use Because you have a postmaster.pid at startup of the postgresql container I assume your container crashed. Could it be that maybe your system runs out of resources at one point and the system kills the containers resulting having the postgresql files in a undefined state? I do no longer use this project, I switched to run guacamole using podman on RHEL but anyways I think nothing is wrong, must be something related to your specific system but I think the root cause is an uncoordinated container crash. Maybe you could somehow store the logs of the container somehow to have it after the container crashed (when your web interface is not reachable)? |
I don't think the container is crashing because all of my other docker containers are fine. My Server usually automatically shuts down at night, but nothing gets corrupted. Maybe it's some user/group permission error? I probably have gotten this same error on all the other guacamole docker images but for those you couldn't see the logs of individual containers. |
Everytime guacmole starts when the server boots or after some time of not using guacamole I can't access the web gui. All I get is ERROR please contact an administrator. These are the logs but I looked inside the container and all the permissions belong to root. I am also running the compose as root.
postgres_guacamole_compose logs:
guacd_compose logs:
guacamole_compose logs:
The text was updated successfully, but these errors were encountered: