pt-agent uses wrong --socket
Bug #1251747 reported by
Kamil Dziedzic
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
pt-agent fails to sent data after installation on server where socket is placed in different location than default.
This is because pt-agent fetches default agent config from api.
Suggested fix is to create separate config on posting new agent - if agent uses different options than those in default config.
To post a comment you must log in.
Correction: it doesn't always default to /var/lib/ mysql/mysql. sock, it defaults to mysqlclientlib default which DBI/DBD-mysql use because it (pt-agent) uses host=localhost which results in preferential use of the socket (vs. host=127.0.0.1 results in use of a TCP connection). If socket var for MySQL is different than the mysqlclientlib default, then using host=localhost causes the mismatch.
See also https:/ /bugs.launchpad .net/percona- toolkit/ +bug/1248363.