Updating, recompiling, VirtualHost templates, customizations,  php safemode …Apache stops responding but is running

Updating, recompiling, VirtualHost templates, customizations,  php safemode …Apache stops responding but is running A few things that could cause that are:

Possible Causes:

1) MaxClients is set to a value that is too low
2) If you have more or over about 800 VirtualHost entries (domains, subdomain, ssl, etc.. ), the ErrorLog files open too many of file descriptors and apache will not be able to log the errors and may stop responding.

These numbers can vary per box depend on the limits, and setup of the system. (lower/higher)


1) edit  /etc/httpd/conf/httpd.conf and then increase the MaxClients setting to the something like 200 or 300.

cd /usr/local/directadmin/data/templates
cp virtual_host*.conf custom
cd custom

# try remove all the ErrorLog lines (or comment though them out) from the 4 virtual_host*.conf files that are in the custom directory.

perl -pi -e ‘s/Error/#Error/’ virtual_host*.conf
echo “action=rewrite&value=httpd” >> /usr/local/directadmin/data/task.queue

The Apache should be restarting automatically after a few minutes later (rewrite might take a while with over 800 sites).

If that is not enough to lower the limit and the problem still persists, then try commenting out the CustomLog entries:

perl -pi -e ‘s/CustomLog/#CustomLog/’ virtual_host*.conf


and then repeat the above echo commands to rewrite the httpd.conf files.

3) Other possible information:
Edit /usr/include/bits/typesizes.h and /usr/include/linux/posix_types.h and set
#define __FD_SETSIZE 32768
and then recompile with customapache or custombuild.

On FreeBSD, it’s /usr/include/sys/select.h or /usr/include/sys/types.h
#define FD_SETSIZE      1024U
#define FD_SETSIZE      32768U

then recompile apache/php

4) edit /etc/sysctl.conf and add:
fs.file-max = 32768

and run:




then recompile apache/php

Other possible entires for the sysctl.conf:
kern.maxfiles = 32768
kern.maxfilesperproc = 32768

5) Another way for free up FileDescriptors (FDs) is to disable ssl on any domains that does not require it at all.
A quck way to check is to type:

ls -la /home/*/domains/*/private_html/index.html

Tryt quickly scan the list for any index.html that isn’t between 200-300 bytes in size.  Any that are not in that range will have been editing and the user is probably using ssl, so take note of those usernames and domains.

And Now, the quick way to do a mass SSL shut-off for domains is to type:

perl -pi -e ‘s/ssl=ON/ssl=OFF/’ /usr/local/directadmin/data/users/*/domains/*.conf

Back Then turn ssl=ON back on for any users those who need it.  Note that this is an end user level setting, so they have the ability to turn it back on themselves via Domain Setup.  Then type the action=rewrite&value=httpd command as it mentioned in step 2 above.
What of this does is reduced the number of FD’s by 50%.

6) Openssl bug.  Either update openssl and recompile apache, or patch apache 2:

Related error messages are:


[error] System: Too many open files in system (errno: 23)

host: isc_socket_create: not enough free resources socket.c:2117: REQUIRE(maxfd <= (int)1024) failed.
host: isc_socket_create: not enough free resources

Also, exim may throw the following error is exim is calling through a php script:

R=lookuphost defer (-1): host lookup did not complete

Lowering the numbers of Filedescriptors apache uses will help, if the file decriptor limit is the reason for the error.

Leave a Reply

Your email address will not be published. Required fields are marked *