[rt-users] Large # of tickets - internal server error?

[Jamie Wilkinson]

This one time, at band camp, Mike Dydyk wrote:
>So, my question comes down to, why is perl using up so much CPU?  I thought
>using fastcgi would avoid mod_perl, so what exactly is using perl (fastcgi
>itself?).  I am far from an expert on perl, so that's probably part of the
>problem.  My mod_perl, from the ports collection, is built as a module.  So
>I know mod_perl won't work properly with RT, but I went with fastcgi to
>avoid that problem..shouldn't I be ok?  I hope I have provided enough
>details, if you need anything else let me know via the list or a private
>email and I'll get back to you ASAP.  Thanks.

There's a difference between mod_perl and perl.

RT is written in the language known as perl.  mod_perl is an apache module
that loads the interpreter for the language perl into the webserver itself.
mod_fastcgi is an apache module that keeps persistent copies of CGIs, thus
reducing the amount of overhead required to launch the CGI (in this case the commandline interpreter for the language perl).  So, you can either run RT
"inside" the webserver with mod_perl, or you can run RT as a CGI and
connect it to the webserver using mod_fastcgi.  Either way, though, you are
going to be invoking some sort of perl interpreter.

Also note:  mod_perl _does_ work properly with RT.  Most people use it that
way.  Only the mod_perl built for Apache 2 on Red Hat 8.0 and 9 seem to have
problems; there is nothing inherently wrong with using mod_perl on any other
operating system.

Anyway, to answer your question, we'd need to know a bit more about your
webserver, how about clagging the RT specific parts of the configuration to
the list?

You say you currently have both mod_perl and mod_fastcgi installed, so which
one are you using?

-- 
jaq at spacepants.org                           http://spacepants.org/jaq.gpg