Problem with FastCGI

Hello!

We received a e-mail which triggers the following behaviour:

If I use RT with mod_perl, it works OK.

If I use RT with mod_fastcgi, perl process (spawned by apache)
eats 100% CPU for a long time and then dies. In Apache error_log we have:

[Sat Jun 28 11:19:37 2003] [error] [client 194.87.2.63] FastCGI: comm with serve
r “/usr/local/rt3/bin/mason_handler.fcgi” aborted: idle timeout (300 sec)
[Sat Jun 28 11:19:37 2003] [error] [client 194.87.2.63] FastCGI: incomplete head
ers (0 bytes) received from server “/usr/local/rt3/bin/mason_handler.fcgi”

The affected E-mail remains in the mail queue, and in the maillog we have:

Jun 28 11:17:38 vh postfix/local[22813]: E966C16E728: to=info@vh.demos.su, ori
g_to=, relay=local, delay=49241, status=deferred (temporary failure. Comma
nd output: An Error Occurred ================= 500 read timeout )

We switched to mod_fastcgi yesterday and received about 100 messages since
that time. It is the only message which RT was unable to process.

Any help will be greatly appreciated.

Thanks!

We received a e-mail which triggers the following behaviour:
If I use RT with mod_perl, it works OK.

If I use RT with mod_fastcgi, perl process (spawned by apache)
eats 100% CPU for a long time and then dies. In Apache error_log we have:

Can you make the email available? We can guess at what the problem
might be, but that would be quite unproductive.

We received a e-mail which triggers the following behaviour:
If I use RT with mod_perl, it works OK.

If I use RT with mod_fastcgi, perl process (spawned by apache)
eats 100% CPU for a long time and then dies. In Apache error_log we have:

Can you make the email available? We can guess at what the problem
might be, but that would be quite unproductive.

This is really strange. During this day, we collected four such messages.
But after apache restart, they all passed.

Now I tried to bounce them back to RT (I also have copies of the original
messages as they were before RT processing) and they were succesfully
processed.

So it seems that such a behaviour exhibits only after RT received a
number of messages.

I’ll investigate this a bit more.

I am running rt2-to-rt3-v1.13 but I don’t see any metadata created
anywhere in my filesystem. Am I doing something wrong ? Has anyone else
experinecd this before ?

Thanks
Asif Iqbal

I am running rt2-to-rt3-v1.13 but I don’t see any metadata created
anywhere in my filesystem. Am I doing something wrong ? Has anyone else
experinecd this before ?

You must create the dumpdir/output dir by hand first.

mkdir outputdir
rt2-to-rt3.pl outputdir

I realized that after I re-read the README …doh :slight_smile:

I also added a die statement to avoid future occurance of this. Would be
nice if it gets added to the v1.14 ;-)On Sun, 29 Jun 2003, Robert Spier wrote:

I am running rt2-to-rt3-v1.13 but I don’t see any metadata created
anywhere in my filesystem. Am I doing something wrong ? Has anyone
else
experinecd this before ?

You must create the dumpdir/output dir by hand first.

mkdir outputdir
rt2-to-rt3.pl outputdir