pt-trend does not work

Bug #856065 reported by Dario Minnucci on 2011-09-22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Percona Toolkit
Daniel Nichter
Daniel Nichter
Daniel Nichter

Bug Description

Hi Daniel,

It seems that pt-trend is not handling options properly.

$ pt-trend --help
Option q does not exist at /usr/bin/pt-trend line 664.

Related branches

Doug (ddressler) wrote :

I see the same behavior with ArchLinux using the AUR Package build for percona-toolkit 1.0.1-1
Build file available here:

I added print " OPT: $opt\n" on the line above where the error is reported and I see this:

[root@dbslave05 ddressler]# pt-trend --progress percentage,5 /var/log/mysql/slow-queries.log
OPT: config
OPT: q
Option q does not exist at /usr/bin/vendor_perl/pt-trend line 665.

Changed in percona-toolkit:
importance: Undecided → Medium
status: New → Confirmed
tags: added: pt-trend
Lindsay Holmwood (auxesis) wrote :

      ? Complete command-line used to run the tool

pt-trend /var/log/mysql/mysql-slow.log

       ? Tool "--version"

pt-trend 1.0.1

       ? MySQL version of all servers involved

$ mysql --version
mysql Ver 14.16 Distrib 5.2.8-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
$ mysqld --version
mysqld Ver 5.2.8-MariaDB-mariadb102~lucid-log for debian-linux-gnu on x86_64 ((MariaDB -

       ? Output from the tool including STDERR

$ pt-trend /var/log/mysql/mysql-slow.log
Option q does not exist at /usr/bin/pt-trend line 664.

       ? Input files (log/dump/config files, etc.)


       If possible, include debugging output by running the tool with "PTDEBUG"; see "ENVIRONMENT".

$ PTDEBUG=1 pt-trend /var/log/mysql/mysql-slow.log
Option q does not exist at /usr/bin/pt-trend line 664.

summary: - pt-trend is not handling options properly
+ pt-trend does not work
Daniel Nichter (daniel-nichter) wrote :

Indeed, pt-trend didn't work at all because somehow its --quiet option was removed in the transition from Maatkit. It has been fixed and tested in 1.0 and 2.0, so it will appear in the next release for either of those series. In the meantime, a fixed version can be gotten from either the latest 1.0 or 2.0 bzr branch. Thanks for reporting this.

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

Duplicates of this bug

Other bug subscribers