From 164b989ee0e92922fa031e870836a30d1a7cc39c Mon Sep 17 00:00:00 2001 From: "mozilla%colinogilvie.co.uk" <> Date: Fri, 4 Apr 2008 11:47:38 +0000 Subject: Bug 232378: switch from entities to XIncludes for inclusion of modular docs files Patch by Colin Ogilvie ; r=vladd --- docs/en/xml/troubleshooting.xml | 89 +++++++++++++++++++++++++++++++++++------ 1 file changed, 77 insertions(+), 12 deletions(-) (limited to 'docs/en/xml/troubleshooting.xml') diff --git a/docs/en/xml/troubleshooting.xml b/docs/en/xml/troubleshooting.xml index 13a756a3b..10ad59f1c 100644 --- a/docs/en/xml/troubleshooting.xml +++ b/docs/en/xml/troubleshooting.xml @@ -1,5 +1,9 @@ - - + + + %myents; +]> Troubleshooting @@ -15,14 +19,14 @@ completion, it normally explains what's wrong and how to fix it. If you can't work it out, or if it's being uncommunicative, post the errors in the - mozilla.support.bugzilla + netscape.public.mozilla.webtools newsgroup. If you have made it all the way through (Installation) and (Configuration) but accessing the Bugzilla - URL doesn't work, the first thing to do is to check your web server error + URL doesn't work, the first thing to do is to check your webserver error log. For Apache, this is often located at /etc/logs/httpd/error_log. The error messages you see may be self-explanatory enough to enable you to diagnose and @@ -32,7 +36,7 @@ Bugzilla can also log all user-based errors (and many code-based errors) - that occur, without polluting the web server's error log. To enable + that occur, without polluting the web server error log. To enable Bugzilla error logging, create a file that Bugzilla can write to, named errorlog, in the Bugzilla data directory. Errors will be logged as they occur, and will include the type @@ -45,10 +49,10 @@
- The Apache web server is not serving Bugzilla pages + The Apache webserver is not serving Bugzilla pages After you have run checksetup.pl twice, run testserver.pl http://yoursite.yourdomain/yoururl - to confirm that your web server is configured properly for + to confirm that your webserver is configured properly for Bugzilla. @@ -75,13 +79,31 @@ TEST-OK Webserver is preventing fetch of http://landfill.bugzilla.org/bugzilla-t - The permissions on your library directories are set incorrectly. - They must, at the very least, be readable by the web server user or - group. It is recommended that they be world readable. + The permissions on your library directories are set incorrectly. + They must, at the very least, be readable by the webserver user or + group. It is recommended that they be world readable.
+ +
+ Bundle::Bugzilla makes me upgrade to Perl 5.6.1 + + Try executing perl -MCPAN -e 'install CPAN' + and then continuing. + + + Certain older versions of the CPAN toolset were somewhat naive about + how to upgrade Perl modules. When a couple of modules got rolled into the + core Perl distribution for 5.6.1, CPAN thought that the best way to get + those modules up to date was to haul down the Perl distribution itself and + build it. Needless to say, this has caused headaches for just about + everybody. Upgrading to a newer version of CPAN with the + commandline above should fix things. + +
+
DBD::Sponge::db prepare failed @@ -139,12 +161,55 @@ TEST-OK Webserver is preventing fetch of http://landfill.bugzilla.org/bugzilla-t
+
+ Your vendor has not defined Fcntl macro O_NOINHERIT + + This is caused by a bug in the version of + File::Temp that is distributed with perl + 5.6.0. Many minor variations of this error have been reported: + + + Your vendor has not defined Fcntl macro O_NOINHERIT, used +at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 208. + +Your vendor has not defined Fcntl macro O_EXLOCK, used +at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 210. + +Your vendor has not defined Fcntl macro O_TEMPORARY, used +at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233. + + Numerous people have reported that upgrading to version 5.6.1 + or higher solved the problem for them. A less involved fix is to apply + the following patch, which is also + available as a patch file. + + + +
+
Everybody is constantly being forced to relogin The most-likely cause is that the cookiepath parameter is not set correctly in the Bugzilla configuration. You can change this (if - you're a Bugzilla administrator) from the editparams.cgi page via the web interface. + you're a Bugzilla administrator) from the editparams.cgi page via the web. The value of the cookiepath parameter should be the actual directory @@ -213,7 +278,7 @@ TEST-OK Webserver is preventing fetch of http://landfill.bugzilla.org/bugzilla-t
-
+
Some users are constantly being forced to relogin First, make sure cookies are enabled in the user's browser. -- cgit v1.2.3-24-g4f1b