source: trunk/TROUBLESHOOTING @ 271

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

Extended and clarified the section of TROUBLESHOOTING about permissions problems s
ome more.

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