Issues
- ``pt-stalk` with ``--mysql-only`` option was not adding MySQL ``processlist`` information to the output file.PT-1576Resolved issue: PT-1576
- LP #1644694: pt-stalk get wrong mysqld pid when the host installed multi mysql instancePT-1398Resolved issue: PT-1398Carlos Salguero
- LP #1642751: Collect information about locks and transactions using P_SPT-1396Resolved issue: PT-1396
- LP #1642750: Collect information about prepared statements if P_S is enabledPT-1395
- LP #1642748: Instrument memory usage if P_S enabledPT-1394
- LP #1642747: Initial pre-checks for P_S for pt-stalkPT-1393
- LP #1642746: Add Performance Schema support to pt-stalkPT-1392
- LP #1489026: pt-stalk before_collect triggers will not fire when --no-collect is specifiedPT-1301
- LP #1449998: pt-stalk "--config" incorrect parsingPT-1278dmitriy.kostiuk
- LP #1307377: pt-stalk ominous open_tables functionPT-1218Resolved issue: PT-1218Sveta Smirnova
- LP #1204763: Wishlist Add ask-pass to pt-stalkPT-1136Resolved issue: PT-1136
- LP #1194874: pt-stalk should capture show slave statusPT-1128Resolved issue: PT-1128
- LP #1194592: pt-stalk should capture BBU statusPT-1127Resolved issue: PT-1127
- LP #1192083: pt-stalk should collect some NUMA informationPT-1123Resolved issue: PT-1123Carlos Salguero
- LP #1190636: pt-stalk have the possibility to define data collection intervalPT-1122Resolved issue: PT-1122
- LP #1177037: pt-summary should give better info about bonding interfacesPT-1109Resolved issue: PT-1109
- LP #1166414: pt-stalk doesn't collect the correct number of mysqladmin samplesPT-1095
- LP #1152571: oprofile in pt-stalk won't work with galera/pxcPT-1090
- LP #1146656: Provide smaps in pt-stalkPT-1085Resolved issue: PT-1085
- LP #1103705: pt-stalk top -bn1 causes an error on CentOSPT-1069Resolved issue: PT-1069
- LP #1099941: Use prefix for pid and log files as wellPT-1066Resolved issue: PT-1066
- LP #1097600: pt-stalk fails to correctly detect if --function value is a file or notPT-1063
- LP #1083488: Include NUMA information in pt-tool outputPT-1052Resolved issue: PT-1052Sveta Smirnova
- LP #1064482: include collection of InnoDB locks and transactions as part of pt-stalkPT-1036Resolved issue: PT-1036
- LP #1049148: pt-stalk can't do "less-than" thresholdsPT-1022
- LP #1046966: pt-stalk fails when there is too many connectionPT-1020
- LP #900544: pt-stalk will trigger collect even if mysql access fails, and pt-collect will also collect non-mysql data.PT-907Resolved issue: PT-907
- LP #889765: no warnings when you execute pt-collect and there is a percona-toolkit-collect-lockfilePT-895Resolved issue: PT-895
- LP #880341: pt-stalk documentation for .conf file is wrongPT-888Resolved issue: PT-888
- LP #1349086: pt-stalk should also gather dmesg outputPT-854Resolved issue: PT-854
- LP #1050497: pt-stalk doesn't capture SHOW MASTER LOGSPT-848
- LP #1642753: Collect information about variables from P_SPT-833
- LP #1537416: sort pt-stalk transactions()PT-828Resolved issue: PT-828
- LP #1266869: pt-stalk fails to start if $HOME environment variable is not setPT-805Resolved issue: PT-805
- LP #1156867: pt-stalk prints the wrong variable name in verbose mode when --function is usedPT-794Resolved issue: PT-794
- LP #1081733: pt-stalk plugins can't access the real --prefixPT-790Resolved issue: PT-790
- LP #954990: pt-stalk --nostalk does not workPT-774Resolved issue: PT-774
- LP #856060: Document gdb dependencyPT-756Resolved issue: PT-756
- LP #1642754: Collect replication slave informationPT-718Resolved issue: PT-718
- LP #1494082: pt-stalk find -warn option is not portablePT-693Resolved issue: PT-693
- LP #1488600: pt-stalk doesn't check tokudb statusPT-691Resolved issue: PT-691
- LP #1425478: pt-stalk removes non-empty files that start with empty linePT-676Resolved issue: PT-676
- LP #1417558: pt-stalk with --collect-strace output doesn't go to an YYYY_MM_DD_HH_mm_ss-strace filePT-673Resolved issue: PT-673
- LP #1348679: pt-stalk handles mysql user password in awkward wayPT-655Resolved issue: PT-655
- LP #1335322: pt-stalk fails when variable or threshold is non-integerPT-651Resolved issue: PT-651
- LP #1318985: pt-stalk should use SQL_NO_CACHEPT-648Resolved issue: PT-648
- LP #1202757: pt-stalk --sleep should never be less than --run-time.PT-618
- LP #1172317: pt-sift does not work if pt-stalk did not collect due to a full diskPT-612Resolved issue: PT-612
- LP #1125665: pt-stalk --no-stalk silently clobbers other options, acts magicallyPT-603Resolved issue: PT-603
- LP #1070434: pt-stalk --no-stalk and --iterations 1 don't wait for the collectPT-589Resolved issue: PT-589
``pt-stalk` with ``--mysql-only`` option was not adding MySQL ``processlist`` information to the output file.
Description
Environment
Confluence content
Smart Checklist
Activity
Stofa KenidaJuly 9, 2018 at 7:00 AM
Hi,
May be the fix should be moving this statement
local ts="$(date +"TS %s.%N %F %T")"
outside the if block started by be below statement
if [ ! "$OPT_MYSQL_ONLY" ]; then
inside the collect routine on put it just before the if condition.
Stofa.
Lalit ChoudharyJuly 6, 2018 at 1:44 PM
Problem: Use of pt-stalk with --mysql-only option not adding mysql processlist information in output file and file is always empty.
Tested for Percona toolkit-3.0.9, 3.0.10 with latest version of Percona server 5.5,5.6 and 5.7
Steps to reproduce the issue:
Case1: Pt-stalk with --*mysql-only option*
pt-stalk -u root --password=xxxxxxx --mysql-only --no-stalk --iterations=1 --sleep=30 --dest=./test1
For above pt-stalk run with --mysql-only option, empty processlist file generated at destination directory. Expectation is, it should have mysql processlist output in it.
Case2: Pt-stalk without --*mysql-only option*
pt-stalk -u root --password=xxxxxxx --mysql-only --no-stalk --iterations=1 --sleep=30 --dest=./test2
In this case, we are running similar pt-stalk command without --mysql-only option, which is generating processlist file which has mysql processlist information in it.
Lalit ChoudharyJuly 6, 2018 at 12:55 PM
Hello Stofa,
Thank you for the report.
Validated as Bug.
mysql-only option is not working as expected.
By running :
/usr/bin/pt-stalk --host 127.0.0.1 --port 3355 --mysql-only --daemonize --log /tmp/pt-stalk/pt-stalk.log --dest /tmp/pt-stalk --function status --variable Threads_running --threshold 12 --cycles=10 --sleep=30 --run-time=20 --interval 5 --retention-time 1 --disk-pct-free 10
The generated file :
/tmp/pt-stalk/2018_07_03_14_30_22-processlist is empty.
Only by removing mysql-option, the file is populated.
I'am using 5.5.59-38.11-log Percona Server (GPL), Release 38.11, Revision 2084a7bc7ec version runnig on centos 6.9.
Kernel version : 2.6.32-696.20.1.el6.x86_64 #1
Also, on my box, other mysql istances ( listening on different ports ) are running.
Thanks.