Here it is what it happened:
I've installed:
Apache/2.2.4 (Win32), Server built: Jan 9 2007 23:17:20
perl, v5.8.8 built for MSWin32-x86-multi-thread built 822
latest mod_perl from TheoryX
After installing them, I started the web server and it worked fine and I
could access the success page.
I have tried stopping and starting it for more times with success.
Then I've created a default Catalyst app named "Testing", using:
catalyst Testing
I was able to access the "Testing" application using its internal web
server, so it is working.
Then I've created a virtual host for calling that Catalyst application. Here
is the content of that virtualhost:
<Virtualhost 127.0.0.1:80>
ServerName www.brk.ro
ServerAdmin [EMAIL PROTECTED]
DocumentRoot e:/web/Testare/root
ErrorLog e:/web/Testare/logs/error.txt
CustomLog e:/web/Testare/logs/access.txt common
<IfModule mod_perl.c>
PerlRequire "e:/web/Testare/script/preload.pl"
<Location />
Options Indexes
Order allow,deny
Allow from all
SetHandler perl-script
PerlResponseHandler Testare
</Location>
</IfModule>
</Virtualhost>
Of course, I created the directory "logs" under the "Testing" app directory,
and I also created the program preload.pl that just "use" the "Testing"
module.
And I tried starting the server, but it appeared an error window "Visual
Studio just in time debugger" and it also printed the following errors in
the command prompt:
net start apache2
The Apache2 service is starting.
The Apache2 service could not be started.
A system error has occurred.
System error 1067 has occurred.
The process terminated unexpectedly.
In the error log it appeared the following errors:
...
[Wed Oct 03 20:19:38 2007] [notice] Child 3008: Starting 250 worker threads.
[Wed Oct 03 20:19:38 2007] [notice] Child 3008: Starting thread to listen on
port 80.
[Wed Oct 03 20:19:59 2007] [notice] Parent: Received shutdown signal --
Shutting down the server.
[Wed Oct 03 20:19:59 2007] [notice] Child 3008: Exit event signaled. Child
process is ending.
[Wed Oct 03 20:20:00 2007] [notice] Child 3008: Released the start mutex
[Wed Oct 03 20:20:01 2007] [notice] Child 3008: Waiting for 250 worker
threads to exit.
[Wed Oct 03 20:20:01 2007] [notice] Child 3008: All worker threads have
exited.
[Wed Oct 03 20:20:01 2007] [notice] Child 3008: Child process is exiting
In order to be sure, I've repeated and I tried starting again the server for
a few times.
2 times, the web server started with that Catalyst app, and I was able to
use it.
The rest of the times it shown those errors. I didn't change absolutely
anything between those trials, but I just tried stopping and restarting the
server.
However it is strange that sometimes it works and sometimes it doesn't.
Thank you.
Octavian
----- Original Message -----
From: "Randy Kobes" <[EMAIL PROTECTED]>
To: "William A. Rowe, Jr." <[EMAIL PROTECTED]>
Cc: "Foo JH" <[EMAIL PROTECTED]>; "Octavian Rasnita"
<[EMAIL PROTECTED]>; <modperl@perl.apache.org>
Sent: Wednesday, October 03, 2007 7:26 PM
Subject: Re: Best version of Apache for Win32 deployment
On Wed, 3 Oct 2007, William A. Rowe, Jr. wrote:
Foo JH wrote:
Octavian Rasnita wrote:
Regarding the best Apache for Windows, I have a problem running Apache
under
windows and I think this thread might help me.
I tried Apache 2.2.4 with and without SSL support, and Apache 2.2.6
from
apachelounge, but they still don't work.
I'm using 2.2.4 now on Win32, and it's running good for me. Much much
better than the 2.x.x series from the Apache site. Works on XP and W2k3.
A point to note though is that you should not use the modperl
compilation from AL. Use the standard-issue one from theoryx5. Install
libapreq2 from theoryx5 also.
EXACTLY.
Because you used theoryx5's perl/modperl/libapreq2 built for VC8, along
with
the AL build of 2.2.4 ALSO built for VC8, everything is dandy.
Equally if you used ActiveState perl (built VC6) + a VC6 build of modperl
and
libapreq2 with the ASF distribution of httpd 2.2.4, everything is dandy.
Mix and match at your own risk.
Actually, I use VC6 to build all the ppm packages in our
theoryx5 repository, including mod_perl and libapreq2, so
as to be compatible with ActivePerl (also built with VC6).
But your point of mixing and matching at your own risk
is well-taken - the fact that the VC6 mod_perl package
appears to work with the AL build of Apache built with
VC8 may just mean that the testing done hasn't yet
encountered the problems that could in principle be
there; see, for example,
http://search.cpan.org/src/SHAY/Win32-SharedFileOpen-3.36/INSTALL
for an instance that is known to illustrate the problem.
I haven't looked into this, but the fact that AL's
mod_perl (compiled, presumably, with VC8) doesn't
work with, again presumably, ActivePerl (compiled
with VC6) may be another example of the dangers
of mixing components compiled with VC6 and VC8.
--
best regards,
Randy
