pt-table-checksum error: Use of uninitialized value in int at line 2778
Bug #1073532 reported by
Ian M. Jones
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Toolkit moved to https://jira.percona.com/projects/PT |
Fix Released
|
High
|
Brian Fraser | ||
Bug Description
When trying to run pt-table-checksum I get the following error, no matter what options I try:
Use of uninitialized value in int at /home/jones/
Example command used:
pt-table-checksum -u jones -p xxx --databases spcs_jones_git
Versions:
percona-toolkit 2.1.5
MySQL 5.0.95
RedHat Enterprise Linux 5.x (fully patched up)
Perl 5.8.8
I'm configuring and installing percona-toolkit with PREFIX=${HOME}, if that makes any difference. And tools such as pt-heartbeat are working fine.
I tried percona-toolkit 2.1.4, that had same problem, so then decided to try 2.0.5, which does not show the problem and seems to work fine for me.
Related branches
lp:~percona-toolkit-dev/percona-toolkit/fix-1073532-Mo-Scalar-Util-PP
- Daniel Nichter: Approve
-
Diff: 409 lines (+114/-61)12 files modifiedbin/pt-archiver (+7/-6)
bin/pt-deadlock-logger (+7/-6)
bin/pt-kill (+7/-6)
bin/pt-online-schema-change (+7/-6)
bin/pt-slave-delay (+7/-6)
bin/pt-slave-find (+7/-6)
bin/pt-slave-restart (+7/-6)
bin/pt-table-checksum (+7/-6)
bin/pt-variable-advisor (+7/-6)
lib/Mo.pm (+7/-7)
t/lib/Mo/isa.t (+16/-0)
t/lib/Mo/isa_subtest.pm (+28/-0)
| Changed in percona-toolkit: | |
| assignee: | nobody → Brian Fraser (fraserbn) |
| status: | New → Confirmed |
| importance: | Undecided → High |
| milestone: | none → 2.1.6 |
Revision history for this message
| Brian Fraser (fraserbn) wrote | #1 |
| Changed in percona-toolkit: | |
| status: | Confirmed → In Progress |
| Changed in percona-toolkit: | |
| status: | In Progress → Fix Committed |
| summary: |
- Use of uninitialized value in int at pt-table-checksum line 2778 + pt-table-checksum error: Use of uninitialized value in int at line 2778 |
| Changed in percona-toolkit: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
Thank you for your bug report!
This bug is pretty bizarre; For some reason your Perl is picking a internal version of a module that it shouldn't be touching with a ten foot stick. I've worked around the problem for the toolkit, but also filed a bug upstream to get the root cause of the problem fixed: https:/
With some luck, this should make it into the 2.1.6 release.