![]() Postgresql 13:09:09.10 Subscribe to project updates by watching Postgresql 13:09:09.10 Welcome to the Bitnami postgresql container Kubectl port-forward $POD_NAME 8080:9000 -n testĪnd then take a close look at the postgres pod ~ > kubectl logs -f -n test sonarqube-postgresql-0 Get the application URL by running these commands:Įxport POD_NAME=$(kubectl get pods -namespace test -l "app=sonarqube,release=sonarqube" -o jsonpath="") ⎈Happy ~/Downloads > helm install -f values.yaml -n test sonarqube sonarqube/sonarqubeġ. Successfully got an update from the "sonarqube" chart repository Hang tight while we grab the latest from your chart repositories. Namespace/test ~/Downloads > mv values.txt ~/Downloads > helm repo update This is what i did: ~/Downloads > kubectl create ns test Sadly i am not able to reproduce the described error and still think there is something wrong in the initialization of the postgresql pod. I checked the configuration of official chart installation, pg_hba.conf configurations are good to allow connections and in nf listen_addresses = '*' has been set. 08:47:45.939 GMT DETAIL: Role “sonarUser” does not exist. 08:47:45.939 GMT FATAL: password authentication failed for user “sonarUser” 08:47:37.462 GMT LOG: incomplete startup packet 08:47:35.969 GMT DETAIL: Role “sonarUser” does not exist.Ĭonnection matched pg_hba.conf line 1: “host all all 0.0.0.0/0 md5” 08:47:35.969 GMT FATAL: password authentication failed for user “sonarUser” 08:47:26.787 GMT LOG: database system is ready to accept connections 08:47:26.663 GMT LOG: database system was shut down at 08:47:03 GMT 08:47:26.636 GMT LOG: pgaudit extension initialized Sonarqube-postgresql pod is giving below error, I tried using official chart from sonarsource with which also I am facing the same issue, Helm-chart-sonarqube/charts/sonarqube at master
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |