On Jun 16, 2009, at 7:54 PM, Charles Jones wrote:

> fouldragon@aol.com wrote:
>>
>> I suspect it's some Apache setting knocking the users off, since  
>> Apache
>> claims responsibility for the 403, but can anyone give me a good  
>> place
>> to start looking?  I don't want to just dump the httpd.conf from the
>> other server (which is a LITTLE different configuration-wise) on here
>> and hope.
> Is the script in question a php script?  Check the error log
> (/var/log/httpd/error_log). I suspect you are hitting the limit of
> database connections, which would make the script error out.

5 or 6 hits per second is a pretty low limit.  You need to figure out  
where in the client -> Apache -> PHP -> MySQL chain your getting  
clogged up.  As Charles suggested, watch your error logs.  Your PHP  
error log might end up somewhere else, depending on the error_log  
directive in php.ini.

In your apache config, maybe check your MaxClients and ServerLimit  
parameters.
   http://httpd.apache.org/docs/2.0/mod/mpm_common.html#maxclients
   http://httpd.apache.org/docs/2.0/mod/mpm_common.html#serverlimit

Open a mysql client while you hit this page, and run 'SHOW  
PROCESSLIST;' every few seconds.  You'll see all the currently-running  
queries, and how long they're taking.  You have some badly-optimized  
query which is slowing the whole process down.  If you want to do this  
frequently, Google for mytop, which is like top, but for watching a  
MySQL server.

alex


> That, or
> hitting a php memory or execution limit, all of which can be fixed by
> tweaking the php.ini or my.cnf.
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>