510689 - add advice on bugzilla configuration

Status: RESOLVED WONTFIX

(Bugzilla :: Documentation, enhancement)

Description

[Peter]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.12) Gecko/2009071200 SUSE/3.0.12-0.1.2 Firefox/3.0.12
Build Identifier: 3.0

bugzilla CGI scripts should have the same perl pathname in their shebang line as was used for successful completion of checksetup.pl - otherwise you may use a perl installation without the modules you checked for.

Reproducible: Sometimes

Steps to Reproduce:
1. install and configure following the docs on a host with 2 perls installed
2. if unlucky you find this problem
Actual Results:  
checksetup.pl reports all perl modules present - bugzilla as run from the web server does not

Expected Results:  
bugzilla page displayed

proposed extension to docs


*** 3.0/xml/troubleshooting.xml 2009-08-15 18:50:03.000000000 +0100
--- 3.0/xml/troubleshooting.xml-new     2009-08-15 18:57:29.000000000 +0100
***************
*** 282,287 ****
--- 282,301 ----

    </section>

+   <section id="trbl-perlmodule-web">
+     <title>
+       checksetup.pl reports all compulsory Perl modules are present but
+       bugzilla as run in the webserver fails to load them.
+     </title>
+     <para>
+       If you have multiple versions of Perl installed ensure that the first
+       line (the "shebang" line with "#!" and the pathname to perl) of
+       all of the bugzilla CGI scripts uses the same pathname as the
+       perl binary with which you had successful completion of checksetup.pl.
+     </para>
+   </section>
+
+
  </appendix>

  <!-- Keep this comment at the end of the file

Comment 1

[Peter]

It would be even better if checksetup.pl actually put the right pathname on the shebang line removing this possible error via automation.

Comment 2

[Max Kanat-Alexander]

I think this would actually be better in the FAQ at:

  http://wiki.mozilla.org/Bugzilla:FAQ

And then we should point people at the FAQ for troubleshooting.