Name and Version bitnami/postgresql 16.1 What a

<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clip

[bitnami/posgresql] with SPIRE fails in crashloopback about charts HOT 5 CLOSED

abhinandantn commented on July 21, 2024

[bitnami/posgresql] with SPIRE fails in crashloopback

from charts.

Comments (5)

abhinandantn commented on July 21, 2024

i hit sometimes issue like below, testdb not found, on different storage system it seemed to work but on this VAST it is failing. is there a way i could generate more debug log to root cause why those testdb and necessary privileges were not given

PostgreSQL Database directory appears to contain a database; Skipping initialization

2024-04-25 17:34:14.623 UTC [1] LOG:  starting PostgreSQL 14.11 (Debian 14.11-1.pgdg120+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-04-25 17:34:14.623 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-04-25 17:34:14.624 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2024-04-25 17:34:14.714 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-04-25 17:34:15.121 UTC [27] LOG:  database system was interrupted; last known up at 2024-04-25 17:33:26 UTC
2024-04-25 17:34:16.164 UTC [27] LOG:  database system was not properly shut down; automatic recovery in progress
2024-04-25 17:34:16.285 UTC [27] LOG:  redo starts at 0/10AE1B8
2024-04-25 17:34:19.198 UTC [27] LOG:  invalid record length at 0/165ED78: wanted 24, got 0
2024-04-25 17:34:19.198 UTC [27] LOG:  redo done at 0/165ECD0 system usage: CPU: user: 0.02 s, system: 0.02 s, elapsed: 2.91 s
2024-04-25 17:34:27.517 UTC [1] LOG:  database system is ready to accept connections
2024-04-25 17:35:02.111 UTC [40] FATAL:  database "testdb" does not exist
2024-04-25 17:35:17.087 UTC [47] FATAL:  database "testdb" does not exist

from charts.

abhinandantn commented on July 21, 2024

2024-04-26 05:17:22.154 GMT [91] LOG:  database system was shut down at 2024-04-26 05:10:55 GMT
2024-04-26 05:17:22.948 GMT [1] LOG:  database system is ready to accept connections
2024-04-26 05:17:58.882 GMT [102] FATAL:  password authentication failed for user "spire"
2024-04-26 05:17:58.882 GMT [102] DETAIL:  Role "spire" does not exist.

even on bitnami spire product which uses postgresql, after helm install i see the above issue, my expectation was that spire role and spire-server db was supposed to be created as part deployment itself

from charts.

javsalgar commented on July 21, 2024

Hi,

It seems to me that the issue is being caused by the VAST filesystem. Just for checking, could you try deploying disabling persistence?

from charts.

github-actions commented on July 21, 2024

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.

from charts.

github-actions commented on July 21, 2024

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.

from charts.

Recommend Projects

[bitnami/posgresql] with SPIRE fails in crashloopback about charts HOT 5 CLOSED

Comments (5)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent