> -----Original Message----- > From: Stan Kaushanskiy [mailto:stan@xxxxxxxxxxxxx] > Sent: Thursday, September 28, 2006 6:26 PM > To: users@xxxxxxxxxxxxxxxx > Subject: Re: [users@httpd] Apache 2.2.3 CGI OS 5 Issue under load > > Boyle Owen wrote: > >> -----Original Message----- > >> From: Stan Kaushanskiy [mailto:stan@xxxxxxxxxxxxx] > >> Sent: Wednesday, September 27, 2006 9:16 PM > >> To: users@xxxxxxxxxxxxxxxx > >> Subject: [users@httpd] Apache 2.2.3 CGI OS 5 Issue under load > >> > >> Hi All, > >> > >> I am running a cgi program through Apache 2.2.3. Usually > everything > >> works fine, > >> but sometimes under load and after about 1-2 hours continuous > >> requests, > >> I get the following error in the apache log: > >> > >> [Tue Sep 26 19:08:16 2006] [error] [client 192.168.26.155] > >> (OS 5)Access > >> is denied. : couldn't set child process attributes: > >> E:/php/php-cgi.exe > >> [Tue Sep 26 19:08:16 2006] [error] [client 192.168.26.155] > >> (OS 5)Access > >> is denied. : couldn't spawn child process: E:/php/php-cgi.exe > >> > >> [Wed Sep 27 11:25:22 2006] [error] [client 192.168.26.155] > >> (OS 5)Access > >> is denied. : couldn't set child process attributes: > >> E:/cgi-bin/UploadProcessor.exe > >> [Wed Sep 27 11:25:22 2006] [error] [client 192.168.26.155] > >> (OS 5)Access > >> is denied. : couldn't spawn child process: > >> E:/cgi-bin/UploadProcessor.exe > >> > >> This error happens with both PHP 5.1.6 as well as with a CGI > >> I compiled > >> from C++, so it cannot be a php issue. > >> > >> I have around 50 - 150 clients hitting the server every 10 > >> seconds. The > >> CGI processes are "long-lived" they take 1 second to 3 > minutes to do > >> their thing. > >> > > > > Probably some statistician could come up with the correct Bayesian > > formula for this, but off the top of my head, if you have about 10 > > hits/sec and each hit takes about a minute to process > (mid-point of your > > ranges), then every second you add 10 processes and it > takes 1 minute > > before any resources are free again, so you peak at about > 600 concurrent > > processes. That seems a lot for a PC... > > > > I would guess that you're simply running out of resources. > > > > I never have more than 150 concurrent connections. I have > plenty of RAM > free. > What resources might I be running out of? File-handles? > Is there any way > to find out > which resources are the problem? Check the process table/Task Manager? I'm not an expert on XP so can't really help you further there... Rgds, Owen Boyle Disclaimer: Any disclaimer attached to this message may be ignored. > > thanks, > > stan > > > Rgds, > > Owen Boyle > > Disclaimer: Any disclaimer attached to this message may be ignored. > > > > > >> I have not noticed the lifetime of the cgi processes affecting this > >> behavior. > >> > >> When these errors happen the clients get 500 errors. > >> > >> Prior to 2.2.3 I ran Apache 2.0.52 and the same issues happened. > >> > >> My Setup: > >> P4 3Ghz HT > >> 1 GB Ram > >> Windows XP Pro > >> Apache 2.2.3 > >> > >> any ideas? > >> > >> thanks, > >> > >> stan > >> > >> > >> > >> > --------------------------------------------------------------------- > >> The official User-To-User support forum of the Apache HTTP > >> Server Project. > >> See <URL:http://httpd.apache.org/userslist.html> for more info. > >> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > >> " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > >> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > >> > >> > > > > > > This message is for the named person's use only. It may > contain confidential, proprietary or legally privileged > information. No confidentiality or privilege is waived or > lost by any mistransmission. If you receive this message in > error, please notify the sender urgently and then immediately > delete the message and any copies of it from your system. > Please also immediately destroy any hardcopies of the > message. You must not, directly or indirectly, use, disclose, > distribute, print, or copy any part of this message if you > are not the intended recipient. The sender's company reserves > the right to monitor all e-mail communications through their > networks. Any views expressed in this message are those of > the individual sender, except where the message states > otherwise and the sender is authorised to state them to be > the views of the sender's company. > > > > > --------------------------------------------------------------------- > > The official User-To-User support forum of the Apache HTTP > Server Project. > > See <URL:http://httpd.apache.org/userslist.html> for more info. > > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > > > > > > > -- > Stan Kaushanskiy > PC-Doctor, Inc. > 9805 Double R Boulevard, Suite 301 > Reno, NV 89521 > 775-336-4039 (direct) > stan@xxxxxxxxxxxxx > > CONFIDENTIALITY > The information contained in this message is confidential. It > is intended to be read only by the individual or entity to > whom it is addressed or by an authorized designee. If the > reader of this message is not the intended recipient, be > aware that distribution of this message in any form is > strictly prohibited. If you have received this message in > error, please immediately notify the sender and destroy any > copy of this message. > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP > Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|