500's on FormMail.cgi ???

[rpmws]

I am seeing 500's on legitimate FormMail.cgi posts ..I can't even get a simple 2 line form to work on any of my boxes where the scripts are 3.2MB in size ..can anyone else verify? did teh specs change recently?

[TAK]

Not working here either. On more than one server, it shows that the scripts were updated on Jul 19th. So something must have changed...

[dave9000]

Been there already. The formmail.cgi issue is one of the things they borked on the latest EDGE update

Roll back to release and the problem will be fixed.

I spent 2 days looking for the issue and logged a ticket on it but did not get a solution in time so I rolled back to release

This is the ticket I submitted. Looks like they screwed up the perl @INC on the compiled FormMail.cgi as its looking for perl 5.6.2. Even doing a symlink of 5.8.7 to 5.6.2 will not completely resolve this. The FormMail.cgi is calling a undefined routing in Carp.pm but due to FormMail being compiled I can not look at it to see why its screwed.

FormMail.cgi Has failed after update to latest EDGE and also cpan module::build
is missing C_support which can be fixed by installing perlinstaller
ExtUtils::ParseXS

As you can see by the locate command there is not a 5.6.2 perl on this system
so it can not find the libs

Goto undefined subroutine &Carp::shortmess_heavy at
/usr/lib/perl5/5.6.2/Carp.pm line 110.
[Thu Jul 20 09:21:19 2006] [error] [client 71.29.69.104] Premature end of
script headers: /usr/local/cpanel/cgi-sys/FormMail.cgi

root@web2 [/usr/lib/perl5]# locate Carp.pm
/root/perl587installer/perl-5.8.7/lib/CGI/Carp.pm
/root/perl587installer/perl-5.8.7/lib/Carp.pm
/home/cpapachebuild/buildapache/scripts/cPScript/Carp.pm
/home/cpins/installd/perl587installer/perl-5.8.7/lib/CGI/Carp.pm
/home/cpins/installd/perl587installer/perl-5.8.7/lib/Carp.pm
/usr/local/cpanel/Cpanel/Carp.pm
/usr/lib/perl5/5.8.7/CGI/Carp.pm
/usr/lib/perl5/5.8.7/Carp.pm
/usr/lib/perl5/5.8.5/CGI/Carp.pm
/usr/lib/perl5/5.8.5/Carp.pm
/scripts/cPScript/Carp.pm

[rpmws]

I was thinking that I updated this post ..sorry. Nick has it working now and it's in the new edge that should be out shortly.

[dave9000]

I was thinking that I updated this post ..sorry. Nick has it working now and it's in the new edge that should be out shortly.

no problem

Sam was working on it on my end but I could not afford the additional downtime so I had to roll back before they got a resolution