Description:
Hi All,
I’m trying to install PMM on Centos 7 using this command:
curl -fsSL https://www.percona.com/get/pmm | /bin/bash
and getting success result but container status is unhealthy and grafana doesn’t work. Could you please advise how to fix the issue.
Steps to Reproduce:
curl -fsSL https://www.percona.com/get/pmm | /bin/bash
Version:
percona/pmm-server:2
Logs:
2024-03-21 15:00:06,630 INFO Included extra file “/etc/supervisord.d/alertmanager.ini” during parsing
2024-03-21 15:00:06,631 INFO Included extra file “/etc/supervisord.d/dbaas-controller.ini” during parsing
2024-03-21 15:00:06,631 INFO Included extra file “/etc/supervisord.d/grafana.ini” during parsing
2024-03-21 15:00:06,631 INFO Included extra file “/etc/supervisord.d/pmm.ini” during parsing
2024-03-21 15:00:06,631 INFO Included extra file “/etc/supervisord.d/prometheus.ini” during parsing
2024-03-21 15:00:06,631 INFO Included extra file “/etc/supervisord.d/qan-api2.ini” during parsing
2024-03-21 15:00:06,631 INFO Included extra file “/etc/supervisord.d/supervisord.ini” during parsing
2024-03-21 15:00:06,631 INFO Included extra file “/etc/supervisord.d/victoriametrics.ini” during parsing
2024-03-21 15:00:06,631 INFO Included extra file “/etc/supervisord.d/vmalert.ini” during parsing
2024-03-21 15:00:06,631 INFO Included extra file “/etc/supervisord.d/vmproxy.ini” during parsing
2024-03-21 15:00:06,631 INFO Set uid to user 0 succeeded
2024-03-21 15:00:06,634 INFO RPC interface ‘supervisor’ initialized
2024-03-21 15:00:06,635 INFO supervisord started with pid 1
2024-03-21 15:00:07,637 INFO spawned: ‘pmm-update-perform-init’ with pid 13
2024-03-21 15:00:07,639 INFO spawned: ‘postgresql’ with pid 14
2024-03-21 15:00:07,641 INFO spawned: ‘clickhouse’ with pid 15
2024-03-21 15:00:07,642 INFO spawned: ‘grafana’ with pid 17
2024-03-21 15:00:07,644 INFO spawned: ‘nginx’ with pid 23
2024-03-21 15:00:07,646 INFO spawned: ‘victoriametrics’ with pid 24
2024-03-21 15:00:07,648 INFO spawned: ‘vmalert’ with pid 25
2024-03-21 15:00:07,661 INFO spawned: ‘alertmanager’ with pid 30
2024-03-21 15:00:07,665 INFO spawned: ‘vmproxy’ with pid 32
2024-03-21 15:00:07,667 INFO spawned: ‘qan-api2’ with pid 33
2024-03-21 15:00:07,669 INFO spawned: ‘pmm-managed’ with pid 34
2024-03-21 15:00:07,699 INFO exited: grafana (exit status 2; not expected)
2024-03-21 15:00:07,724 INFO exited: qan-api2 (exit status 1; not expected)
2024-03-21 15:00:07,770 INFO exited: clickhouse (exit status 232; not expected)
2024-03-21 15:00:08,169 INFO exited: pmm-update-perform-init (exit status 1; not expected)
2024-03-21 15:00:08,751 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-21 15:00:08,752 INFO spawned: ‘grafana’ with pid 81
2024-03-21 15:00:08,753 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-21 15:00:08,753 INFO success: victoriametrics entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-21 15:00:08,753 INFO success: vmalert entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-21 15:00:08,753 INFO success: alertmanager entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-21 15:00:08,753 INFO success: vmproxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-21 15:00:08,754 INFO spawned: ‘qan-api2’ with pid 83
2024-03-21 15:00:08,754 INFO success: pmm-managed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-21 15:00:08,769 INFO exited: grafana (exit status 2; not expected)
2024-03-21 15:00:08,772 INFO spawned: ‘clickhouse’ with pid 90
2024-03-21 15:00:08,777 INFO exited: qan-api2 (exit status 1; not expected)
2024-03-21 15:00:08,872 INFO exited: clickhouse (exit status 232; not expected)
2024-03-21 15:00:09,266 INFO spawned: ‘pmm-update-perform-init’ with pid 91
2024-03-21 15:00:09,742 INFO exited: pmm-update-perform-init (exit status 1; not expected)
2024-03-21 15:00:10,692 INFO spawned: ‘pmm-agent’ with pid 126
2024-03-21 15:00:11,429 INFO spawned: ‘clickhouse’ with pid 137
2024-03-21 15:00:11,431 INFO spawned: ‘grafana’ with pid 138
2024-03-21 15:00:11,433 INFO spawned: ‘qan-api2’ with pid 139
2024-03-21 15:00:11,449 INFO exited: grafana (exit status 2; not expected)
2024-03-21 15:00:11,450 INFO exited: qan-api2 (exit status 1; not expected)
2024-03-21 15:00:11,536 INFO exited: clickhouse (exit status 232; not expected)
2024-03-21 15:00:11,886 INFO spawned: ‘pmm-update-perform-init’ with pid 163
2024-03-21 15:00:11,886 INFO success: pmm-agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-21 15:00:12,381 INFO exited: pmm-update-perform-init (exit status 1; not expected)
Expected Result:
Container status: healthy and no issues when trying to open grafana login page
Actual Result:
Container status: unhealthy and 502 Bad Gateway when trying to open grafana login page
Additional Information:
CLI log:
Starting PMM server…
Created PMM Data Volume: pmm-data
Created PMM Server: pmm-server
Use the following command if you ever need to update your container by hand:
docker run -d -p 443:443 --volumes-from pmm-data --name pmm-server --restart always percona/pmm-server:2
PMM Server has been successfully setup on this system!
You can access your new server using one of the following web addresses:
address1:443/
address2:443/
address3:443/
address4:443/
The default username is ‘admin’ and the password is ‘admin’ 
Note: Some browsers may not trust the default SSL certificate when you first open one of the urls above.
If this is the case, Chrome users may want to type ‘thisisunsafe’ to bypass the warning.
Enjoy Percona Monitoring and Management!
[root@myhost:/home/]docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1e9e02688536 percona/pmm-server:2 “/opt/entrypoint.sh” 15 seconds ago Up 15 seconds (unhealthy) 80/tcp, 0.0.0.0:443->443/tcp pmm-server
b38c81dc871c percona/pmm-server:2 “/bin/true” 17 seconds ago Created pmm-data