Problem
Your PMM server address has changed (IP, hostname or port). The pmm-agent running on the monitored servers can't connect anymore. This guide assumes that you are on a Linux server (Ubuntu).Solution
This can be fixed by updating the configuration file (pmm-agent.yaml) and restarting pmm-agent.Here are the steps:
1. Locate the config file
Run service pmm-agent status to find the location of your pmm installation:
$ service pmm-agent status
● pmm-agent.service - pmm-agent
Loaded: loaded (/lib/systemd/system/pmm-agent.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-01-27 09:31:21 CST; 3s ago
Main PID: 2357146 (pmm-agent)
Tasks: 37 (limit: 38472)
Memory: 27.1M
CGroup: /system.slice/pmm-agent.service
├─2357146 /usr/sbin/pmm-agent --config-file=/usr/local/percona/pmm2/config/pmm-agent.yaml
We can see that the --config-file path is /usr/local/percona/pmm2/config/pmm-agent.yaml
2. Update the config file
Open pmm-agent.yaml in a text editor and update the server details.$ nano /usr/local/percona/pmm2/config/pmm-agent.yamlUpdate the address/username/password in the server block.
pmm-agent.yaml
...
server:
address: 123.456.123.456:443
username: admin
password: 123456
insecure-tls: true
...
Save the file (CTRL+O) and exit (CTRL+X)
3. Restart pmm-agent agent
Run service pmm-agent restart.The pmm-agent should now be connected to your updated pmm-server address.

Self-hosted analytics
0 comentarii:
Post a Comment