# Installation pmm server 3 on k8s not successful **URL:** \ **Category:** PMM 3.x\ **Created:** [December 29, 2025, 11:26am UTC](https://forums.percona.com/t/installation-pmm-server-3-on-k8s-not-successful/39950 "2025-12-29T11:26:44Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![alexst](https://avatars.discourse-cdn.com/v4/letter/a/bb73d2/32.png) [@alexst](https://forums.percona.com/u/alexst)\ **Post date:** [December 29, 2025, 11:26am UTC](https://forums.percona.com/t/installation-pmm-server-3-on-k8s-not-successful/39950/1 "2025-12-29T11:26:44Z")
I installed pmm server3 on k8s v. 1.27 via helm chart. when i check logs ,i get k logs pmm-0 2025-12-29 10:31:15,086 INFO exited: qan-api2 (exit status 1; not expected) 2025-12-29 10:31:15,125 INFO exited: postgresql (exit status 2; not expected) 2025-12-29 10:31:15,645 INFO exited: grafana (exit status 1; not expected) 2025-12-29 10:31:16,046 INFO success: pmm-init entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-12-29 10:31:16,065 INFO success: clickhouse entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-12-29 10:31:16,065 INFO success: nginx entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-12-29 10:31:16,066 INFO success: victoriametrics entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-12-29 10:31:16,066 INFO success: vmalert entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-12-29 10:31:16,066 INFO success: vmproxy entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-12-29 10:31:16,066 INFO success: pmm-managed entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-12-29 10:31:16,088 INFO spawned: ‘qan-api2’ with pid 809 2025-12-29 10:31:16,138 INFO spawned: ‘postgresql’ with pid 814 2025-12-29 10:31:16,153 INFO exited: postgresql (exit status 2; not expected) 2025-12-29 10:31:16,741 INFO spawned: ‘grafana’ with pid 853 2025-12-29 10:31:17,124 INFO success: qan-api2 entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-12-29 10:31:17,262 INFO exited: grafana (exit status 1; not expected) 2025-12-29 10:31:18,167 INFO spawned: ‘postgresql’ with pid 917 2025-12-29 10:31:18,191 INFO exited: postgresql (exit status 2; not expected) 2025-12-29 10:31:19,555 INFO spawned: ‘grafana’ with pid 918 2025-12-29 10:31:20,159 INFO exited: grafana (exit status 1; not expected) 2025-12-29 10:31:22,094 INFO spawned: ‘postgresql’ with pid 932 2025-12-29 10:31:22,118 INFO exited: postgresql (exit status 2; not expected) 2025-12-29 10:31:23,574 INFO spawned: ‘grafana’ with pid 933 2025-12-29 10:31:24,166 INFO exited: grafana (exit status 1; not expected) 2025-12-29 10:31:27,101 INFO spawned: ‘postgresql’ with pid 952 2025-12-29 10:31:27,125 INFO exited: postgresql (exit status 2; not expected) 2025-12-29 10:31:29,104 INFO spawned: ‘grafana’ with pid 953 2025-12-29 10:31:29,713 INFO exited: grafana (exit status 1; not expected) 2025-12-29 10:31:32,330 INFO spawned: ‘postgresql’ with pid 966 2025-12-29 10:31:32,346 INFO exited: postgresql (exit status 2; not expected) ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [December 29, 2025, 6:16pm UTC](https://forums.percona.com/t/installation-pmm-server-3-on-k8s-not-successful/39950/2 "2025-12-29T18:16:35Z")
Hello @alexst, grafana is crashing because it cannot access postgresql. Why pgsql is crashing, I don’t know. You will need to exec into the pod and look at the pgsql logs in /srv/logs/ ---
**Author:** ![alexst](https://avatars.discourse-cdn.com/v4/letter/a/bb73d2/32.png) [@alexst](https://forums.percona.com/u/alexst)\ **Post date:** [December 30, 2025, 6:49am UTC](https://forums.percona.com/t/installation-pmm-server-3-on-k8s-not-successful/39950/3 "2025-12-30T06:49:55Z")
@matthewb thanks for response . cat postgresql14.log 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 ls -l /srv/postgres14/ total 0 i see that /srv/postgres14 is empty and pmm user have ownerships on it. any idea? ---
**Author:** ![alexst](https://avatars.discourse-cdn.com/v4/letter/a/bb73d2/32.png) [@alexst](https://forums.percona.com/u/alexst)\ **Post date:** [December 30, 2025, 11:43am UTC](https://forums.percona.com/t/installation-pmm-server-3-on-k8s-not-successful/39950/4 "2025-12-30T11:43:05Z")
Ok inside pod i run /usr/pgsql-14/bin/initdb -D /srv/postgres14 --auth=trust --username=postgres The files belonging to this database system will be owned by user “pmm”. This user must also own the server process. The database cluster will be initialized with locale “en\_US.utf8”. The default database encoding has accordingly been set to “UTF8”. The default text search configuration will be set to “english”. Data page checksums are disabled. fixing permissions on existing directory /srv/postgres14 … ok creating subdirectories … ok selecting dynamic shared memory implementation … posix selecting default max\_connections … 20 selecting default shared\_buffers … 400kB selecting default time zone … UTC creating configuration files … ok running bootstrap script … child process was terminated by signal 7: Bus error initdb: removing contents of data directory “/srv/postgres14” ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [December 30, 2025, 3:02pm UTC](https://forums.percona.com/t/installation-pmm-server-3-on-k8s-not-successful/39950/5 "2025-12-30T15:02:25Z")
Hey @alexst, I recommend removing the whole thing and trying again. Somewhere in the pod init process the postgres db did not get correctly initialized. I’m running PMM 3.5.0 with Helm v3 and used the following command: ```auto $ helm install pmm percona/pmm \ --namespace pmmdemo \ --set service.type=LoadBalancer \ --set pmmEnv.PMM_ENABLE_UPDATES=0 ``` ---
**Author:** ![alexst](https://avatars.discourse-cdn.com/v4/letter/a/bb73d2/32.png) [@alexst](https://forums.percona.com/u/alexst)\ **Post date:** [December 31, 2025, 10:14am UTC](https://forums.percona.com/t/installation-pmm-server-3-on-k8s-not-successful/39950/6 "2025-12-31T10:14:30Z")
I successfully installed pmm server on the cluster ,that have no config for huge pages on the nodes. can i config pmm or guess it postgress issue to ignore huge page config on the nodes?