DE

↑ ↓ select, Enter open, Esc close

Find the top IP addresses in the access log

harmless rootLogsdebian, ubuntu
Adjust the values, the command updates live
root@server
awk '{print $1}' /var/www/vhosts/system/example.com/logs/access_ssl_log | sort | uniq -c | sort -rn | head -20

Counts how often each IP address appears in the log and lists the 20 most frequent with their count. Useful when a server is suddenly under load and you want to know whether individual clients are responsible. Works with the combined format of Apache and nginx, where the IP is in the first column.

Note: On Plesk, HTTP and HTTPS requests are logged separately in access_log and access_ssl_log. Only the period since the last rotation is counted.

Also searched as

  • which ip makes the most requests
  • top ips in access log
  • who is hitting my site so often
  • count ip addresses in log file

Related one-liners

All in Logs

Find the most requested URLs in the access log

#awk '{print $7}' /var/www/vhosts/system/example.com/logs/access_ssl_log | sort | uniq -c | sort -rn | head -20
harmlessLogs

Count HTTP status codes in the access log

#awk '{print $9}' /var/www/vhosts/system/example.com/logs/access_ssl_log | sort | uniq -c | sort -rn
harmlessLogs

Regenerate the web server configuration of a domain

#plesk sbin httpdmng --reconfigure-domain example.com
cautionPlesk

Repair a domain's web server configuration with plesk repair

#plesk repair web example.com -y
cautionPlesk

Analyze server errors (5xx) in the access log

#awk '$9 ~ /^5[0-9][0-9]$/ {print $9, $7}' /var/www/vhosts/system/example.com/logs/access_ssl_log | sort | uniq -c | sort -rn | head -20
harmlessLogs

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

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.