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 [2015/06/29 20:48] zoza |
server_maintenance [2016/06/02 11:46] zoza |
||
---|---|---|---|
Line 28: | Line 28: | ||
mysql>DELETE FROM wp_comments WHERE comment_approved = '0'; | mysql>DELETE FROM wp_comments WHERE comment_approved = '0'; | ||
</code> | </code> | ||
+ | |||
+ | mysql running out of memory in minutes | ||
+ | http://brunzino.github.io/blog/2016/05/21/solution-how-to-debug-intermittent-error-establishing-database-connection/ | ||
+ | https://www.linode.com/docs/websites/apache-tips-and-tricks/tuning-your-apache-server | ||
+ | added the following lines | ||
+ | <code> | ||
+ | #trying to fix mysql memory leak, which is possibly linked to an attack ? | ||
+ | <files xmlrpc.php> | ||
+ | order allow,deny | ||
+ | deny from all | ||
+ | </files> | ||
+ | </code> | ||
+ | to all /etc/apache2/sites-available/domain.com configuration files which host a WordPress, to block possible **xmlrpc** attack. | ||
+ | In /etc/apache2/access.log grep for this | ||
+ | <code> | ||
+ | POST /xmlrpc.php HTTP/1.1 | ||
+ | </code> | ||
+ | installed **lynx** and added the following lines: | ||
+ | <code> | ||
+ | <Location /server-status> | ||
+ | SetHandler server-status | ||
+ | Order Deny,Allow | ||
+ | Deny from all | ||
+ | Allow from localhost | ||
+ | </Location> | ||
+ | </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. | ||
+ | |||
+ |