search

timescale / helm-charts

Configuration and Documentation to run TimescaleDB in your Kubernetes cluster
Apache License 2.0
263 stars 223 forks source link

timescaledb ha : Password does not match for user "standby" #625

Open yspassivelogic opened 11 months ago

yspassivelogic commented 11 months ago

We are using the timescale/timescaledb-ha:pg14.9-ts2.11.2-all image with the timescaledb single node helm charts (version 0.33.1) and we are experiencing issues with the master node, timescaledb-0 replicated data into timescaledb-1 replica.

We keep seeing this error

2023-10-10 16:15:57 UTC [161610]: [652578bd.2774a-3] standby@[unknown],app=[unknown] [28P01] DETAIL:  Password does not match for user "standby".
2023-10-10 16:16:02 UTC [161620]: [652578c2.27754-2] standby@[unknown],app=[unknown] [28P01] FATAL:  password authentication failed for user "standby"
2023-10-10 16:16:02 UTC [161620]: [652578c2.27754-3] standby@[unknown],app=[unknown] [28P01] DETAIL:  Password does not match for user "standby".
Connection matched pg_hba.conf line 8: "hostssl   replication     standby            all                md5"

This issue is recent - we hadn't see this issue before when we deployed 1 month ago.

We running on Google Kubernetes Engine - k8s v1.27.

To reproduce:

Deploy timescaledb single node helm chart with timescale/timescaledb-ha:pg14.9-ts2.11.2-all

Scale up to 2 pods in timescaledb.

yspassivelogic commented 11 months ago

Furthermore got this from the timescaledb replica

$ kubectl logs timescaledb-1 | grep ERROR
Defaulted container "timescaledb" out of: timescaledb, postgres-exporter, tstune (init)
2023-10-11 18:08:54,368 ERROR: Error creating replica using method pgbackrest: /etc/timescaledb/scripts/pgbackrest_restore.sh exited with code=1
yspassivelogic commented 11 months ago

any updates on this issue?

SebSa commented 10 months ago

Same problem