closing because: client sent partial pkt in startup phase

[spatialman]

Hi,

I am trying to host the pgbouncer linux container using "Azure - Web App Container" and trying connect to Azure PostgreSQL. During the startup i am getting below issues... Could someone through some light on this..
The below logs are getting emitted frequently:
LOG: closing because: client sent partial pkt in startup phase (age=0s)
WARNING: pooler error: client sent partial pkt in startup phase

Because of this, container fails to start:

Initiating warmup request to container x for site y
Waiting for response to warmup request for container x. Elapsed time = 15.2121973 sec
Waiting for response to warmup request for container x. Elapsed time = 30.4317658 sec
..
..
Container x for site y did not start within expected time limit.
Stopping site y because it failed during startup

[edbergavera]

I am having the same issue with AKS. Have you figured out a solution to this?

[iBrooks]

I am also experiencing this issue, and only when deployed to Azure. The same container runs just fine locally, but on azure I get the following:

LOG C-0x7fbcbbd17160: (nodb)/(nouser)@172.16.5.1:29265 closing because: client sent partial pkt in startup phase (age=0s)
WARNING C-0x7fbcbbd17160: (nodb)/(nouser)@172.16.5.1:29265 pooler error: client sent partial pkt in startup phase

[eulerto]

This doesn't seem a pgbouncer issue. You should ask Azure why AKS or Web App Container is sending partial packets to Azure PostgreSQL. Azure Database for PostgreSQL provides a built-in pgbouncer. It is possibly a forked version that could explain this issue.

[michaelgmcd]

Seeing this as well when trying to use AWS Fargate connecting to RDS. Not sure how to proceed.

[Tieantono]

I guess this is because Azure App Service always pinging a HTTP request to the exposed port of your container, but since the exposed port of pgbouncer is not for HTTP request, the pgbouncer won't proceed and hence the Azure App Service think that your container didn't start well.

I've tried to run the pgbouncer using https://hub.docker.com/r/bitnami/pgbounce image, and try to access it from web browser using the exposed port (6432), and the same log messages was found in my container's logs.