I am getting the same exact problem on RedHat7.0.
I was wondering if there is a solution to this access permission
problem?
The strace.out looks like this:
accept(16,
Just one line.
Any pointers is appreciated.
-Joan
try this (in the mod_perl-x.xx directory):
% make start_httpd
% strace -o strace.out -p `cat t/logs/httpd.pid` &
% make run_tests
% grep open stace.out | grep .htaccess > send_to_modperl_list
% make kill_httpd
and send us that file. I have the feeling there's a .htaccess in your
tree that the process can't read.
-Doug
On Thu, 9 Sep 1999, Earl Evans wrote:
>
> Greetings,
>
> I'm trying to install mod_perl, and getting stuck at the "make test"
> phase.
>
> (Note to readers: I've been thru the FAQs, archives, and web resources
> before asking here.)
>
> My info:
>
> RedHat Linux 6.0
> Kernel 2.2.5-15
> Apache 1.3.9
> mod_perl 1.21
> Perl 5.005_03
> All prerequisite Perl modules reqd by mod_perl installed
> httpd.conf in t/conf directory left unchanged
>
> My steps:
>
> # perl Makefile.PL {parameters}
>
> (with various sets of parameters as suggested on FAQ,
> etc.)
>
> # make
> # make test
>
> My problem:
>
> "perl Makefile.PL" and "make" work fine. However, "make test" fails
with
> an error:
>
> httpd listening on port 8529
> will write error_log to: t/logs/error_log
> letting apache warm up...\c
> done
> /usr/bin/perl t/TEST 0
> still waiting for server to warm upnot ok
> server failed to start! at t/TEST line 95.
> make: *** [run_tests] Error 9
>
> ...although the httpd process does start. I can tell by grepping a ps
ax
> that the httpd process is running. And it answers to telnet, as shown
> below.
>
> Telneting to the process on the designated port:
>
> telnet localhost 8529
>
> then typing:
>
> GET /test.html (a file that does exist in the DocumentRoot)
>
> results in:
>
>
>
> 403 Forbidden
>
> Forbidden
> You don't have permission to access /test.html
> on this server.
>
> Connection closed by foreign host.
>
> ...so it appears there is a permissions problem. File and directory
> permissions appear OK for t/docs, and there are no directives in the
> distributed httpd.conf that block access. I did see a .htaccess file
in
> the docroot, but it's blank. (Also, it seems access wouldn't be
denied by
> default anyhow...this is a test server docroot...)
>
> Any ideas would be much appreciated. And the virtual beverage of your
> choice is on me :-)
>
> Best Regards,
>
> Earl
> [EMAIL PROTECTED]
>
>
>
