[rt-users] Mod_FastCgi and RT

[Rich West]

I did manage to fix the problem.  It seems that it was directly related 
to the load average and the heavy load on the MySQL server caused by 
spamassassin and it's overly HUGE bayes database.

It seems that, because of the load and delays, apache wasn't able to 
properly fork and change ownership of the process in some mystical 
timeperiod.  Because it took so long, the parent process considered that 
child defunct, and just let it sit there.

Once I disabled the MySQL bayes database for SpamAssassin, everything 
else started working properly.

Thanks for all of those who offered their ideas and comments.  I'm 
happily back to running multiple RT instances with mod_fastcgi. :)

-Rich

>I'm running a current FC2 with mod_fastcgi 2.4.2 (which I think came
>from (http://www.wesmo.com/redhat/i386/mod_fastcgi-2.4.2-1.i386.rpm),
>thanks, and it is running in a virtualhost with no problem.
>  
>
>>So, if I disable the FastCgiServer processes (just commenting them out) 
>>and start up the server, everything comes up just fine..  If I have the 
>>FastCgiServer processes enabled, then 2 or 3 of forked web server 
>>processes run as apache, the rest run as root..
>>    
>>
>
>Oh - you have more than one RT instance...  What happens if you only
>run one?  My FastCgiServer statement is in the global section but the
>scriptalias and AddHandler that invoke it are in a virtualhost.
>  
>
>>Is this just us?! Could this be kernel related?  I've personally been 
>>using RT with mod_fastcgi for ages.. it is just plain odd that it has 
>>tanked out on us like this.
>>    
>>
>
>You may be the only one running multiple instances of RT in one httpd.
>