Failed to register pmm-agent on PMM Server

Percona Monitoring and Management (PMM) PMM 2.x
1

Hi Team- Greetings, i’ve deployed perconaxtradb cluster with proxysql and pmm enbled using helm chart(percona-helm-charts/values.yaml at main · percona/percona-helm-charts · GitHub where proxysql and pmm enabled) in k8s. and then hitting this error “Checking local pmm-agent status…
pmm-agent is not running.
Registering pmm-agent on PMM Server…
Failed to register pmm-agent on PMM Server: Post “https://monitoring-service:443/v1/management/Node/Register”: dial tcp: lookup monitoring-service on x.x.x.x:xx: no such host.
pmm-agent setup exited with 1.” inside the pmm-client container logs. is there any documentation for me to follow to deploy using helm? or how can i resolve above since i did not get any info from internet. Do i have to install the pmm-server helm before deploying the above(pxc-db with helm)? please help. Thank you

2

Hi @ajay

Please check the PMM2 Port is opened or not?
Check the firewall and selinux disabled or not?
Are you using SSL ?

Please share us the commands you are using?

2 Likes
3

Hi @Naresh9999 , Thank you so much for responding. So basically it was deployed with helm in k8s and in the values.yaml file of pxc-db i have enabled the pmm to be true
pmm:
enabled: true
image:
repository: percona/pmm-client
tag: 2.23.0
serverHost: monitoring-service
serverUser: admin
resources:
requests:
memory: 150M
cpu: 300m
limits: {}
looks like the above just spinning up a pmm-client as a side car. not pmm-server as per above code. and yes SSL is enabled.

commands:
helm install -name cluster-operator -n pxc -f values.yaml .
helm install -name cluster1 -n pxc -f values.yaml .
kubectl logs cluster1-pxc-db-pxc-0 -c pmm-client -n percona

pmm-agent is not running.
Registering pmm-agent on PMM Server…
Failed to register pmm-agent on PMM Server: Post “https://monitoring-service:443/v1/management/Node/Register”: dial tcp: lookup monitoring-service on x.x.x.x:xx: no such host.
pmm-agent setup exited with 1.”

operator logs: kubectl logs -f cluster-operator-pxc-operator-58598dd796-bwgsz -n percona

{“level”:“error”,“ts”:1643200298.3914824,“logger”:“controller-runtime.manager.controller.perconaxtradbcluster-controller”,“msg”:“Reconciler error”,“name”:“cluster1-pxc-db”,“namespace”:“percona”,“error”:“pxc upgrade error: failed to apply changes: failed to wait pod: reach pod wait limit”,“errorVerbose”:"reach pod wait limit\ngithub.com/percona/percona-xtradb-cluster-operator/pkg/controller/pxc.retry\n\t/go/src/github.com/percona/percona-xtradb-cluster-operator/pkg/controller/pxc/upgrade.go:414\ngithub.com/percona/percona-xtradb-cluster-operator/pkg/controller/pxc.(*ReconcilePerconaXtraDBCluster).

1 Like
4

@ajay I’m hitting this issue, were you able to get it working?
I am using helm to deploy both Percona db cluster and PMM
Failed to register pmm-agent on PMM Server: Post " https://pmm-server-service:443/v1/management/Node/Register ": dial tcp: lookup pmm-server-service on *****:53: no such host.

PMM is enabled as following in the PerconaServerMongoDB:

 pmm:
    enabled: true
    serverHost: pmm-server-service

PMM server Service is with following config:

# Source: pmm-server/templates/svc.yaml
kind: Service
apiVersion: v1
metadata:
  name: "pmm-server-service"
  labels:
    component: pmm
    app: pmm-server
    chart: "pmm-server-2.26.1"
    release: "pmm-server"
    heritage: "Helm"
spec:
  ports:
    - name: https
      protocol: TCP
      port: 443
      targetPort: 443
  selector:
    component: pmm
    app: pmm-server
  type: "ClusterIP"
1 Like