Replies: 1 comment
-
|
No explanation as to why it was working and then stopped working, but the fix was the postgres.conf file had the port listed as the host port, not the container port. Nothing was changed between when it was working and when it wasn't. Removing the configuration option for the host port in the conf file for the docker resolved the issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm stumped and not even sure where to start to look for the problem on this.
I installed the whole dawarich stack yesterday and it was working fine for the entire day. About 4 AM this morning, logs show the database received a shutdown request from administrator. I don't know why or how this would have happened... but the container was still up but database wasn't responding.
I restarted the container and it comes up and eventually goes into an unhealthy state. The container and logs show it's up and working fine, but when trying to connect to the port (in this case 5435, which I changed because I already have another pgsql instance running), it just immediately closes connection. It does connect to the port, so the port is open... but the connection is closed immediately. I have two other pgsql instances on the server on different ports and both of them work fine.
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.
There's nothing in the logs that show any kind of problems. I'm stumped on what to look at next. Everything was working fine until 4:18 this morning.
Beta Was this translation helpful? Give feedback.
All reactions