Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
Topic: mod_perl updated |
|
Author |
|
Steffen Moderator
Joined: 15 Oct 2005 Posts: 3094 Location: Hilversum, NL, EU
|
Posted: Thu 07 Sep '06 23:10 Post subject: mod_perl updated |
|
|
I build the latest 2.0.3 RC1 of mod_perl against Apache 2.2.3 and Perl 5.8.8.819. Available at the download page here.
Steffen |
|
Back to top |
|
dami
Joined: 25 Sep 2006 Posts: 2 Location: geneva switzerland
|
Posted: Mon 25 Sep '06 9:55 Post subject: mod_perl dies silently |
|
|
Hi Steffen,
First, thanks a lot for your download site.
However I can't get mod_perl to work. I installed ActivePerl 5.8.8 build 819, then installed your Apache 2.2.3 and mod_perl 2.0.3 binaries. But when I add the line
LoadModule perl_module modules/mod_perl.so
to httpd.conf, the http.exe no longer starts (dies silently, no error message in the logs).
Any hint ? thanks in advance. |
|
Back to top |
|
dami
Joined: 25 Sep 2006 Posts: 2 Location: geneva switzerland
|
Posted: Wed 27 Sep '06 9:33 Post subject: mod_perl dies silently (fixed) |
|
|
Hi,
Forget my previous message --- the problem was in my perl.conf configuration (trying to load an absent module). Too bad that the whole thing collapses without any message, so that made it hard to debug .... |
|
Back to top |
|
Jorge
Joined: 12 Mar 2006 Posts: 376 Location: Belgium
|
Posted: Wed 27 Sep '06 10:53 Post subject: Re: mod_perl dies silently (fixed) |
|
|
dami wrote: | Hi,
Forget my previous message --- the problem was in my perl.conf configuration (trying to load an absent module). Too bad that the whole thing collapses without any message, so that made it hard to debug .... |
that might be because it died before logs where opened try running it with the -d command to debug |
|
Back to top |
|
|
|
|
|
|