Help Request: ./gradlew serverRun leads to PSQLException #13139
-
Environment
IntentionWhen doing Logs: https://drive.google.com/file/d/1KrQhu9FtSjS_XU1hikxgnGSBbWlEY1gj/view?usp=sharing My guess from the logs is that this is causing the issue: But, i am able to use docker desktop exec and run psql -U teammates successfully. Some other information is that i am able to access http://localhost:8080/web/front/home, but not able to login as user or adminstrator. Localhost:8080 shows HTTP ERROR 503 Service Unavailable. Some screenshots are attached:
Any help would be greatly appreciated! Resolution Attempt
Additional Information: when doing
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
@xenosf @domoberzin @mingyuanc @dishenggg any help? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Hey, did you try connecting with another tool? Or maybe trying to connect using a connection URI. If those issues still persist could you try changing username to something else. |
Beta Was this translation helpful? Give feedback.
-
Hi, thanks for all the help. After some tinkering, I discovered the error and wanted to share it here in case anyone else encounters the same issue in the future. The problem arises when a PostgreSQL service is already started using Homebrew and then a PostgreSQL container is started using Docker Compose. The program defaults to using the local PostgreSQL database from Homebrew instead of the Dockerized instance. To fix this, create the necessary role and database in the local PostgreSQL instance to keep it running. |
Beta Was this translation helpful? Give feedback.
Hi, thanks for all the help. After some tinkering, I discovered the error and wanted to share it here in case anyone else encounters the same issue in the future.
The problem arises when a PostgreSQL service is already started using Homebrew and then a PostgreSQL container is started using Docker Compose. The program defaults to using the local PostgreSQL database from Homebrew instead of the Dockerized instance.
To fix this, create the necessary role and database in the local PostgreSQL instance to keep it running.