On Fri, 4 Apr 2003, Sebastian Breier wrote:

> Hi.
> 
> I just upgraded Apache to 2.0.45 (from 2.0.44),
> and now most of my perl-generated sites crash.
> They worked perfectly before.
> 
> Server is Apache 2.0.45 on W2000 + mod_perl-2 1.99_09-dev,
> as said in the subject.
> 
> I just checked again with 2.0.44, everything works
> (nothing changed except Apache).
> 
> One script still works with 2.0.45, but it has only a few subs
> that don't do anything.
> 
> Logs always show some error message like these:
> 
> [Fri Apr 04 15:49:29 2003] [notice] Parent: child process exited with 
> status 1073807364 -- Restarting.
> or
> [Fri Apr 04 15:46:53 2003] [notice] Parent: child process exited with 
> status 3221225477 -- Restarting.
> 
> Any ideas? Do I need a recompile of mod_perl-2? (I hope
> somebody makes one, I can't)

>From a later message I take it this is with ActivePerl 8xx
(perl-5.8.0)? If not, and you're using ActivePerl 6xx, then it
may be that you're running into a problem that others have also
seen with ActivePerl 6xx and mod_perl 2 on Win32, for which an
upgrade to 8xx would most likely help.

If this is with ActivePerl 8xx, though, then it may be that
there's an incompatibility between modules compiled against
Apache 2.0.44 (which the mod_perl ppm package on our site was
compiled against) and Apache 2.0.45. The Apache group says that,
starting with 2.0.42, they're working at maintaining
configuration and module interface compatibility, so in principle
upgrading from 2.0.44 to 2.0.45 shouldn't be a problem. But with
a combination of Win32 and the relative complexity of mod_perl 2,
this compatibility may not have survived .... I've tried
compiling the current cvs mod_perl 2 sources against Apache
2.0.45, but have run into a problem (unrelated to the 2.0.45
upgrade) that hasn't yet been resolved. Given the security fixes
for Win32 present in 2.0.45, if you feel uneasy about reverting
to 2.0.44, I could make available a mod_perl 2 package based on
not-so-current cvs sources compiled against 2.0.45 until the
problem in the current cvs version is fixed.

-- 
best regards,
randy kobes

Reply via email to