Server Too Busy Problem

[necblog]

Hello
i have a server : Core2 Quad Q9400 + 8GB of ram which load average is about 0.20 and memory usage is about 5%
and i see this error : Server Is too busy at the moment please check back again
but i have some Security configs :
PHP safe_mod = on
disable_functions="link,symlink,readlink,ini_get,php_uname,exec,syste m,passthru,shell_exec,escapeshellarg,escapeshellcm d,proc_close,proc_open,ini_alter,dl,popen,curl_exe c,popen,pcntl_exec,socket_accept,socket_bind,socke t_clear_error,socket_close,socket_connect,socket_c reate_listen,socket_create_pair,socket_create,sock et_get_option,socket_getpeername,socket_getsocknam e,socket_last_error,socket_listen,socket_read,sock et_recv,socket_recvfrom,socket_select,socket_send, socket_sendto,socket_set_block,socket_set_nonblock ,socket_set_option,socket_shutdown,socket_strerror ,socket_write,stream_socket_client,stream_socket_s erver,fsockopen,pfsockopen,stream_set_timeout,disk _total_space,disk_free_space,chown,getrusage,get_c urrent_user,set_time_limit,getmyuid,getmypid,dl,le ak,listen,chgrp,link,symlink,dlopen,proc_nice,proc _get_stats,proc_terminate,shell_exec,sh2_exec,posi x_getpwuid,posix_getgrgid,posix_kill,ini_restore,m kfifo,dbmopen,dbase_open,filepro,filepro_rowcount, posix_mkfifo,putenv,sleep"


and some mod_sec configs do you think this is because of my PHP configs?

--------------- Added 1238223488 at 1238223488 ---------------

another thing server too busy page is not a vbulletin page it is a Blank page

[TigerC10]

Is this your dedicated server? Your website is the only website on the box?

Are you the one that installed the webhosting application (apache/IIS)?

Do you have access to php.ini? If so, you should check the memory_limit variable in php.ini.

Also, check your php.ini extension list. Make sure that only the extensions you need (like GD) are enabled. Also, check the extension directory variable to see if it matches the PHP extension directory on the server (check to make sure all of the enabled extensions are in the extension directory).

I just did a little research and found that the Zend Optimizer has this problem thanks to some caching feature. If you're using Zend, you should contact them regarding this problem.

[necblog]

No it is a shared server but i am server admin.
memory_limit is set to 32MB
i use memcache that is compatible with Zend.
are extensions are there because i use cpanel/whm and i have compiled php by easyapache

[TigerC10]

Yeah, I just told you that the "server too busy" problem can come from Zend's caching feature. Go ask for support over there:

http://www.zend.com/en/services/support/

[snakes1100]

1st you need to check the apache logs and verify what the real issue is.

Seeing as you have root access to the server, verify apaches log location, as it varies from O/S to O/S, as well its dependent on the control panel installed.

Run this cmd to find out apaches current running location.

ps ax | grep httpd

Linux
tail -f /etc/httpd/logs/error_log
tail -f /usr/local/apache/logs/error_log

Debian
tail -f /var/log/apache2/error.log

You may need to enable apache's debug mode.
Edit httpd.conf or apache.conf (this varies from OS to OS as well.)
Add or edit to show the following and HUP apache

LogLevel debug

[kermit2]

vbulletin has it's own 'too busy' message, although I think it's something like 'forum too busy' - there's an option to control it in the ACP. Sounds like it isn't this though.

Sounds to me more like you're exceeding Apache's max clients. Try grepping for MaxClients in your Apache config file, then run:

ps aux|grep apache|wc -l

(may need to grep for httpd instead), to see how many clients it is currently serving. If the output of the above command is regularly getting close to your MaxClients, you could see about raising MaxClients. That's assuming your server can handle more clients.

You might want to see about lowering your KeepAliveTimeout a little too, if KeepAlive is turned on. That should result in each Apache process hanging around for less time after it has served the request(s), which will reduce the number of concurrent processes

[snakes1100]

If he is hitting maxclients, it's 100% doubtful his server will respond until he restarted apache.

If the server was loaded up by reaching maxclients, it wouldn't respond with a blank page, it wont respond at all.