Postgrsql keep restarting

[xingya1822]

Name and Version

bitnami/postgresql 15.5.16

What architecture are you using?

amd64

What steps will reproduce the bug?

just install with custom values

Are you using any custom parameters or values?

global:
  imageRegistry: "172.25.128.67:9002"
image:
  registry: "172.25.128.67:9002"
  repository: bitnami/postgresql
  tag: 16.3.0-debian-12-r19
auth:
  postgresPassword: "#Fgglgy0223"
primary:
  persistence:
    size: 50Gi
    storageClass: "rook-ceph-block"
  initdb:
    scripts:
      init-user-db.sh: |
        #!/bin/bash
        echo "------- 初始化XWIKI数据库 -------"
        set -e
        export PGPASSWORD='#Fgglgy0223'
        psql -v ON_ERROR_STOP=1 --username "postgres" --dbname "postgres" <<-EOSQL
        CREATE USER xwiki with ENCRYPTED PASSWORD 'xwiki';
        CREATE DATABASE xwiki;
        GRANT ALL PRIVILEGES ON DATABASE xwiki TO xwiki;
        \c xwiki
        GRANT USAGE,CREATE ON SCHEMA public TO xwiki;
        EOSQL

What is the expected behavior?

postgresql run stablely

What do you see instead?

postgresql keep restart

Additional information

Readiness probe failed: 127.0.0.1:5432 - rejecting connections

Liveness probe failed: command "/bin/sh -c exec pg_isready -U \"postgres\" -h 127.0.0.1 -p 5432" timed out

[carrodher]

The issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a specific scenario that is not easy to reproduce on our side.

If you think that's not the case and are interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

[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.