DE

↑ ↓ select, Enter open, Esc close

Query Memcached statistics with netcat

harmlessRedis and Memcacheddebian, ubuntu
Adjust the values, the command updates live
user@server
printf 'stats\nquit\n' | nc 127.0.0.1 11211 | grep -E 'STAT (curr_items|bytes|limit_maxbytes|get_hits|get_misses|evictions|curr_connections) '

Sends the stats command to Memcached over the text protocol and filters out the most meaningful lines. bytes and limit_maxbytes show usage and limit, get_hits and get_misses show how effective the cache is. If evictions keeps rising, the memory (option -m in /etc/memcached.conf) is too small.

Note: Without the final grep, the full statistics are shown. If nothing answers, Memcached is not running or is listening on a different address.

Also searched as

  • is memcached running
  • memcached hit rate
  • memcached memory full

Related one-liners

All in Redis and Memcached

Flush Memcached completely (flush_all)

$printf 'flush_all\nquit\n' | nc 127.0.0.1 11211
cautionRedis and Memcached

Show the Redis cache hit rate

$redis-cli INFO stats | grep -E '^(keyspace_hits|keyspace_misses|evicted_keys|expired_keys):'
harmlessRedis and Memcached

Calculate the average, minimum and maximum of a column

$awk -v c=2 'NR == 1 {min = max = $c} {s += $c; if ($c < min) min = $c; if ($c > max) max = $c} END {if (NR) printf "n=%d avg=%.2f min=%s max=%s\n", NR, s/NR, min, max}' measurements.txt
harmlessText processing

Count requests per minute in the access log

#awk '{print substr($4, 2, 17)}' /var/www/vhosts/system/example.com/logs/access_ssl_log | sort | uniq -c | sort -rn | head -20
harmlessLogs

Count WordPress posts by status

$wp post list --post_type=post --post_status=any --field=post_status --path=/var/www/vhosts/example.com/httpdocs | sort | uniq -c
harmlessWP-CLI

Show traffic and error counters of a network interface

$ip -s link show eth0
harmlessNetwork

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.