# Unable to setup PMM using Helm **URL:** \ **Category:** PMM 2.x\ **Tags:** pmm\ **Created:** [October 9, 2024, 5:29am UTC](https://forums.percona.com/t/unable-to-setup-pmm-using-helm/34244 "2024-10-09T05:29:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Amith](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/amith/32/18431_2.png) [@Amith](https://forums.percona.com/u/Amith)\ **Post date:** [October 9, 2024, 5:29am UTC](https://forums.percona.com/t/unable-to-setup-pmm-using-helm/34244/1 "2024-10-09T05:29:39Z")
## Description: Hello, I am trying to setup PMM on my Kubernetes cluster using helm, but the pod is not moving into ready status. ## Steps to Reproduce: Followed the instructions here to setup: ```auto https://docs.percona.com/percona-monitoring-and-management/setting-up/server/helm.html ``` ```auto helm install pmm \ --set secret.create=false --set secret.name=pmm-secret \ --set-string pmmEnv.DISABLE_UPDATES="1" \ --set service.type="LoadBalancer" \ percona/pmm ``` #Percona Monitoring and Management (PMM) > PMM 2.x # Version: ```auto NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION pmm default 1 2024-10-08 23:33:23.81268372 -0500 CDT deployed pmm-1.3.16 2.43.1 ``` ## Logs: ```auto NAME READY STATUS RESTARTS AGE pmm-0 0/1 Running 0 51m ``` ```auto Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 52m default-scheduler Successfully assigned default/pmm-0 to fdc00datah603l Normal Pulled 51m kubelet Container image "percona/pmm-server:2.43.1" already present on machine Normal Created 51m kubelet Created container pmm Normal Started 51m kubelet Started container pmm Warning Unhealthy 51m kubelet Readiness probe failed: Get "http://192.168.133.83:80/v1/readyz": dial tcp 192.168.133.83:80: connect: connection refused Warning Unhealthy 114s (x641 over 51m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 500 ``` Looking at pod logs, it looked like the issue was due to postgres not starting: ```auto 2024-10-09 04:33:28,291 INFO success: pmm-update-perform-init entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-09 04:33:28,291 INFO success: clickhouse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-09 04:33:28,291 INFO success: grafana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-09 04:33:28,292 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-09 04:33:28,292 INFO success: victoriametrics entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-09 04:33:28,292 INFO success: vmalert entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-09 04:33:28,292 INFO success: alertmanager entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-09 04:33:28,292 INFO success: vmproxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-09 04:33:28,304 INFO exited: qan-api2 (exit status 1; not expected) 2024-10-09 04:33:28,436 INFO success: pmm-managed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-09 04:33:28,639 INFO spawned: 'postgresql' with pid 54 2024-10-09 04:33:28,697 INFO exited: postgresql (exit status 2; not expected) 2024-10-09 04:33:29,428 INFO spawned: 'qan-api2' with pid 59 2024-10-09 04:33:29,553 INFO exited: qan-api2 (exit status 1; not expected) ``` PV and PVC: ```auto NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGE pmm-storage-pmm-0 Bound pvc-ad6786af-5fd4-4c6c-b86b-dc8294aea1d2 10Gi RWO managed-nfs-storage 57m ``` ```auto NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS VOLUMEATTRIBUTESCLASS REASON AGE pvc-ad6786af-5fd4-4c6c-b86b-dc8294aea1d2 10Gi RWO Delete Bound default/pmm-storage-pmm-0 managed-nfs-storage 58m ``` Any suggestions on what could be wrong here? ---
**Author:** ![Amith](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/amith/32/18431_2.png) [@Amith](https://forums.percona.com/u/Amith)\ **Post date:** [October 13, 2024, 3:45pm UTC](https://forums.percona.com/t/unable-to-setup-pmm-using-helm/34244/2 "2024-10-13T15:45:08Z")
On checking the logs further I noticed this error in /srv/logs/postgresql14.log ```auto postgres: could not access the server configuration file "/srv/postgres14/postgresql.conf": No such file or directory postgres: could not access the server configuration file "/srv/postgres14/postgresql.conf": No such file or directory postgres: could not access the server configuration file "/srv/postgres14/postgresql.conf": No such file or directory ``` On checking this location, I found that this postgres14 directory was empty ![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/5/c/5cceeaa4df00c99b7403f57764b3dffdc1438b02.png) Any help is appreciated, thanks! ---
**Author:** ![Yunus](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yunus/32/6430_2.png) [@Yunus](https://forums.percona.com/u/Yunus)\ **Post date:** [October 14, 2024, 5:05am UTC](https://forums.percona.com/t/unable-to-setup-pmm-using-helm/34244/3 "2024-10-14T05:05:39Z")
> [@Amith](#): > > postgres14 directory was empty What version of Helm and K8s are you using? ---
**Author:** ![Amith](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/amith/32/18431_2.png) [@Amith](https://forums.percona.com/u/Amith)\ **Post date:** [October 14, 2024, 5:24am UTC](https://forums.percona.com/t/unable-to-setup-pmm-using-helm/34244/4 "2024-10-14T05:24:41Z")
Hello, I am on Kubernetes v1.29.4 and Helm v3.16.2 ---
**Author:** ![Amith](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/amith/32/18431_2.png) [@Amith](https://forums.percona.com/u/Amith)\ **Post date:** [October 21, 2024, 9:21am UTC](https://forums.percona.com/t/unable-to-setup-pmm-using-helm/34244/5 "2024-10-21T09:21:35Z")
It seemed like issue was caused by a misconfigured NFS storage class. This is working now