-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Postgres LOG: invalid length of startup packet #886
Comments
Is the container behind any ingress, loadbalancer, or proxy? |
Nope, it's only docker. It's driving me crazy because this same exact docker project used to work fine everywhere now it's not working anywhere! |
Yeah I imagine it's something with the host's environment. Weird that you get it on Windows and Linux, but I'm not able to reproduce the error $ docker-compose up -d
Creating network "root_default" with the default driver
Pulling db (postgres:10)...
10: Pulling from library/postgres
36d925ed8e30: Pull complete
c8b0099cd1a0: Pull complete
0bf2a548fff2: Pull complete
36e6fa05828b: Pull complete
000ab621c968: Pull complete
6855b4b63497: Pull complete
9201c39bd813: Pull complete
de19e180543b: Pull complete
b25ce2d23845: Pull complete
9a1621c579ee: Pull complete
ef3f0fd3ca11: Pull complete
f5442c57fe0c: Pull complete
72221f0ea2ce: Pull complete
432032c2a5e6: Pull complete
Digest: sha256:0ce09036f7fbaa27ab91863d8941555fc089a80ada45e1970f10a3d830d38f21
Status: Downloaded newer image for postgres:10
Creating root_db_1 ... done
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e16ce605e533 postgres:10 "docker-entrypoint.s…" 4 minutes ago Up 4 minutes 0.0.0.0:5432->5432/tcp root_db_1
$ psql -h 127.0.0.1 -U admin
Password for user admin:
psql (12.8, server 10.18 (Debian 10.18-1.pgdg90+1))
Type "help" for help.
admin=# exit
$ docker-compose logs | tail -n 5
db_1 | 2021-09-28 18:21:27.575 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
db_1 | 2021-09-28 18:21:27.577 UTC [1] LOG: listening on IPv6 address "::", port 5432
db_1 | 2021-09-28 18:21:27.580 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1 | 2021-09-28 18:21:27.602 UTC [76] LOG: database system was shut down at 2021-09-28 18:21:27 UTC
db_1 | 2021-09-28 18:21:27.611 UTC [1] LOG: database system is ready to accept connections You could also try asking over at the Docker Community Forums, Docker Community Slack, or Stack Overflow |
Nevermind, I'm still not sure what's going on but it's probably me |
Experiencing similar problem here: wasp-lang/wasp#460 . Seems related to MIT-LCP/mimic-code#684 . |
I've had the same error output when trying to connect to a PSQL server. |
For me this was solved by adding this to .helmignore: |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as duplicate.
This comment was marked as duplicate.
@meena-erian I think we have encountered the same problem, This phenomenon occurs after running for a period of time, and can be recovered by restarting. |
@liyaodev Sorry for the late reply. I ended up trying different image tags until I found a build that worked fine and I locked it. I would share with you the exact tag but it's too hard to trace back in which project I encountered this. Fortunately, most of my recent projects uses much more recent versions of Postgress and everything is working fine. |
@meena-erian Thank you very much for your reply. I haven't solved it yet. What is the latest version you said? The version I'm using |
@liyaodev Very welcome! In most of my current projects, I'm using |
That's great, I'll give it a try, thanks. |
Steps to reproduce:
Run
docker-compose up
in a folder containing the followingdocker-compose.yml
What I was expecting:
That the postgres image will work as it used to (This same docker compose file used to work just fine until recently)
What happens:
I'm unable to connect to the postgresql server and every time I try to establish a tcp connection with the server, it doesn't respond and it repeats the error:
invalid length of startup packet
Host OS: Tested on Windows 11 and Ubuntu 20 linux, same results
Output of
docker-compose up
image JSON
The text was updated successfully, but these errors were encountered: