The command itself is very easy to run from the MySQL client: mysql> SHOW PROCESSLIST SHOW PROCESSLIST lists all the open connections to the server, including: thread IDs, material on the requesting host, user and database, the query string, and the current state of the connection. This assists in keeping account of client-user transactions. This will fix your queries problem!Īnother helpful MySQL command, is SHOW PROCESSLIST. The final step is to copy the provided query in the output and run as instructed. Perform the following to produce kill commands from the PROCESSLIST table: mysql> SELECT GROUP_CONCAT(CONCAT('KILL ',id,' ') SEPARATOR ' ')įROM information_schema.processlist WHERE user 'system user' If multiple bad requests are preventing valid queries from working, you can fix this by clearing them out without having to run kill on individual threads. Next, run the following command to kill it:Īs a side note, be sure to replace with the ID of the query you want to deactivate or get rid of.Then review the “Time” field to find the longest running query.When you are able to successfully make a local MySQL connection to the site’s database, run the ensuing command to present a list of accessible threads:

In order to kill these long-running queries, you must access the environment’s MySQL database.

MySQL queries can sometimes be long-running and may prevent transactions from accessing necessary tables to complete a request.

My sequel workbench