pt-agent uses wrong --socket

Bug #1251747 reported by Kamil Dziedzic on 2013-11-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to
Won't Fix

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.

Daniel Nichter (daniel-nichter) wrote :

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= 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

summary: - pt-agent uses wrong --socket, always defaults to
- /var/lib/mysql/mysql.sock
+ pt-agent uses wrong --socket
tags: added: pt-agent
Changed in percona-toolkit:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Daniel Nichter (daniel-nichter)
milestone: none → 2.2.6
Daniel Nichter (daniel-nichter) wrote :

I'm going to close this as WontFix because it's indirectly fixed by bug 1248363. We need a default config that presumes the default socket will work. When that's not the case, the user must create a new agent config with the correct/actual socket. Now that bug 1248363 is fixed, the user can re-config the agent on-the-fly with the new socket. If this affects all their agents, they could also just change the default agent config.

Changed in percona-toolkit:
status: Confirmed → Won't Fix
milestone: 2.2.6 → none
importance: Medium → Undecided
assignee: Daniel Nichter (daniel-nichter) → nobody

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers