Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > Linux Forums > HOWTO-Related Questions

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 17th April 2010, 00:21
tbirnseth tbirnseth is offline
Junior Member
 
Join Date: Apr 2010
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
 
Default 500 Servier Misconfiguration and Fast CGI

I have some processes that do a lot of calculation or configuration and can take a long time to run. The server grinds away to produce configuration information for various shopping carts. It can take several minutes (wall-clock time) to create a "catalog" to send (sometimes up to 10 minutes). It then takes this catalog and sends it to a shopping cart site usually hosted on the same server. The cart can also take several minutes of wall-clock time to process the data before responding with a result back to the server.

The server gets httpd busy timeout (or one of several different fast_cgi or httpd errors). Probably 3 out of 5 times. I have tried increasing the following values in httpd.conf for the virtual server. However they do not seem to have an affect. I'm a little afraid to increase these values system wide.
#IPCCommTimeout 600
IPCCommTimeout 10800
#Timeout 3000
Timeout 10800
#TB Added
IPCConnectTimeout 60
ProcessLifeTime 10800
IdleTimeout 10800
BusyTimeout 10800
MaxRequestsPerProcess 2048

The user sees a Server 500: Server Misconfiguration Error from Apache.

The virtual server error_log shows:
[Fri Apr 16 13:41:32 2010] [warn] (104)Connection reset by peer: mod_fcgid: read data from fastcgi server error.
[Fri Apr 16 13:41:32 2010] [warn] (104)Connection reset by peer: mod_fcgid: ap_pass_brigade failed in handle_request function

I would like to have the virtual server wait for up to (I used 10800 above just to see if there was a difference) 1200 seconds before it kills the fcgi process - or better yet, just wait.

The processes seem to get killed at between 6 & 7 minutes of wall-clock time. It is NOT failing due to php set_time_limit() expiration or php memory_limit.

Can anyone help me figure this out? I'm pretty much stumped at this point. Appreciate any help/inisight anyone can provide.
Reply With Quote
Sponsored Links
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 19:26.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.