#34454: Connection failed with error message "FATAL: password authentication
failed
for user 'user'"
-------------------------------------+-------------------------------------
Reporter: nainiu | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by nainiu):
Replying to [comment:2 Tim Graham]:
> I don't think you've provided enough details to make this ticket
actionable. I guess you will need to debug the issue further or at least
provide a minimal sample project that reproduces the problem. I guess the
issue doesn't occur with pyscopg2?
Yes, this issue does not occur in psycopg2. Currently, I have not found a
stable way to reproduce it, and I have also examined the 'conninfo'
information in psycopg\connection.py and found that it is the same every
time.
After contacting my cloud database provider, they said that the problem
may be caused by an error after connecting to the same container. I
noticed that there is an additional database connection before each error
occurs.
--
Ticket URL: <https://code.djangoproject.com/ticket/34454#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018747b04c77-ce7e3ea7-3ccb-4ff1-b40d-0f67b111db47-000000%40eu-central-1.amazonses.com.
