Hot answers tagged wordpress
The memory leak (or just high memory usage) is almost always because of Wordpress. Wordpress is a well known memory and CPU hog, especially if you are using bad plugins and templates. You may try to disable all the plugins and templates one by one until you find which one is causing the high memory usage and replace it with another similar one or report ...
It looks like an infinite loop as line 159 of wp-admin/includes/file.php is a recursive call to the function wp_tmpnam(). It breaks the update process, so may be it could be worth checking this small correction, which describes your problem : wordpress bug fix
Since you do not have any addition plugins, I still suggest you to follow below steps: Disable both plugins Switched to default WordPress themes Scan all contents using virus scanner Then try to update contents. If it is still consuming lots of memory, it may be server configuration issue.
What I do for my clients is fairly straight forward. I provision physical machines from OVH, because I can get them "spun" up rapidly, usually in a few minutes. Allocate a separate IP for either the client or client projects, as sometimes one client might like to have a separate IP for each project. Slice the machine up using LXC containers, so each ...
Here is a little shell script I created for our developers. This way each time they roll out WordPress they don't have to remember all what to do. Your file structure is almost certainly somewhat different so will need to modify a bit. Please feel free to suggest improvements. SELinux isn't my specialization, but I'm learning it. #!/bin/sh # License: Public ...
The field in your logs that you are seeing is the cs(User-Agent) one, and the actual value in this field is all of WordPress/3.9.1;+http://www.zescience.com Something (probably a bot or WordPress plugin) is requesting your URL using that User Agent.
Wordpress has a fixed memory limit that overwrites the one defined in php.ini (if allowed by PHP configuration). In my experience setting a new memory limit on wp-config.php does not overwrite the memory limit set by wordpress itself (even though by glancing at the code it should have been working properly). So I generally modify ...
Although there are many ways to address this, I found an old question on ServerFault which suggests a simple iptables rule iptables -I INPUT -p tcp --dport 80 \ -m connlimit --connlimit-above 20 --connlimit-mask 40 -j DROP
Well, after a lot of unlucky tries, I've managed to find a way to correct the problem. For people having the same problem or similar, here's how I proceeded : Update your wordpress Connect to your wordpress admin panel if you can and uninstall all unused themes and plugins If you can't, delete them from your server (default path is [your web ...
Only top voted, non community-wiki answers of a minimum length are eligible