Oudin's questions

I have an Ubuntu server in AWS. It runs a WordPress multi site, which has worked perfectly for some years. However now the site is constantly crashing as a result of lack of or no space.

To restore the site I have delete at least 1 plugin. However the no space issue quickly returns and the site crashes. I have also deleted about 8GB of log files, yet in a matter of hours same issue. No Space.

Running the following command.

df -hT /dev/xvda1

Shows that there is enough space available, as shown below.

Filesystem Type Size Used Avail Use% Mounted on
/dev/xvda1     ext4   59G   26G   31G  46% /

Runging the following comand

df -h

Have the following results

Filesystem      Size  Used Avail Use% Mounted on
udev            996M   12K  996M   1% /dev
tmpfs           201M  396K  200M   1% /run
/dev/xvda1       59G   26G   31G  46% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
none            5.0M     0  5.0M   0% /run/lock
tmpfs          1001M     0 1001M   0% /run/shm
none            100M     0  100M   0% /run/user

How can I narrow down the cause of this issue and fix it?

I have the following cron setup to clear the tmp folder:

0 0 * * *  rm -rf /home/user/tmp/* >> /dev/null 2>&1

However I'm looking for a more efficient way which would be less CPU intensive as this would have to clear 1000+ files daily.

How can I edit this to make it less CPU intensive?

I've upgraded Apache 2.4 and would like to block an Ip this could be done by using the following in the .htaccess on Apache 2.2

Order Deny,Allow
Deny from 50.62.136.183

However how can I achieve the same in the .htaccess on Apache 2.4

I'm running WordPress multi-site on an amazon micro ec2 with suexec, Apache and php CGi On Ubuntu 12.04 However I've been experiencing a lot of Internal server 500 errors and I'm in the process of debugging it to find a solution. I've posted my error logs below

example.com error.log:

[Fri Oct 26 10:10:08 2012] [warn] [client 23.23.xxx.xx] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server
[Fri Oct 26 10:10:08 2012] [error] [client 23.23.xxx.xx] Premature end of script headers: wp-cron.php
[Fri Oct 26 10:50:04 2012] [warn] [client 190.213.xxx.xxx] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: https://www.example.com/wp-admin/
[Fri Oct 26 10:50:04 2012] [error] [client 190.213.xxx.xxx] Premature end of script headers: admin.php, referer: https://www.example.com/wp-admin/
[Fri Oct 26 10:58:14 2012] [warn] [client 190.213.xxx.xxx] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: https://www.example.com/wp-admin/network/index.php
[Fri Oct 26 10:58:15 2012] [error] [client 190.213.xxx.xxx] Premature end of script headers: admin-ajax.php, referer: https://www.example.com/wp-admin/network/index.php
[Fri Oct 26 10:58:56 2012] [warn] [client 190.213.xxx.xxx] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: https://www.example.com/wp-admin/network/index.php
[Fri Oct 26 10:58:57 2012] [error] [client 190.213.xxx.xxx] Premature end of script headers: plugins.php, referer: https://www.example.com/wp-admin/network/index.php
[Fri Oct 26 10:59:18 2012] [warn] [client 190.213.xxx.xxx] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: https://www.example.com/wp-admin/network/index.php
[Fri Oct 26 10:59:18 2012] [error] [client 190.213.xxx.xxx] Premature end of script headers: admin-ajax.php, referer: https://www.example.com/wp-admin/network/index.php
[Fri Oct 26 11:01:49 2012] [warn] [client 190.213.xxx.xxx] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: https://www.example.com/wp-admin/
[Fri Oct 26 11:01:49 2012] [warn] [client 190.213.xxx.xxx] (104)Connection reset by peer: mod_fcgid: ap_pass_brigade failed in handle_request_ipc function, referer: https://www.example.com/wp-admin/

Apache Log:

php (pre-forking): Cannot allocate memory
php (pre-forking): Cannot allocate memory
Recipient names must be specified
Recipient names must be specified
php (pre-forking): Cannot allocate memory
php (pre-forking): Cannot allocate memory
php (pre-forking): Cannot allocate memory
[Fri Oct 26 10:49:33 2012] [warn] mod_fcgid: cleanup zombie process 2852
[Fri Oct 26 10:49:33 2012] [warn] mod_fcgid: cleanup zombie process 2851
[Fri Oct 26 10:49:33 2012] [warn] mod_fcgid: cleanup zombie process 2853
[Fri Oct 26 10:58:22 2012] [warn] mod_fcgid: process 2892 graceful kill fail, sending SIGKILL
php (pre-forking): Cannot allocate memory
[Fri Oct 26 10:59:21 2012] [warn] mod_fcgid: process 2894 graceful kill fail, sending SIGKILL
[Fri Oct 26 10:59:25 2012] [warn] mod_fcgid: process 2866 graceful kill fail, sending SIGKILL

suexec.log:

[2012-10-25 16:05:36]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-25 18:09:38]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-25 18:09:51]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-25 18:14:03]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-25 18:14:06]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-25 18:14:35]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-25 20:20:27]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-25 20:20:29]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-25 20:20:31]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-25 21:42:12]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-25 22:56:50]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-26 02:34:43]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-26 04:25:07]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-26 06:35:19]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-26 06:40:05]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-26 07:22:45]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-26 10:10:05]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-26 10:49:24]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi
[2012-10-26 10:49:24]: uid: (1002/username) gid: (1002/username) cmd: php-fcgi

based on the logs can any determine what might be the cause of this? Thinking that it might be the micro instance I'm thinking of upgrading to a small.

Any help would be greatly appreciated.

This is the output after typing free -m

             total       used       free     shared    buffers     cached
Mem:           590        583          6          0          2         22
-/+ buffers/cache:        559         30
Swap:            0          0          0

I've set up a WordPress multi-site with a wildcard ssl for example.com to access the admin area securely. However I'm also using domain mapping to map other domains to other sites e.g. alldogs.com to alldogs.example.com.

The problem is when I'm trying to access the front end of a site from and admin for a mapped domain e.g. alldogs.com by clicking "Visit Site" the Link goes to https://alldogs.com because of the forced ssl applied to the admin area. Which produces a certificate warning since the certificate is for example.com and not alldogs.com.

How can write a mod_rewrite rule to determine if the url/link clicked on is not the main domain e.g. example.com then change the https:// to http:// so the site can be accessed via port 80 and not generate a certificate warning for that mapped domains

Hi I've installed suexec using on ubuntu 12.04:

apt-get install apache2 apache2-suexec libapache2-mod-fcgid php5-cgi

However when I run the following command:

sudo /usr/lib/apache2/suexec -V

I get the following info:

 -D AP_DOC_ROOT="/var/www"
 -D AP_GID_MIN=100
 -D AP_HTTPD_USER="www-data"
 -D AP_LOG_EXEC="/var/log/apache2/suexec.log"
 -D AP_SAFE_PATH="/usr/local/bin:/usr/bin:/bin"
 -D AP_UID_MIN=100
 -D AP_USERDIR_SUFFIX="public_html"

I'm utilizing "/home/user/public_html" to serve users content on the web not "/var/www" How can I change the root directory to "/home"?

I'm currently setting up WordPress on an Ubuntu server 12 everything runs fine but there is an issue when it comes to automatically updating and uploading media via WP as Apache "www-data" user does not have permissions to write to the directories. "user1" has full permission

All my directories have permissions of 0755 and files 644

my directories setup is as follows:

/home/user1/public_html

All WP files and directories are in "public_html"

In order to work around the auto updating and uploading media I've granted Apache user ownership to the following directories

sudo chown www-data:www-data wp-content -R
sudo chown www-data:www-data wp-includes -R
sudo chown www-data:www-data wp-admin -R

I would like to know security wise how secure this is and if it is not secure what would be the best solution?

That will allow me to keep all files and directories owned by user1 and still allow wp to be able to automatically update and uploading media