source: trunk/TROUBLESHOOTING @ 346

Last change on this file since 346 was 346, checked in by Earle Martin, 18 years ago

tidied a little

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 2.5 KB
Line 
1OpenGuides Troubleshooting Guide
2================================
3
4If you wish to install the OpenGuides modules in a private directory,
5you will need to specify this when you run the Build.PL.
6
7If you are using version 0.20 of Module::Build, do:
8
9  perl Build.PL install_path=lib=/path/to/my/modules/ \
10                install_path=script=/path/to/my/bin/ \
11                install_path=arch=/path/to/my/modules/auto/ \
12                install_path=libdoc=/path/to/my/man/ \
13                install_path=bindoc=/path/to/my/man/
14
15Or for earlier versions of Module::Build, do:
16
17  perl Build.PL config='sitelib=/path/to/my/modules/'
18
19----------------------------------------------------------------------
20
21If any or all of the modules required by the OpenGuides scripts are in
22a private directory, then you'll need to tell the scripts where to find
23them. At present the only way to do this is to install everything and
24then manually edit wiki.cgi (or whatever you called it),
25supersearch.cgi and preferences.cgi to include a line like
26
27  use lib qw( /path/to/my/modules/ );
28
29at the top before any other modules are required.
30
31----------------------------------------------------------------------
32
33If you are able to run wiki.cgi from the command line but receive an
34Error 500 when trying to view it in your browser, look for the following
35message in your webserver error logs:
36
37  "Unable to tie -map_name [...] datafiles directory [...] does not exist
38   and cannot be created."
39
40This means that the directory you specified in your configuration as
41"indexing_directory" is inaccessible by the user that your CGI is running
42as.  This might mean one of two things:
43
44 - you've specified an indexing_directory within your own webspace
45   and the user your CGIs are running as - typically 'nobody' or
46   'www-data' - doesn't have permission to write there
47
48or
49
50 - you've specified an indexing_directory in a place that you're not
51   allowed to write to
52
53or a combination of both.  Your ISP or sysadmin might be able to help you
54further with this problem if you can't figure it out yourself; as a start,
55try setting your indexes directory as world-writeable.
56
57----------------------------------------------------------------------
58
59Important note for those using SQLite:
60
61The user your CGI is running as must have write access to not only the
62database file itself, but the directory that the file is in, in order
63that it can write a lockfile. If it doesn't have write access to the
64database file, you'll see errors like "Unhandled error: [DBD::SQLite::db
65do failed...".
66
67----------------------------------------------------------------------
Note: See TracBrowser for help on using the repository browser.