RE: redirect
I don't know if it's any help to anyone but if it is,
it seems the reason the usual redirect didn't work for me as it should, was
due to screen output after the redirect command
$r->headers_out->set(Location => '../index.pl');
$r->status(Apache2::Const::REDIRECT);
$r->headers_out;
# Print qq ( test ); # not a good idea
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Perrin
Harkins
Sent: Sunday, October 07, 2007 12:41 AM
To: Eli Shemer
Cc: Issac Goldstand; modperl@perl.apache.org
Subject: Re: redirect
On 10/6/07, Eli Shemer <[EMAIL PROTECTED]> wrote:
> $r->headers_out->set("Refresh"=>"0;url=index.pl");
>
> $r->headers_out;
> return Apache2::Const::OK;
>
> this method seems to be the best solution for me since
> 1. it works
> 2. I rather send an OK signal since it's not an actual warning/error but a
> valid redirect as part of the system.
There's no reason to avoid using a normal redirect in this case. It's
not an error and will not be written to the error_log. I'm not sure
all browsers will honor this trick you're using, but they definitely
will work with a standard 302 response.
- Perrin
removing temporary uploaded files
Hi List, Background: I don't not now for sure, but I think that apache stores files you upload with and in a directory on the server temporarily and then hands the input stream off to your script. Does anybody know a way I can cofigure apache to automatically delete these temporarily uploaded files. Thanks Tyler
Re: Apache crashing
Perrin Harkins wrote: > On 10/10/07, Ian G. Tyndall <[EMAIL PROTECTED]> wrote: >> Apache version: 2.2.6 > > There was a thread earlier about that version not being an official > apache release. If you mix and match binaries from multiple sources > you are likely to have trouble. Have you tried the binaries that > Randy provides? FYI 2.2.6 was released (2.2.5 was not) and discovered to have an incompatibility with modperl. You'll note that 2.2.4 downloads are still available from the same mirrors to help tide you over for 2.2.7, where we hope this is all addressed.
Re: Apache crashing
On 10/10/07, Ian G. Tyndall <[EMAIL PROTECTED]> wrote: > Apache version: 2.2.6 There was a thread earlier about that version not being an official apache release. If you mix and match binaries from multiple sources you are likely to have trouble. Have you tried the binaries that Randy provides? http://perl.apache.org/download/binaries.html - Perrin
RE: Apache crashing
Thanks for the reply! I do have these in my conf already (sorry, should've been more specific): LoadFile Perl/bin/perl58.dll LoadModule perl_module modules/mod_perl.so But, I don't have the others. I added the following to my conf: LoadFile "X:/Apache2.2/bin/libapreq2.dll" LoadModule apreq_module modules/mod_apreq2.so And, I get this error: httpd.exe: Syntax error on line 183 of X:/Apache2.2/conf/httpd.conf: API module structure 'apreq_module' in file X:/Apache2.2/modules/mod_apreq2.so is garbled - expected signature 41503232 but saw 41503230 - perhaps this is not an Apache module DSO, or was compiled for a different Apache version? Apache version: 2.2.6 Any thoughts/suggestions? -Original Message- From: Foo JH [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 10, 2007 3:51 AM To: Ian G. Tyndall Cc: modperl@perl.apache.org Subject: Re: Apache crashing Your conf does not look complete. For example, I don't even see the following lines: LoadFile Perl/bin/perl58.dll LoadModule perl_module modules/mod_perl.so LoadFile bin/libapreq2.dll LoadModule apreq_module modules/mod_apreq2.so Ian G. Tyndall wrote: > My virtual host: > > > ServerName mysite.com > DocumentRoot "X:/htdocs/sites/mysite_dev" > ScriptAlias /cgi-bin/admin/ > "X:/htdocs/sites/mysite_dev/cgi-bin/admin/" > ErrorLog logs/rt-error.log > > Options +ExecCGI > Order allow,deny > Allow from all > > SetHandler perl-script > PerlHandler ModPerl::Registry > PerlSendHeader On > > > > > Earlier in the conf, I'm doing: > > PerlSwitches -IX:/perl/5.8.8/site/lib > PerlInitHandler Apache2::Reload > PerlHandler ModPerl::Registry > > -Original Message- > From: Foo JH [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 09, 2007 12:43 PM > To: Ian G. Tyndall > Cc: modperl@perl.apache.org > Subject: Re: Apache crashing > > What's your modperl config like? > > Ian G. Tyndall wrote: > >> Ok, I decided to upgrade my Apache to see if that would fix things. >> >> I installed 2.2.4, and I was getting the same error as originally >> reported... but more often. >> Then, I upgraded to 2.2.6 from the Apachelounge... and now I'm >> getting >> > > >> an error. >> >> The error is as follows: >> >> [Tue Oct 09 08:50:20 2007] [error] [client 192.168.3.28] failed to >> resolve handler `ModPerl::Registry': Can't load >> 'X:/perl/5.8.8/site/lib/auto/Apache2/RequestRec/RequestRec.dll' for >> module Apache2::RequestRec: load_file:The specified procedure could >> not be found at X:/perl/5.8.8/lib/XSLoader.pm line 64.\n at >> X:/perl/5.8.8/site/lib/Apache2/XSLoader.pm line 31\nCompilation >> failed >> > > >> in require at X:/perl/5.8.8/site/lib/ModPerl/RegistryCooker.pm line >> 32.\nBEGIN failed--compilation aborted at >> X:/perl/5.8.8/site/lib/ModPerl/RegistryCooker.pm line >> 32.\nCompilation >> > > >> failed in require at (eval 5) line 3.\n\t...propagated at >> X:/perl/5.8.8/lib/base.pm line 91.\nBEGIN failed--compilation aborted >> at X:/perl/5.8.8/site/lib/ModPerl/Registry.pm line 26.\nCompilation >> failed in require at (eval 4) line 3.\n >> >> I did do a fresh install of ModPerl 2.0.3, and I've seen similar >> "failed to resolve handler" messages on the web... but nothing like >> > this. > >> Any suggestions/thoughts! >> >> Thanks again, >> Ian >> >> >> -Original Message- >> From: Randy Kobes [mailto:[EMAIL PROTECTED] >> Sent: Thursday, October 04, 2007 3:40 PM >> To: Ian G. Tyndall >> Cc: modperl@perl.apache.org >> Subject: Re: Apache crashing >> >> On Thu, 4 Oct 2007, Ian G. Tyndall wrote: >> >> >> >>> Oh the problems come and go so quickly! >>> >>> I've got one cgi script that always crashes apache. The error log >>> gives the following message: >>> >>> [Thu Oct 04 11:38:29 2007] [crit] (22)Invalid argument: Parent: >>> Failed >>> >>> >> >> >>> to create the child process. >>> [Thu Oct 04 11:38:29 2007] [crit] (OS 6)The handle is invalid. : >>> master_main: create child process failed. Exiting. >>> [Thu Oct 04 11:38:29 2007] [notice] Parent: Forcing termination of >>> child process 2474288 >>> >>> Other scripts run fine... so what would be the best way of debugging >>> this. >>> >>> I'm in the process of commenting out modules/code, but no luck so >>> >>> >> far... >> >> >>> any recommendations? >>> >>> I'm using mod_perl 2.0.3, perl 5.8.8, apache 2.0.59 on a Windows >>> 2003 >>> > > >>> server. >>> >>> Thanks, >>> Ian >>> >>> >> Is this a cgi script, or a mod_perl registry script? >> Although the log messages are generic, similar messages appear when >> one tries to restart apache with mod_perl enabled - if it's a cgi >> script, does commenting out the loading of mod_perl.so help? >> >> As for tracking down the problem, reducing it to a minimal version >> will help. If you can do this, and don't see the problem, try posting >> it
Re: Apache crashing
Your conf does not look complete. For example, I don't even see the following lines: LoadFile Perl/bin/perl58.dll LoadModule perl_module modules/mod_perl.so LoadFile bin/libapreq2.dll LoadModule apreq_module modules/mod_apreq2.so Ian G. Tyndall wrote: My virtual host: ServerName mysite.com DocumentRoot "X:/htdocs/sites/mysite_dev" ScriptAlias /cgi-bin/admin/ "X:/htdocs/sites/mysite_dev/cgi-bin/admin/" ErrorLog logs/rt-error.log Options +ExecCGI Order allow,deny Allow from all SetHandler perl-script PerlHandler ModPerl::Registry PerlSendHeader On Earlier in the conf, I'm doing: PerlSwitches -IX:/perl/5.8.8/site/lib PerlInitHandler Apache2::Reload PerlHandler ModPerl::Registry -Original Message- From: Foo JH [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 09, 2007 12:43 PM To: Ian G. Tyndall Cc: modperl@perl.apache.org Subject: Re: Apache crashing What's your modperl config like? Ian G. Tyndall wrote: Ok, I decided to upgrade my Apache to see if that would fix things. I installed 2.2.4, and I was getting the same error as originally reported... but more often. Then, I upgraded to 2.2.6 from the Apachelounge... and now I'm getting an error. The error is as follows: [Tue Oct 09 08:50:20 2007] [error] [client 192.168.3.28] failed to resolve handler `ModPerl::Registry': Can't load 'X:/perl/5.8.8/site/lib/auto/Apache2/RequestRec/RequestRec.dll' for module Apache2::RequestRec: load_file:The specified procedure could not be found at X:/perl/5.8.8/lib/XSLoader.pm line 64.\n at X:/perl/5.8.8/site/lib/Apache2/XSLoader.pm line 31\nCompilation failed in require at X:/perl/5.8.8/site/lib/ModPerl/RegistryCooker.pm line 32.\nBEGIN failed--compilation aborted at X:/perl/5.8.8/site/lib/ModPerl/RegistryCooker.pm line 32.\nCompilation failed in require at (eval 5) line 3.\n\t...propagated at X:/perl/5.8.8/lib/base.pm line 91.\nBEGIN failed--compilation aborted at X:/perl/5.8.8/site/lib/ModPerl/Registry.pm line 26.\nCompilation failed in require at (eval 4) line 3.\n I did do a fresh install of ModPerl 2.0.3, and I've seen similar "failed to resolve handler" messages on the web... but nothing like this. Any suggestions/thoughts! Thanks again, Ian -Original Message- From: Randy Kobes [mailto:[EMAIL PROTECTED] Sent: Thursday, October 04, 2007 3:40 PM To: Ian G. Tyndall Cc: modperl@perl.apache.org Subject: Re: Apache crashing On Thu, 4 Oct 2007, Ian G. Tyndall wrote: Oh the problems come and go so quickly! I've got one cgi script that always crashes apache. The error log gives the following message: [Thu Oct 04 11:38:29 2007] [crit] (22)Invalid argument: Parent: Failed to create the child process. [Thu Oct 04 11:38:29 2007] [crit] (OS 6)The handle is invalid. : master_main: create child process failed. Exiting. [Thu Oct 04 11:38:29 2007] [notice] Parent: Forcing termination of child process 2474288 Other scripts run fine... so what would be the best way of debugging this. I'm in the process of commenting out modules/code, but no luck so far... any recommendations? I'm using mod_perl 2.0.3, perl 5.8.8, apache 2.0.59 on a Windows 2003 server. Thanks, Ian Is this a cgi script, or a mod_perl registry script? Although the log messages are generic, similar messages appear when one tries to restart apache with mod_perl enabled - if it's a cgi script, does commenting out the loading of mod_perl.so help? As for tracking down the problem, reducing it to a minimal version will help. If you can do this, and don't see the problem, try posting it to the list here. Also, trying some of the debugging tips suggested in the thread http://marc.info/?t=11913767701&r=1&w=2 may help, along with installing http://www.apache.org/dist/httpd/binaries/win32/#source to help in the crash analysis. -- best regards, Randy
