www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Rose <richard.r...@lucasvarity.com>
Subject os-windows/3293: Perl 5.005_02 will not run under Apache 1.3.3 win 95
Date Mon, 26 Oct 1998 16:29:30 GMT

>Number:         3293
>Category:       os-windows
>Synopsis:       Perl 5.005_02 will not run under Apache 1.3.3 win 95
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Oct 26 08:30:00 PST 1998
>Originator:     richard.rose@lucasvarity.com
>Release:        1.3.3  (win 32)
Windows 95 OSR2
ActivePerl, Build 502  (version 5.005_02 built for MSWin32-x86-object )
*I have a problem getting Perl to work on 
* Apache /1.3.3 (win 32) on a windows 95 OSR2 PC
* Reading throught the various problem reports
* it appears that the problem has appeared and been
* solved in various other versions, but I am unable to
* make the solutions work.

* This is the configuration I have

*Apache initially instaled in default directory, following prompts
* "It worked!" screen appears OK.

*Active State Perl installed in default directories.
*Confirmation of Perl installation by typing perl-v 
* at the c: prompt, returns the following:

This is perl, version 5.005_02 built for MSWin32-x86-object
Copyright 1987-1998, Larry Wall
Binary build 502 provided by ActiveState Tool Corp. 
Built 10:59:41 Aug 11 1998

* Perl executable in the following directory:

*Testing by other command line perl programs, seems to run OK.

*Followed instructions as per PR 3104. Checked all the directory names appear
*in quotes as per other PRs
*New directories created:


* (contents & subsequent sub-directories in htdocs
   copied from original location)
* Original directories re-named to ensure server cannot pick up
* on those directories by accident (i.e. if I've not changed a conf
* line I should have, the original directory no longer exists)

*The following lines in the srm.conf file changed:

DocumentRoot "C:/www/htdocs"

ScriptAlias /cgi-bin/ "C:/www/cgi-bin/"

# To use CGI scripts:
AddHandler cgi-script .pl

*The following lines in access.conf changed:

<Directory "C:/www/htdocs">

<Directory "C:/www/cgi-bin">
AllowOverride None
Options ExecCGI

*The following line in httpd.conf changed:


*The following perl script created and stored
*as c:\www\cgi-bin\hello.pl:

print "Content-type: text/plain\n\nHello World!\n"; 

*Running from the command line prints Hello World! as expected
*The PC Apache runs on has an IP address, so the "IT WORKED"
*page is accessed as:
*This works OK,therefore the perl script was accessed as:

*This returned the following text in the browser:

Internal Server Error
The server encountered an internal error or misconfiguration
and was unable to complete your request.
Please contact the server administrator,
you@your.address and inform them of the time the error occurred,
and anything you might have done that may have caused the error.

couldn't spawn child process: c:/www/cgi-bin/hello.pl

*And the following entry in the error log:
*(I have split the line up)

[Mon Oct 26 14:24:56 1998] [error] 
[client] (2)No such file or directory: 
couldn't spawn child process: c:/www/cgi-bin/hello.pl

*Any suggestions? I have gone through the FAQ, and the bug reports, but I do
*not have newsgroup access, so Iapologise if the answer is out there
*and I can't access it. If this is something so blindingly obvious that I can't see
* for looking at trhe detail, then I also apologise.

*RIchard Rose
This server is running on a standaone laptop, so there is no access to it from outside. (It's
only purpose is to test out CGI scripts prior to loading on the real server)
I have tried including or omiting the trailing slash from directory names, as the
documentation seems to sometimes include them and sometimes not. It 
does not appear to make a difference.
I could try building an earlier version of Perl, but I'd prefer to use the same one 
as the main server.
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]

View raw message