This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
server_maintenance [2016/06/02 11:46] zoza |
server_maintenance [2016/06/02 11:48] zoza |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== server maintenance ====== | ====== server maintenance ====== | ||
- | * logging activity | + | ===== logging activity ===== |
apache error log | apache error log | ||
Line 15: | Line 15: | ||
<code>geoiplookup THE.IP.ADD.RE.SS</code> | <code>geoiplookup THE.IP.ADD.RE.SS</code> | ||
- | * IP filtering | + | ===== IP filtering ===== |
check existing iptables filters | check existing iptables filters | ||
Line 22: | Line 23: | ||
<code>iptables -A INPUT -s THE.IP.ADD.RE.SS -j DROP</code> | <code>iptables -A INPUT -s THE.IP.ADD.RE.SS -j DROP</code> | ||
- | * mysql | + | ===== mysql ===== |
remove comments from a wordpress site | remove comments from a wordpress site | ||
Line 55: | Line 56: | ||
</code> | </code> | ||
to all /etc/apache2/sites-available/domain.com configuration files which host a WordPress, to enable lynx analytics report, which clearly showed many **xmlrpc** requests in seconds. | to all /etc/apache2/sites-available/domain.com configuration files which host a WordPress, to enable lynx analytics report, which clearly showed many **xmlrpc** requests in seconds. | ||
+ | Solved the memory issue by blocking the ip that was sending xmlrpc requests (iptables drop) after geoiplocating it in lithuania | ||