Aaron

More Bugzilla on Windows

When I finally got bugzilla passing checksetup, I go to http://localhost/bugzilla and get plain text. Obviously not executing CGI.

Add the following to httpd.conf:

<Directory C:/Apache/httpd/2.2/htdocs/bugzilla>
AddHandler cgi-script .cgi
Options ExecCGI
AllowOverride Limit
DirectoryIndex index.cgi
</Directory>

–

Then I get a 500

Internal Server Error

with the following in the Apache log file:

[error] [client 127.0.0.1] (OS 3)The system cannot find the path specified. : couldn’t spawn child process: C:/Apache/httpd/2.2/htdocs/bugzilla/index.cgi

A quick search turns up this:

http://www.nabble.com/Internal-Server-Error-td14693066.html

You can either set perl to be the .cgi handler in the registry and set the directive

ScriptInterpreterSource register

Alternately, install perl where it is expected by index.cgi

: #!/usr/bin/perl -wT

or edit the script to expect perl in the proper location

C:/Perl/bin/perl.exe

or just #!perl

I think last time (on my laptop) I copied C:/Perl/bin/perl.exe to C:/usr/bin/perl.exe

Posted in Uncategorized5 Comments

5 thoughts on “More Bugzilla on Windows”

  1. copying perl.exe to c:/usr/bin/perl.exe works, but it’s inelegant.

    I’m trying to find a way to get mod_perl to work, but I run into an error with Apache::SizeLimit that aparently only works on MPM pre-fork?

    So apparently, mod_perl only works with bugzilla on Linux, because there the Windows binary is threaded, I’m guessing

    C:\USR\bin>\Aaron\Apache\httpd\2.2\bin\httpd.exe -t
    Syntax error on line 271 of C:/Aaron/Apache/httpd/2.2/conf/httpd.conf:
    Apache2::SizeLimit at the moment works only with non-threaded MPMs at C:/Aaron/Perl/site/lib/Apache2
    /SizeLimit.pm line 51.\nBEGIN failed–compilation aborted at C:/Aaron/Perl/site/lib/Apache2/SizeLimi
    t.pm line 98.\nCompilation failed in require at C:/Aaron/Apache/httpd/2.2/htdocs/bugzilla/mod_perl.p
    l line 32.\nBEGIN failed–compilation aborted at C:/Aaron/Apache/httpd/2.2/htdocs/bugzilla/mod_perl.
    pl line 32.\nCompilation failed in require at (eval 4) line 1.\n

    Reply

    1. Patrick-

      That sounds cool. I’ve only worried about Bugzilla on Windows for development or small deployment, so it hasn’t been a serious issue for me, but it’d be interesting to see.

      Reply

Leave a comment