Back to commands

Hosting Operations

Read-only, sensitive output

Show Active MySQL Sessions

MySQL is slow or rejecting clients and you need a quick view of active sessions.

Command

mysql -e "show full processlist;"

Before you run this

System impact: Read-only. Output may expose users, paths, tokens, keys, IPs, process arguments, or log details.

When not to use it: Do not use this as the kill step; inspect carefully before terminating sessions.

Expected output

Rows showing connection ID, user, host, database, command, time, state, and query text.

System impact

Read-only, sensitive output. Nothing changes. MySQL prints current sessions and queries.

Recovery / rollback: no state is changed.

When to use it

Use when MySQL feels saturated, slow, or overloaded.

When not to use it

Do not use this as the kill step; inspect carefully before terminating sessions.

Watch this command run

Command transcript

This sanitized transcript shows the commands and output shape without exposing host details.

demo@lab:~$

$ mysqladmin status

Uptime: 86400  Threads: 7  Questions: 23890  Slow queries: 3  Opens: 112  Open tables: 64  Queries per second avg: 0.276

$ mysql -e "show processlist;"

Id	User	Host	db	Command	Time	State	Info
17	app	192.0.2.10	shop	Query	91	Sending data	select * from orders
18	app	192.0.2.10	shop	Sleep	20		NULL
22	report	192.0.2.10	analytics	Query	680	Copying to tmp table	select customer_id

$ mysql -e "show full processlist;"

Id	User	Host	db	Command	Time	State	Info
17	app	192.0.2.10	shop	Query	91	Sending data	select * from orders join order_items
18	app	192.0.2.10	shop	Sleep	20		NULL
22	report	192.0.2.10	analytics	Query	680	Copying to tmp table	select customer_id, sum(total) from orders group by customer_id
View commands shown

These are the commands shown in the sanitized transcript.

Commands shown

  1. mysqladmin status
  2. mysql -e "show processlist;"
  3. mysql -e "show full processlist;"

next steps

Related commands

Hosting Operations Sensitive output

Find Long-Running MySQL Queries

One old query explained the whole slowdown.

mysql -e "select id,user,host,db,command,time,state,left(info,80) as info from information_schema.processlist where command <> 'Sleep' order by time desc limit 10;"
Hosting Operations Read-only

Show Active PostgreSQL Connections

The database was not down. It was full.

psql -X -A -F '|' -c "select pid,usename,datname,state,client_addr from pg_stat_activity order by state, pid;"
Hosting Operations Read-only

Check PostgreSQL Lock Waits

The outage was a queue, not a crash.

psql -X -c "select pid, wait_event_type, wait_event, state, left(query, 80) as query from pg_stat_activity where wait_event_type is not null order by pid;"
Hosting Operations Sensitive output

Show MySQL Database Sizes

The storage alert needed a database name.

mysql -e "select table_schema, round(sum(data_length + index_length)/1024/1024, 1) as mb from information_schema.tables group by table_schema order by mb desc;"
Study mapping

Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.

  • lfcs:operations-deployment
  • lfcs:services-logs
  • risk:read-only

Useful for

  • LPIC-1 style command-line practice
  • LFCS style performance tasks
  • Linux+ style troubleshooting review

Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.