pt-query-digest crashes if processlist has extra columns
Bug #883098 reported by
Usu
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Fix Released
|
Medium
|
Brian Fraser |
Bug Description
# pt-query-digest --processlist localhost,
Pipeline process 2 (Processlist) caused an error: Can't use string ("1319806283") as a HASH ref while "strict refs" in use at /usr/bin/
Pipeline process 2 (Processlist) caused an error: Can't use string ("1319806283") as a HASH ref while "strict refs" in use at /usr/bin/
[...]
# pt-query-digest --version
pt-query-digest 1.0.1
# mysqld --version
mysqld Ver 5.5.16-55-log for Linux on x86_64 (Percona Server (GPL), Release 22.0)
OS: Ubuntu 10.04.3 LTS
I hope you can look into this.
Thanks,
Andrea
Related branches
lp:~percona-toolkit-dev/percona-toolkit/fix-883098-extra-processlist-fields
- Daniel Nichter: Approve
-
Diff: 374 lines (+97/-46)5 files modifiedbin/pt-kill (+36/-23)
bin/pt-query-digest (+22/-13)
bin/pt-table-usage (+10/-8)
lib/Processlist.pm (+2/-2)
t/lib/Processlist.t (+27/-0)
tags: | added: processlist pt-query-digest |
Changed in percona-toolkit: | |
importance: | Undecided → Medium |
Changed in percona-toolkit: | |
importance: | Medium → Undecided |
Changed in percona-toolkit: | |
status: | New → Confirmed |
Changed in percona-toolkit: | |
milestone: | none → 2.1.3 |
Changed in percona-toolkit: | |
assignee: | nobody → Brian Fraser (fraserbn) |
Changed in percona-toolkit: | |
importance: | Undecided → Medium |
Changed in percona-toolkit: | |
status: | Confirmed → In Progress |
summary: |
- pt-query-digest processlist isn't working + pt-query-digest processlist crashes if processlist has extra columns |
summary: |
- pt-query-digest processlist crashes if processlist has extra columns + pt-query-digest crashes if processlist has extra columns |
Changed in percona-toolkit: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
If you can reproduce the problem, would you please run the tool with
MKDEBUG=1 and capture the entry in the processlist (or whatever seems
to be the problem) to help us reproduce it?