.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" Set up some character translations and predefined strings. \*(-- will .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left .\" double quote, and \*(R" will give a right double quote. \*(C+ will .\" give a nicer C++. Capital omega is used to do unbreakable dashes and .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, .\" nothing in troff, for use with C<>. .tr \(*W- .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' .ie n \{\ . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} .el\{\ . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .ie \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . nr % 0 . rr F .\} .el \{\ . de IX .. .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. . \" fudge factors for nroff and troff .if n \{\ . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] \fP .\} .if t \{\ . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff .if n \{\ . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} .if t \{\ . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' .ds 8 \h'\*(#H'\(*b\h'-\*(#H' .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] .ds ae a\h'-(\w'a'u*4/10)'e .ds Ae A\h'-(\w'A'u*4/10)'E . \" corrections for vroff .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' . \" for low resolution devices (crt and lpr) .if \n(.H>23 .if \n(.V>19 \ \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} .rm #[ #] #H #V #F C .\" ======================================================================== .\" .IX Title "PT-MYSQL-SUMMARY 1p" .TH PT-MYSQL-SUMMARY 1p "2012-06-15" "perl v5.14.2" "User Contributed Perl Documentation" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH "NAME" pt\-mysql\-summary \- Summarize MySQL information nicely. .SH "SYNOPSIS" .IX Header "SYNOPSIS" Usage: pt-mysql-summary [\s-1OPTIONS\s0] [\-\- \s-1MYSQL\s0 \s-1OPTIONS\s0] .PP pt-mysql-summary conveniently summarizes the status and configuration of a MySQL database server so that you can learn about it at a glance. It is not a tuning tool or diagnosis tool. It produces a report that is easy to diff and can be pasted into emails without losing the formatting. It should work well on any modern \s-1UNIX\s0 systems. .SH "RISKS" .IX Header "RISKS" The following section is included to inform users about the potential risks, whether known or unknown, of using this tool. The two main categories of risks are those created by the nature of the tool (e.g. read-only tools vs. read-write tools) and those created by bugs. .PP pt-mysql-summary is a read-only tool. It should be very low-risk. .PP At the time of this release, we know of no bugs that could harm users. .PP The authoritative source for updated information is always the online issue tracking system. Issues that affect this tool will be marked as such. You can see a list of such issues at the following \s-1URL:\s0 http://www.percona.com/bugs/pt\-mysql\-summary . .PP See also \*(L"\s-1BUGS\s0\*(R" for more information on filing bugs and getting help. .SH "DESCRIPTION" .IX Header "DESCRIPTION" pt-mysql-summary works by connecting to a MySQL database server and querying it for status and configuration information. It saves these bits of data into files in a temporary directory, and then formats them neatly with awk and other scripting languages. .PP To use, simply execute it. Optionally add a double dash and then the same command-line options you would use to connect to MySQL, such as the following: .PP .Vb 1 \& pt\-mysql\-summary \-\- \-\-user=root .Ve .PP The tool interacts minimally with the server upon which it runs. It assumes that you'll run it on the same server you're inspecting, and therefore it assumes that it will be able to find the my.cnf configuration file, for example. However, it should degrade gracefully if this is not the case. Note, however, that its output does not indicate which information comes from the MySQL database and which comes from the host operating system, so it is possible for confusing output to be generated if you run the tool on one server and connect to a MySQL database server running on another server. .SH "OUTPUT" .IX Header "OUTPUT" Many of the outputs from this tool are deliberately rounded to show their magnitude but not the exact detail. This is called fuzzy-rounding. The idea is that it does not matter whether a server is running 918 queries per second or 921 queries per second; such a small variation is insignificant, and only makes the output hard to compare to other servers. Fuzzy-rounding rounds in larger increments as the input grows. It begins by rounding to the nearest 5, then the nearest 10, nearest 25, and then repeats by a factor of 10 larger (50, 100, 250), and so on, as the input grows. .PP The following is a sample of the report that the tool produces: .PP .Vb 9 \& # Percona Toolkit MySQL Summary Report ####################### \& System time | 2012\-03\-30 18:46:05 UTC \& (local TZ: EDT \-0400) \& # Instances ################################################## \& Port Data Directory Nice OOM Socket \& ===== ========================== ==== === ====== \& 12345 /tmp/12345/data 0 0 /tmp/12345.sock \& 12346 /tmp/12346/data 0 0 /tmp/12346.sock \& 12347 /tmp/12347/data 0 0 /tmp/12347.sock .Ve .PP The first two sections show which server the report was generated on and which MySQL instances are running on the server. This is detected from the output of \&\f(CW\*(C`ps\*(C'\fR and does not always detect all instances and parameters, but often works well. From this point forward, the report will be focused on a single MySQL instance, although several instances may appear in the above paragraph. .PP .Vb 12 \& # Report On Port 12345 ####################################### \& User | msandbox@% \& Time | 2012\-03\-30 14:46:05 (EDT) \& Hostname | localhost.localdomain \& Version | 5.5.20\-log MySQL Community Server (GPL) \& Built On | linux2.6 i686 \& Started | 2012\-03\-28 23:33 (up 1+15:12:09) \& Databases | 4 \& Datadir | /tmp/12345/data/ \& Processes | 2 connected, 2 running \& Replication | Is not a slave, has 1 slaves connected \& Pidfile | /tmp/12345/data/12345.pid (exists) .Ve .PP This section is a quick summary of the MySQL instance: version, uptime, and other very basic parameters. The Time output is generated from the MySQL server, unlike the system date and time printed earlier, so you can see whether the database and operating system times match. .PP .Vb 1 \& # Processlist ################################################ \& \& Command COUNT(*) Working SUM(Time) MAX(Time) \& \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\- \-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\- \& Binlog Dump 1 1 150000 150000 \& Query 1 1 0 0 \& \& User COUNT(*) Working SUM(Time) MAX(Time) \& \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\- \-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\- \& msandbox 2 2 150000 150000 \& \& Host COUNT(*) Working SUM(Time) MAX(Time) \& \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\- \-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\- \& localhost 2 2 150000 150000 \& \& db COUNT(*) Working SUM(Time) MAX(Time) \& \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\- \-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\- \& NULL 2 2 150000 150000 \& \& State COUNT(*) Working SUM(Time) MAX(Time) \& \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\- \-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\- \& Master has sent all binlog to 1 1 150000 150000 \& NULL 1 1 0 0 .Ve .PP This section is a summary of the output from \s-1SHOW\s0 \s-1PROCESSLIST\s0. Each sub-section is aggregated by a different item, which is shown as the first column heading. When summarized by Command, every row in \s-1SHOW\s0 \s-1PROCESSLIST\s0 is included, but otherwise, rows whose Command is Sleep are excluded from the \s-1SUM\s0 and \s-1MAX\s0 columns, so they do not skew the numbers too much. In the example shown, the server is idle except for this tool itself, and one connected replica, which is executing Binlog Dump. .PP The columns are the number of rows included, the number that are not in Sleep status, the sum of the Time column, and the maximum Time column. The numbers are fuzzy-rounded. .PP .Vb 10 \& # Status Counters (Wait 10 Seconds) ########################## \& Variable Per day Per second 10 secs \& Binlog_cache_disk_use 4 \& Binlog_cache_use 80 \& Bytes_received 15000000 175 200 \& Bytes_sent 15000000 175 2000 \& Com_admin_commands 1 \& ...................(many lines omitted)............................ \& Threads_created 40 1 \& Uptime 90000 1 1 .Ve .PP This section shows selected counters from two snapshots of \s-1SHOW\s0 \s-1GLOBAL\s0 \s-1STATUS\s0, gathered approximately 10 seconds apart and fuzzy-rounded. It includes only items that are incrementing counters; it does not include absolute numbers such as the Threads_running status variable, which represents a current value, rather than an accumulated number over time. .PP The first column is the variable name, and the second column is the counter from the first snapshot divided by 86400 (the number of seconds in a day), so you can see the magnitude of the counter's change per day. 86400 fuzzy-rounds to 90000, so the Uptime counter should always be about 90000. .PP The third column is the value from the first snapshot, divided by Uptime and then fuzzy-rounded, so it represents approximately how quickly the counter is growing per-second over the uptime of the server. .PP The third column is the incremental difference from the first and second snapshot, divided by the difference in uptime and then fuzzy-rounded. Therefore, it shows how quickly the counter is growing per second at the time the report was generated. .PP .Vb 3 \& # Table cache ################################################ \& Size | 400 \& Usage | 15% .Ve .PP This section shows the size of the table cache, followed by the percentage of the table cache in use. The usage is fuzzy-rounded. .PP .Vb 10 \& # Key Percona Server features ################################ \& Table & Index Stats | Not Supported \& Multiple I/O Threads | Enabled \& Corruption Resilient | Not Supported \& Durable Replication | Not Supported \& Import InnoDB Tables | Not Supported \& Fast Server Restarts | Not Supported \& Enhanced Logging | Not Supported \& Replica Perf Logging | Not Supported \& Response Time Hist. | Not Supported \& Smooth Flushing | Not Supported \& HandlerSocket NoSQL | Not Supported \& Fast Hash UDFs | Unknown .Ve .PP This section shows features that are available in Percona Server and whether they are enabled or not. In the example shown, the server is standard MySQL, not Percona Server, so the features are generally not supported. .PP .Vb 2 \& # Plugins #################################################### \& InnoDB compression | ACTIVE .Ve .PP This feature shows specific plugins and whether they are enabled. .PP .Vb 5 \& # Query cache ################################################ \& query_cache_type | ON \& Size | 0.0 \& Usage | 0% \& HitToInsertRatio | 0% .Ve .PP This section shows whether the query cache is enabled and its size, followed by the percentage of the cache in use and the hit-to-insert ratio. The latter two are fuzzy-rounded. .PP .Vb 4 \& # Schema ##################################################### \& Would you like to mysqldump \-d the schema and analyze it? y/n y \& There are 4 databases. Would you like to dump all, or just one? \& Type the name of the database, or press Enter to dump all of them. \& \& Database Tables Views SPs Trigs Funcs FKs Partn \& mysql 24 \& performance_schema 17 \& sakila 16 7 3 6 3 22 \& \& Database MyISAM CSV PERFORMANCE_SCHEMA InnoDB \& mysql 22 2 \& performance_schema 17 \& sakila 8 15 \& \& Database BTREE FULLTEXT \& mysql 31 \& performance_schema \& sakila 63 1 \& \& c t s e l d i t m v s \& h i e n o a n i e a m \& a m t u n t t n d r a \& r e m g e y i c l \& s b t i u h l \& t l i n m a i \& a o m t t r n \& m b e e t \& p x \& t \& Database === === === === === === === === === === === \& mysql 61 10 6 78 5 4 26 3 4 5 3 \& performance_schema 5 16 33 \& sakila 1 15 1 3 4 3 19 42 26 .Ve .PP If you select to dump the schema and analyze it, the tool will print the above section. This summarizes the number and type of objects in the database. It is generated by running \f(CW\*(C`mysqldump \-\-no\-data\*(C'\fR, not by querying the \&\s-1INFORMATION_SCHEMA\s0, which can freeze a busy server. You can use the \&\*(L"\-\-databases\*(R" option to specify which databases to examine. If you do not, and you run the tool interactively, it will prompt you as shown. .PP You can choose not to dump the schema, to dump all of the databases, or to dump only a single named one, by specifying the appropriate options. In the example above, we are dumping all databases. .PP The first sub-report in the section is the count of objects by type in each database: tables, views, and so on. The second one shows how many tables use various storage engines in each database. The third sub-report shows the number of each type of indexes in each database. .PP The last section shows the number of columns of various data types in each database. For compact display, the column headers are formatted vertically, so you need to read downwards from the top. In this example, the first column is \&\f(CW\*(C`char\*(C'\fR and the second column is \f(CW\*(C`timestamp\*(C'\fR. This example is truncated so it does not wrap on a terminal. .PP All of the numbers in this portion of the output are exact, not fuzzy-rounded. .PP .Vb 10 \& # Noteworthy Technologies #################################### \& Full Text Indexing | Yes \& Geospatial Types | No \& Foreign Keys | Yes \& Partitioning | No \& InnoDB Compression | Yes \& SSL | No \& Explicit LOCK TABLES | No \& Delayed Insert | No \& XA Transactions | No \& NDB Cluster | No \& Prepared Statements | No \& Prepared statement count | 0 .Ve .PP This section shows some specific technologies used on this server. Some of them are detected from the schema dump performed for the previous sections; others can be detected by looking at \s-1SHOW\s0 \s-1GLOBAL\s0 \s-1STATUS\s0. .PP .Vb 10 \& # InnoDB ##################################################### \& Version | 1.1.8 \& Buffer Pool Size | 16.0M \& Buffer Pool Fill | 100% \& Buffer Pool Dirty | 0% \& File Per Table | OFF \& Page Size | 16k \& Log File Size | 2 * 5.0M = 10.0M \& Log Buffer Size | 8M \& Flush Method | \& Flush Log At Commit | 1 \& XA Support | ON \& Checksums | ON \& Doublewrite | ON \& R/W I/O Threads | 4 4 \& I/O Capacity | 200 \& Thread Concurrency | 0 \& Concurrency Tickets | 500 \& Commit Concurrency | 0 \& Txn Isolation Level | REPEATABLE\-READ \& Adaptive Flushing | ON \& Adaptive Checkpoint | \& Checkpoint Age | 0 \& InnoDB Queue | 0 queries inside InnoDB, 0 queries in queue \& Oldest Transaction | 0 Seconds \& History List Len | 209 \& Read Views | 1 \& Undo Log Entries | 1 transactions, 1 total undo, 1 max undo \& Pending I/O Reads | 0 buf pool reads, 0 normal AIO, \& 0 ibuf AIO, 0 preads \& Pending I/O Writes | 0 buf pool (0 LRU, 0 flush list, 0 page); \& 0 AIO, 0 sync, 0 log IO (0 log, 0 chkp); \& 0 pwrites \& Pending I/O Flushes | 0 buf pool, 0 log \& Transaction States | 1xnot started .Ve .PP This section shows important configuration variables for the InnoDB storage engine. The buffer pool fill percent and dirty percent are fuzzy-rounded. The last few lines are derived from the output of \s-1SHOW\s0 \s-1INNODB\s0 \s-1STATUS\s0. It is likely that this output will change in the future to become more useful. .PP .Vb 4 \& # MyISAM ##################################################### \& Key Cache | 16.0M \& Pct Used | 10% \& Unflushed | 0% .Ve .PP This section shows the size of the MyISAM key cache, followed by the percentage of the cache in use and percentage unflushed (fuzzy-rounded). .PP .Vb 3 \& # Security ################################################### \& Users | 2 users, 0 anon, 0 w/o pw, 0 old pw \& Old Passwords | OFF .Ve .PP This section is generated from queries to tables in the mysql system database. It shows how many users exist, and various potential security risks such as old-style passwords and users without passwords. .PP .Vb 10 \& # Binary Logging ############################################# \& Binlogs | 1 \& Zero\-Sized | 0 \& Total Size | 21.8M \& binlog_format | STATEMENT \& expire_logs_days | 0 \& sync_binlog | 0 \& server_id | 12345 \& binlog_do_db | \& binlog_ignore_db | .Ve .PP This section shows configuration and status of the binary logs. If there are zero-sized binary logs, then it is possible that the binlog index is out of sync with the binary logs that actually exist on disk. .PP .Vb 10 \& # Noteworthy Variables ####################################### \& Auto\-Inc Incr/Offset | 1/1 \& default_storage_engine | InnoDB \& flush_time | 0 \& init_connect | \& init_file | \& sql_mode | \& join_buffer_size | 128k \& sort_buffer_size | 2M \& read_buffer_size | 128k \& read_rnd_buffer_size | 256k \& bulk_insert_buffer | 0.00 \& max_heap_table_size | 16M \& tmp_table_size | 16M \& max_allowed_packet | 1M \& thread_stack | 192k \& log | OFF \& log_error | /tmp/12345/data/mysqld.log \& log_warnings | 1 \& log_slow_queries | ON \& log_queries_not_using_indexes | OFF \& log_slave_updates | ON .Ve .PP This section shows several noteworthy server configuration variables that might be important to know about when working with this server. .PP .Vb 10 \& # Configuration File ######################################### \& Config File | /tmp/12345/my.sandbox.cnf \& [client] \& user = msandbox \& password = msandbox \& port = 12345 \& socket = /tmp/12345/mysql_sandbox12345.sock \& [mysqld] \& port = 12345 \& socket = /tmp/12345/mysql_sandbox12345.sock \& pid\-file = /tmp/12345/data/mysql_sandbox12345.pid \& basedir = /home/baron/5.5.20 \& datadir = /tmp/12345/data \& key_buffer_size = 16M \& innodb_buffer_pool_size = 16M \& innodb_data_home_dir = /tmp/12345/data \& innodb_log_group_home_dir = /tmp/12345/data \& innodb_data_file_path = ibdata1:10M:autoextend \& innodb_log_file_size = 5M \& log\-bin = mysql\-bin \& relay_log = mysql\-relay\-bin \& log_slave_updates \& server\-id = 12345 \& report\-host = 127.0.0.1 \& report\-port = 12345 \& log\-error = mysqld.log \& innodb_lock_wait_timeout = 3 \& # The End #################################################### .Ve .PP This section shows a pretty-printed version of the my.cnf file, with comments removed and with whitespace added to align things for easy reading. The tool tries to detect the my.cnf file by looking at the output of ps, and if it does not find the location of the file there, it tries common locations until it finds a file. Note that this file might not actually correspond with the server from which the report was generated. This can happen when the tool isn't run on the same server it's reporting on, or when detecting the location of the configuration file fails. .SH "OPTIONS" .IX Header "OPTIONS" All options after \*(-- are passed to \f(CW\*(C`mysql\*(C'\fR. .IP "\-\-config" 4 .IX Item "--config" type: string .Sp Read this comma-separated list of config files. If specified, this must be the first option on the command line. .IP "\-\-help" 4 .IX Item "--help" Print help and exit. .IP "\-\-save\-samples" 4 .IX Item "--save-samples" type: string .Sp Save the data files used to generate the summary in this directory. .IP "\-\-read\-samples" 4 .IX Item "--read-samples" type: string .Sp Create a report from the files found in this directory. .IP "\-\-databases" 4 .IX Item "--databases" type: string .Sp Names of databases to summarize. If you want all of them, you can use the value \&\f(CW\*(C`\-\-all\-databases\*(C'\fR; you can also pass in a comma-separated list of database names. If not provided, the program will ask you for manual input. .IP "\-\-sleep" 4 .IX Item "--sleep" type: int; default: 10 .Sp Seconds to sleep when gathering status counters. .IP "\-\-version" 4 .IX Item "--version" Print tool's version and exit. .SH "ENVIRONMENT" .IX Header "ENVIRONMENT" This tool does not use any environment variables. .SH "SYSTEM REQUIREMENTS" .IX Header "SYSTEM REQUIREMENTS" This tool requires Bash v3 or newer, Perl 5.8 or newer, and binutils. These are generally already provided by most distributions. On \s-1BSD\s0 systems, it may require a mounted procfs. .SH "BUGS" .IX Header "BUGS" For a list of known bugs, see http://www.percona.com/bugs/pt\-mysql\-summary . .PP Please report bugs at https://bugs.launchpad.net/percona\-toolkit . Include the following information in your bug report: .IP "\(bu" 4 Complete command-line used to run the tool .IP "\(bu" 4 Tool \*(L"\-\-version\*(R" .IP "\(bu" 4 MySQL version of all servers involved .IP "\(bu" 4 Output from the tool including \s-1STDERR\s0 .IP "\(bu" 4 Input files (log/dump/config files, etc.) .PP If possible, include debugging output by running the tool with \f(CW\*(C`PTDEBUG\*(C'\fR; see \*(L"\s-1ENVIRONMENT\s0\*(R". .SH "DOWNLOADING" .IX Header "DOWNLOADING" Visit http://www.percona.com/software/percona\-toolkit/ to download the latest release of Percona Toolkit. Or, get the latest release from the command line: .PP .Vb 1 \& wget percona.com/get/percona\-toolkit.tar.gz \& \& wget percona.com/get/percona\-toolkit.rpm \& \& wget percona.com/get/percona\-toolkit.deb .Ve .PP You can also get individual tools from the latest release: .PP .Vb 1 \& wget percona.com/get/TOOL .Ve .PP Replace \f(CW\*(C`TOOL\*(C'\fR with the name of any tool. .SH "AUTHORS" .IX Header "AUTHORS" Baron Schwartz, Brian Fraser, and Daniel Nichter .SH "ABOUT PERCONA TOOLKIT" .IX Header "ABOUT PERCONA TOOLKIT" This tool is part of Percona Toolkit, a collection of advanced command-line tools developed by Percona for MySQL support and consulting. Percona Toolkit was forked from two projects in June, 2011: Maatkit and Aspersa. Those projects were created by Baron Schwartz and developed primarily by him and Daniel Nichter, both of whom are employed by Percona. Visit for more software developed by Percona. .SH "COPYRIGHT, LICENSE, AND WARRANTY" .IX Header "COPYRIGHT, LICENSE, AND WARRANTY" This program is copyright 2010\-2011 Baron Schwartz, 2011\-2012 Percona Inc. Feedback and improvements are welcome. .PP \&\s-1THIS\s0 \s-1PROGRAM\s0 \s-1IS\s0 \s-1PROVIDED\s0 \*(L"\s-1AS\s0 \s-1IS\s0\*(R" \s-1AND\s0 \s-1WITHOUT\s0 \s-1ANY\s0 \s-1EXPRESS\s0 \s-1OR\s0 \s-1IMPLIED\s0 \&\s-1WARRANTIES\s0, \s-1INCLUDING\s0, \s-1WITHOUT\s0 \s-1LIMITATION\s0, \s-1THE\s0 \s-1IMPLIED\s0 \s-1WARRANTIES\s0 \s-1OF\s0 \&\s-1MERCHANTABILITY\s0 \s-1AND\s0 \s-1FITNESS\s0 \s-1FOR\s0 A \s-1PARTICULAR\s0 \s-1PURPOSE\s0. .PP This program is free software; you can redistribute it and/or modify it under the terms of the \s-1GNU\s0 General Public License as published by the Free Software Foundation, version 2; \s-1OR\s0 the Perl Artistic License. On \s-1UNIX\s0 and similar systems, you can issue `man perlgpl' or `man perlartistic' to read these licenses. .PP You should have received a copy of the \s-1GNU\s0 General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, \s-1MA\s0 02111\-1307 \s-1USA\s0. .SH "VERSION" .IX Header "VERSION" pt-mysql-summary 2.1.2