[rt-users] Perl upgrade Broke my RT!

[Rich West]

Actually, although I got those "Could not send mail." messages, my test 
message did go through and I did receive an auto reply.

Hrmm.. I wonder if there are other addresses in one of the scrips that 
are bad.  Still the "Could not send mail" message gives me the chills.

Anyhow, I'm now running the standalone_httpd since I cannot seem to get 
Apache to display (using mod_perl) the site any longer. :(

I'd prefer to use Apache because it is threaded and already had the 
mechanism in place to handle all of the load, but I'm not getting 
anything logged anywhere, and I simply get a "Zero Sized Reply".

-Rich

> We upgraded a couple of perl libraries due to some requirements from 
> another application (relaydelay), and, while things worked through the 
> night, this morning it was discovered that our RT installation was no 
> longer displaying pages!
>
> Hence, we get a zero sized reply, and emails to RT fail.
>
> In a panic, we upgraded to 3.4.2 and the results were the same. :(  I 
> did notice the new standalone_httpd, which prompted for a quick test.  
> Viola!  The site was accessible and functional!  Great.
>
> Then, I saw a number of messages on STDOUT similar to the following:
> [Thu Jul 21 17:42:18 2005] [crit]: 
> <rt-3.4.2-15930-185295-6.7.1573970583762 at oursite.org>Could not send 
> mail. (/var/www/html/oursite.org/rt3/lib/RT/Action/SendEmail.pm:280)
>
> Ack!  A quick check showed that RT was unable to send email.
>
> Anyone have any ideas on how to debug this?  I'm in a bit of a panic 
> and at a loss as to how to pull more information out of RT to 
> determine WHY it cannot send email.
>
> Thanks!
> -Rich