Unable to load PMM dash board with PMMVersion: 2.8.0
Description
How to test
How to document
Attachments
- 30 Jun 2020, 03:01 PM
- 30 Jun 2020, 03:01 PM
- 30 Jun 2020, 03:01 PM
- 30 Jun 2020, 03:01 PM
Activity
Lalit Choudhary July 13, 2020 at 8:18 AM
In case you need further help, you may ask this question on our PMM forum,
https://forums.percona.com/categories/percona-monitoring-and-management
Lalit Choudhary July 13, 2020 at 8:17 AM
@Jayabharath
I do not think this is a bug with PMM and more about AWS ELB configuration.
you may refer following,
https://sheamunion.com/aws-elb-target-group-health-check-nginx
Jayabharath July 11, 2020 at 8:18 AM
Hi Lalit,
Our EBL looking health_check file in root dir, so in new pmm.conf could not find the document root dir so added for testing but still not working, we tried without this also but no luck.
Error logs: --> cat /srv/logs/nginx.error.log
2020/07/11 07:53:00 [error] 28203#28203: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "POST /agent.Agent/Connect HTTP/2.0", subrequest: "/auth_request", upstream: "http://127.0.0.1:7772/auth_request", host: "127.0.0.1"
2020/07/11 07:53:00 [error] 28203#28203: *1 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: _, request: "POST /agent.Agent/Connect HTTP/2.0", host: "127.0.0.1"
2020/07/11 07:53:14 [error] 28203#28203: *39 connect() failed (111: Connection refused) while connecting to upstream, client: 132.10.0.10, server: _, request: "GET /qan-api/agents/5ab902ee0646482f6fd1e6a3f28e78c4/data HTTP/1.1", subrequest: "/auth_request", upstream: "http://127.0.0.1:7772/auth_request", host: "pmmserver01.aws.com:8080"
2020/07/11 07:53:14 [error] 28203#28203: *39 auth request unexpected status: 502 while sending to client, client: 132.10.0.10, server: _, request: "GET /qan-api/agents/5ab902ee0646482f6fd1e6a3f28e78c4/data HTTP/1.1", host: "pmmserver01.aws.com:8080"
2020/07/11 07:53:15 [error] 28203#28203: *41 connect() failed (111: Connection refused) while connecting to upstream, client: 10.102.113.141, server: _, request: "GET /qan-api/agents/c9ed1e03cb69498e6e36cde628561ccb/data HTTP/1.1", subrequest: "/auth_request", upstream: "http://127.0.0.1:7772/auth_request", host: "pmmserver01.aws.com:8080"
2020/07/11 07:53:15 [error] 28203#28203: *41 auth request unexpected status: 502 while sending to client, client: 10.102.113.141, server: _, request: "GET /qan-api/agents/c9ed1e03cb69498e6e36cde628561ccb/data HTTP/1.1", host: "pmmserver01.aws.com:8080"
2020/07/11 07:53:15 [error] 28203#28203: *43 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /v1/readyz HTTP/1.1", subrequest: "/auth_request", upstream: "http://127.0.0.1:7772/auth_request", host: "127.0.0.1"
2020/07/11 07:53:15 [error] 28203#28203: *43 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: _, request: "GET /v1/readyz HTTP/1.1", host: "127.0.0.1"
2020/07/11 07:53:17 [error] 28203#28203: *5 upstream prematurely closed connection while reading upstream, client: 127.0.0.1, server: _, request: "POST /agent.Agent/Connect HTTP/2.0", upstream: "grpc://127.0.0.1:7771", host: "127.0.0.1"
2020/07/11 07:53:17 [error] 28203#28203: *12 upstream prematurely closed connection while reading upstream, client: 132.88.5.308, server: _, request: "POST /agent.Agent/Connect HTTP/2.0", upstream: "grpc://127.0.0.1:7771", host: "pmmserver01.aws.com"
2020/07/11 07:53:17 [error] 28203#28203: *45 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "POST /agent.Agent/Connect HTTP/2.0", subrequest: "/auth_request", upstream: "http://127.0.0.1:7772/auth_request", host: "127.0.0.1"
2020/07/11 07:53:17 [error] 28203#28203: *45 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: _, request: "POST /agent.Agent/Connect HTTP/2.0", host: "127.0.0.1"
2020/07/11 07:53:17 [error] 28203#28203: *23 connect() failed (111: Connection refused) while connecting to upstream, client: 132.88.5.380, server: _, request: "GET /health_check HTTP/1.1", subrequest: "/auth_request", upstream: "http://127.0.0.1:7772/auth_request", host: "132.88.5.308:8080"
2020/07/11 07:53:17 [error] 28203#28203: *23 auth request unexpected status: 502 while sending to client, client: 132.88.5.380, server: _, request: "GET /health_check HTTP/1.1", host: "132.88.5.308:8080"
Lalit Choudhary July 7, 2020 at 9:48 AM
Hi @Jayabharath
Thank you for the report.
After comparing default install nginx.conf and the nginx.conf not the same, in your case following is the additional entry in nginx.conf
#added by jana
root /usr/share/nginx/html;
##Why you are adding this?
Details
Details
Assignee
Reporter
Priority
High
Hi Team,
We installed PMMVersion: 2.8.0 docker based setup, But unable to open the PMM2 dashboard.
After investigation could not find document root in ngnix.conf and seeing error in nginx error log.
Error:
2020/06/30 14:11:57 [emerg] 424#424: unknown "realm" variable
2020/06/30 14:13:00 [warn] 18#18: "ssl_stapling" ignored, issuer certificate not found for certificate "/srv/nginx/certificate.crt"
Please find the attached error/access logs and config files.
Kindly suggest a forward way to fix this issue.
Dashboard error:
This page isn't working
dev-pmm01.copt.xyz.com is currently unable to handle this request.
HTTP ERROR 503