DE

↑ ↓ select, Enter open, Esc close

Show running MySQL queries without idle connections

harmless rootMySQL and MariaDBdebian, ubuntu
root@server
mysql -e "SELECT id, user, db, time, state, LEFT(info, 100) AS query FROM information_schema.processlist WHERE command <> 'Sleep' ORDER BY time DESC;"

Reads the process list and hides sleeping connections. It shows ID, user, database, runtime in seconds, state and the first 100 characters of the query. The first thing to check under high database load or when pages hang.

Note: SHOW FULL PROCESSLIST; shows the complete list including idle connections. On Plesk servers, run it as admin.

Also searched as

  • mysql high load
  • which query is hanging
  • show mysql process list

Related one-liners

All in MySQL and MariaDB

Compare max connections with the peak so far

#mysql -e "SHOW GLOBAL STATUS LIKE 'Max_used_connections'; SHOW GLOBAL VARIABLES LIKE 'max_connections';"
harmlessMySQL and MariaDB

Enable the slow query log at runtime

#mysql -e 'SET GLOBAL slow_query_log = 1; SET GLOBAL long_query_time = 2; SHOW VARIABLES LIKE "slow_query_log_file";'
cautionMySQL and MariaDB

Find the 20 largest tables on the server

#mysql -e 'SELECT table_schema, table_name, ROUND((data_length + index_length) / 1024 / 1024, 1) AS mb, table_rows FROM information_schema.tables ORDER BY data_length + index_length DESC LIMIT 20;'
harmlessMySQL and MariaDB

Kill a hanging MySQL query

#mysql -e 'KILL 12345;'
cautionMySQL and MariaDB

Analyze the slow query log for the slowest queries

#mysqldumpslow -s t -t 10 /var/log/mysql/mariadb-slow.log
harmlessMySQL and MariaDB

Back up a single database consistently as gzip

$mysqldump --single-transaction --quick -u dbuser -p wp_example | gzip > /var/www/vhosts/example.com/wp_example.sql.gz
harmlessMySQL and MariaDB

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.