graphprotocol / graphprotocol/graph-node
[Bug] password authentication failed for user "postgres" / Role "postgres" does not exist.
Open
Nobody has claimed this yet.
bug
ops
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Bug report
when using docker, everything works correctly for a few hours, then Postgres starts showing an error about an account that does not exist. Tested with release 0.3.0 on ubuntu 20.04, and Docker 4.12.
Relevant log output
postgres_1 | 2023-03-24 21:42:44.141 UTC [93] FATAL: password authentication failed for user "postgres"
postgres_1 | 2023-03-24 21:42:44.141 UTC [93] DETAIL:
postgres_1 | Connection matched pg_hba.conf line 100: "host all all all scram-sha-256"
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
- Tick this box if this bug is caused by a regression found in the latest release.
- Tick this box if this bug is specific to the hosted service.
- I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
Linux
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Docker deployment described for release 0.3.0 on Ubuntu 20.04, then inspect the reported PostgreSQL authentication logs and the pg_hba.conf rule shown in the report. Done means identifying why the postgres account becomes unavailable after several hours and documenting or implementing a verified fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100