RE: RedHat 8.0 standard Apache2.0 and mod_perl 2.0::PerlRun doesn't work?

[Dale Lancaster]

Thanks for the information.  I did try removing Apache:DBI, but it still
fails.  Building everything from source will be time consuming.  If I do
that,  I will probably just drop back to Apache 1.3 since I know it works.
If I can, I will attempt to produce a simple CGI script that fails.  The
ones that I have in place are simply too complex to send off to you.  I will
try to narrow it down since I want to stick with the latest stuff.  I
suspect would of the internal handlers is just not staying hooked up.  The
debugging show it getting to the eval statement for the script, but it
appears as though either the script is empty or it never really eval'd, even
though a positive return came back.

I'll try to get you something to work with...
thanks!
dale


-Original Message-
From: Stas Bekman [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 24, 2002 8:21 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: RedHat 8.0 standard Apache2.0 and mod_perl 2.0::PerlRun
doesn't work?


Dale Lancaster wrote:
 I have searched the archives and various websites to find my problem and
 its associated resolution to no avail.

 I upgraded my working Apache 1.3 and mod_perl 1.x website using the
 PerlRun option of modperl to the RedHat 8.0 standard release with
 Apache/mod_perl 2.0 combo -- bad move it appears.

ModPerl::Registry and friends are in beta now. I've ported the 1.0's
version and made it a bit more modular via ModPerl::RegistryCooker. It's
quite possible that I broke some of the functionalities while porting as
you saw in the recent bug fix. The problem is that I couldn't verify
whether the porting was 1:1 because there was no exhaustive test suite.
For 2.0 we are hoping to have one.

First, disable Apache::DBI. Does the problem persist?

Second, please download the latest cvs versions of apache and mod_perl
and try again. Does the problem persist?

If it does, please send a short script that reproduces the problem, and
hopefully a self-contained one, so it's not relying on mysql. In short,
think of it this way: To solve the problem, I need to reproduce it
first. So help me to accomplish that first.


__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

RedHat 8.0 standard Apache2.0 and mod_perl 2.0::PerlRun doesn't work?

[Dale Lancaster]

I have 
searched the archives and various websites to find my problem and its associated 
resolution to no avail.

I 
upgraded my working Apache 1.3 and mod_perl 1.x website using the PerlRun option 
of modperl to the RedHat 8.0 standard release with Apache/mod_perl 2.0 combo -- 
bad move it appears.

When I 
start mod_perl on my website, the first couple of CGI loads on a given script 
work and then I begin to receive blank page responses. Meaning,I 
refresh the page and the response is just blank. No errors, no text (other 
than a standard header). Looking in the log file all I see 
is:

[24/Dec/2002:12:56:10 -0500] "GET /cgi-bin/filter.cgi?Mode=ListApplicants 
HTTP/1.1" 200 0 "http://mysite.com/cgi-bin/jobs.cgi?Mode=DisplayResponses" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; 
Q312461)"

and the error log 
indicates no errors at all. Note the above that I have a 200 status with 0 
bytes, when in reality when it does work, it should show several thousand bytes 
of transfer. After a few more refreshes, I get output that I expect. 
This happens with all of my scripts, not just the same one. If I restart 
the server, it always works the first time. Invariably the first and 
subsequent refreshes tend to fail (produce blank pages).

I have enabled any 
and all types of debugging. I found in RegisteryCooker where I could 
enable some debugging and it shows it going through, loading and compiling the 
script, running it and then flushing the namespace, but no HTML output 
occurs. 

I am using the 
prefork() MPM and fiddled with various settings to no avail. I have 
ensured that caching is disabled, I have played with mod_expire settings, moved 
the mod_perl module to be loaded first and all kinds of stuff just to try and 
get the behavior to change, all to no avail as well. I also used some 
suggestions on how to use the mod_perl::Registry with settings to force it to 
restart threads everytime and it doesn't work either. My scripts all use 
DBI with mysql. I have noticed that the mysql server is not being hit when 
the script produces a blank response. So that tells me that either the 
"eval{}" call in RegistryCooker is really not working somehowor the script 
is simply not running, but producing no errors anywhere. I don't know why 
the eval{} call to run my script would work the first time and fail the second 
time, strange.

My perlrun 
configuration is:

PerlModule 
Apache2PerlModule Apache::DBIPerlRequire 
/etc/httpd/conf.d/startup.pl

Directory /home/usa/cgi-bin 
SetHandler perl-script PerlHandler 
ModPerl::PerlRun PerlSendHeader On 
PerlOptions +ParseHeaders Options ExecCGI FollowSymLinks 
Includes/Directory

startup.pl 
contains:

# This will give 
us a stack trace when a perl script dies#$SIG{__WARN__} = 
\Carp::cluck;

# Load CGI.pm and 
call its compile() method to precompile# (but not to import) its autoloaded 
methods.use CGI ();CGI-compile(':all');

use Apache::DBI() 
;use DBI() ;
All the scripts run 
fine without mod_perl, and in fact ran just fine on the old Apache 1.x system 
with mod_perl. I am at the end of my wits on this one and looking for 
ideas.

Thanks
dale