Random issue with creating pool

[nxsofsys]

• asyncpg version: 0.11.0
• PostgreSQL version: 10 Beta
• Python version: 3.6.1 (miniconda)
• Platform: Fedora
• Do you use pgbouncer?: No
• Did you install asyncpg with pip?: Yes
• If you built asyncpg locally, which version of Cython did you use?: -
• Can the issue be reproduced under both asyncio and
  uvloop?: yes

Hi, I have random issue with creating pool - sometimes (about one of 5 attempts) password authentication fails =(

Here is code:

import asyncio
import asyncpg

async def init():
    pool = await asyncpg.create_pool(
        "postgres://postgres:postgres@localhost:5432/postgres", min_size=10, max_size=10)

loop = asyncio.get_event_loop()
loop.run_until_complete(init())

Traceback:

Traceback (most recent call last):
  File "asyncio_test.py", line 10, in <module>
    loop.run_until_complete(init())
  File "/home/user/miniconda3/envs/backend/lib/python3.6/asyncio/base_events.py", line 466, in run_until_complete
    return future.result()
  File "asyncio_test.py", line 7, in init
    "postgres://postgres:postgres@localhost:5432/postgres", min_size=40, max_size=40)
  File "/home/user/miniconda3/envs/backend/lib/python3.6/site-packages/asyncpg/pool.py", line 344, in _async__init__
    await asyncio.gather(*connect_tasks, loop=self._loop)
  File "/home/user/miniconda3/envs/backend/lib/python3.6/site-packages/asyncpg/pool.py", line 133, in connect
    connection_class=self._pool._connection_class)
  File "/home/user/miniconda3/envs/backend/lib/python3.6/site-packages/asyncpg/connect_utils.py", line 274, in _connect_addr
    await asyncio.wait_for(connected, loop=loop, timeout=timeout)
  File "/home/user/miniconda3/envs/backend/lib/python3.6/asyncio/tasks.py", line 352, in wait_for
    return fut.result()
asyncpg.exceptions.InvalidPasswordError: password authentication failed for user "postgres"

Postgres log:

[12683] [5946c2a0.318b] [2017-06-18 21:12:48.687 MSK] [0]: FATAL:  password authentication failed for user "postgres"
[12683] [5946c2a0.318b] [2017-06-18 21:12:48.687 MSK] [0]: DETAIL:  Password does not match for user "postgres".
	Connection matched pg_hba.conf line 92: "host	all		all		::/0			md5"

Of course, it may be issue of Postgresql 10 beta.
Thanks.

[lelit]

Yes, I'm hitting the same problem, trying out PG 10beta1. Maybe unrelated, but PG emits the following immediately before the error:

2017-06-29 11:24:56.001 UTC [168] LOG:  incomplete startup packet
2017-06-29 11:24:56.023 UTC [174] LOG:  incomplete startup packet
2017-06-29 11:24:56.042 UTC [180] LOG:  incomplete startup packet
2017-06-29 11:24:56.047 UTC [182] FATAL:  password authentication failed for user "user"
2017-06-29 11:24:56.047 UTC [182] DETAIL:  Password does not match for user "user".

[1st1]

Can you guys reproduce this with stable Postgres?

[lelit]

I tried, but was unable to unfortunately. In the DB tests suite of my application, all is good with 9.6.3, while with PG10b1 it never finishes correctly, at least one out of the more of 70 tests fails, never at the same point.

[lelit]

Of course I'm willing to try harder, if you have some hint on how to dig further.

[dpnova]

FWIW I've noticed this error lately too in a config that was working fine. I see this post is about 5 days old and the last update on the postgres dockerhub is 6 days ago.

Please see the issue referring to this one for my fix.. not sure if it's relevant here.

[lelit]

FYI, the same happens against the PG10b2 hub.docker.com official image.

[lelit]

I spent a few more hours trying to distill a recipe to reproduce the problem, and this is the result. I hope it at least helps in determining if the problem is with the PG beta image or not.

[1st1]

Thank you very much, @lelit! We'll take a look at this in detail soon.

[elprans]

@lelit This seems to be an issue with the docker image. I could not reproduce on a locally built version of PostgreSQL 10 beta 2.

[lelit]

Ok, thank you both!

[lelit]

FYI, I posted the recipe (augmented with an alternative the uses plain docker) also on the docker-library/postgres #308.

[lelit]

Uhm, the problem is still there in PG10b3.

[dpnova]

FYI I'm convinced this is an issue with the image and not clients. I was using nodejs at work when I reported the issue, but now using asyncpg in my own personal thing and the image is ok if password isn't set.