[bitnami/postgresql-ha] install failed

[emptyworld0]

Name and Version

bitnami/postgresql-ha 10.0.6

What architecture are you using?

arm64

What steps will reproduce the bug?

1. In mac m2 chip os 13.0 (22A380). I use minikube single node cluster.

helm upgrade --install postgresql-ha bitnami/postgresql-ha -n ${namespace} \
 --set postgresql.password="${postgresql_password}" \
 --set postgresql.repmgrPassword="${repmgr_password}" \
 --set pgpool.adminPassword="${pgpool_admin_password}" \
 --version 10.0.6

Are you using any custom parameters or values?

NO

What is the expected behavior?

postgresql-ha-postgresql-1 and postgresql-ha-pgpool-59f8bb9748-4b425 should running but it failed

What do you see instead?

I've delete minikube cluster and install bitnami in a fresh cluster. I get

NAME                                    READY   STATUS             RESTARTS       AGE
postgresql-ha-pgpool-59f8bb9748-4b425   0/1     CrashLoopBackOff   6 (116s ago)   12m
postgresql-ha-postgresql-0              1/1     Running            0              12m
postgresql-ha-postgresql-1              0/1     CrashLoopBackOff   6 (3m3s ago)   12m
postgresql-ha-postgresql-2              1/1     Running            0              12m

I run kubectl describe pod postgresql-ha-postgresql-1 -n yatai-system

Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  15m   default-scheduler  0/1 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
  Normal   Scheduled         15m   default-scheduler  Successfully assigned yatai-system/postgresql-ha-postgresql-1 to minikube
  Normal   Pulling           15m   kubelet            Pulling image "docker.io/bitnami/postgresql-repmgr:15.1.0-debian-11-r0"
  Normal   Pulled            14m   kubelet            Successfully pulled image "docker.io/bitnami/postgresql-repmgr:15.1.0-debian-11-r0" in 4.534s (1m3.145s including waiting)
  Warning  Unhealthy         13m   kubelet            Liveness probe failed: psql: error: connection to server at "127.0.0.1", port 5432 failed: Connection refused
           Is the server running on that host and accepting TCP/IP connections?
  Normal   Created    13m (x3 over 14m)     kubelet  Created container postgresql
  Normal   Started    13m (x3 over 14m)     kubelet  Started container postgresql
  Normal   Pulled     12m (x3 over 13m)     kubelet  Container image "docker.io/bitnami/postgresql-repmgr:15.1.0-debian-11-r0" already present on machine
  Warning  BackOff    5m18s (x34 over 13m)  kubelet  Back-off restarting failed container postgresql in pod postgresql-ha-postgresql-1_yatai-system(0fcbd3c5-d92a-40f8-9f38-7ce8f558c8b3)
  Warning  Unhealthy  22s (x17 over 14m)    kubelet  Readiness probe failed: psql: error: connection to server at "127.0.0.1", port 5432 failed: Connection refused
           Is the server running on that host and accepting TCP/IP connections?

kubectl logs -f postgresql-ha-postgresql-1 -n yatai-system

postgresql-repmgr 10:45:16.89
postgresql-repmgr 10:45:16.92 Welcome to the Bitnami postgresql-repmgr container
postgresql-repmgr 10:45:16.93 Subscribe to project updates by watching https://github.com/bitnami/containers
postgresql-repmgr 10:45:16.95 Submit issues and feature requests at https://github.com/bitnami/containers/issues
postgresql-repmgr 10:45:16.97
postgresql-repmgr 10:45:17.13 INFO  ==> ** Starting PostgreSQL with Replication Manager setup **
postgresql-repmgr 10:45:17.30 INFO  ==> Validating settings in REPMGR_* env vars...
postgresql-repmgr 10:45:17.34 INFO  ==> Validating settings in POSTGRESQL_* env vars..
postgresql-repmgr 10:45:17.36 INFO  ==> Querying all partner nodes for common upstream node...
postgresql-repmgr 10:45:30.20 INFO  ==> Auto-detected primary node: 'postgresql-ha-postgresql-0.postgresql-ha-postgresql-headless.yatai-system.svc.cluster.local:5432'
postgresql-repmgr 10:45:30.26 INFO  ==> Preparing PostgreSQL configuration...
postgresql-repmgr 10:45:30.30 INFO  ==> postgresql.conf file not detected. Generating it...
postgresql-repmgr 10:45:31.42 INFO  ==> Preparing repmgr configuration...
postgresql-repmgr 10:45:31.50 INFO  ==> Initializing Repmgr...
postgresql-repmgr 10:45:31.55 INFO  ==> Waiting for primary node...
postgresql-repmgr 10:45:37.83 INFO  ==> Rejoining node...
postgresql-repmgr 10:45:37.88 INFO  ==> Cloning data from primary node...

kubectl logs -f postgresql-ha-pgpool-59f8bb9748-4b425 -n yatai-system

2024-01-15 10:41:22.325: main pid 1: LOG:  Backend status file /opt/bitnami/pgpool/logs/pgpool_status does not exist
2024-01-15 10:41:22.328: main pid 1: LOG:  health_check_stats_shared_memory_size: requested size: 12288
2024-01-15 10:41:22.328: main pid 1: LOG:  memory cache initialized
2024-01-15 10:41:22.328: main pid 1: DETAIL:  memcache blocks :64
2024-01-15 10:41:22.329: main pid 1: LOG:  allocating (144190784) bytes of shared memory segment
2024-01-15 10:41:22.329: main pid 1: LOG:  allocating shared memory segment of size: 144190784
2024-01-15 10:41:22.651: main pid 1: LOG:  health_check_stats_shared_memory_size: requested size: 12288
2024-01-15 10:41:22.655: main pid 1: LOG:  health_check_stats_shared_memory_size: requested size: 12288
2024-01-15 10:41:22.655: main pid 1: LOG:  memory cache initialized
2024-01-15 10:41:22.655: main pid 1: DETAIL:  memcache blocks :64
2024-01-15 10:41:22.722: main pid 1: LOG:  pool_discard_oid_maps: discarded memqcache oid maps
2024-01-15 10:41:22.737: main pid 1: LOG:  Setting up socket for 0.0.0.0:5432
2024-01-15 10:41:22.737: main pid 1: LOG:  Setting up socket for :::5432
2024-01-15 10:41:22.848: main pid 1: LOG:  find_primary_node_repeatedly: waiting for finding a primary node
2024-01-15 10:41:26.012: child pid 362: WARNING:  failed to connect to PostgreSQL server, getaddrinfo() failed with error "Name or service not known"
2024-01-15 10:41:26.012: child pid 362: LOG:  failed to create a backend 1 connection
2024-01-15 10:41:26.012: child pid 362: DETAIL:  skip this backend because because failover_on_backend_error is off and we are in streaming replication mode and node is standby node
2024-01-15 10:41:29.092: main pid 1: WARNING:  failed to connect to PostgreSQL server, getaddrinfo() failed with error "Name or service not known"
2024-01-15 10:41:29.094: main pid 1: LOG:  find_primary_node: make_persistent_db_connection_noerror failed on node 1
2024-01-15 10:41:31.002: child pid 407: WARNING:  failed to connect to PostgreSQL server, getaddrinfo() failed with error "Name or service not known"
2024-01-15 10:41:31.003: child pid 407: LOG:  failed to create a backend 1 connection
2024-01-15 10:41:31.003: child pid 407: DETAIL:  skip this backend because because failover_on_backend_error is off and we are in streaming replication mode and node is standby node

Additional information

No response

[javsalgar]

Hi,

Could you launch the chart with postgresql.image.debug=true? this may provide more insight on the issue

[Evsio0n]

HI, Here I comes same issue here on linux.

[javsalgar]

Did you try enabling the debug value?

[github-actions[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions[bot]]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.