source: trunk/TROUBLESHOOTING @ 1129

Last change on this file since 1129 was 1129, checked in by Earle Martin, 14 years ago

The section about installing into a private directory really belongs in INSTALL, not TROUBLESHOOTING.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 1.5 KB
Line 
1OpenGuides Troubleshooting Guide
2================================
3
4If you are able to run wiki.cgi from the command line but receive an
5Error 500 when trying to view it in your browser, look for the following
6message in your webserver error logs:
7
8  "Unable to tie -map_name [...] datafiles directory [...] does not exist
9   and cannot be created."
10
11This means that the directory you specified in your configuration as
12"indexing_directory" is inaccessible by the user that your CGI is running
13as.  This might mean one of two things:
14
15 - you've specified an indexing_directory within your own webspace
16   and the user your CGIs are running as - typically 'nobody' or
17   'www-data' - doesn't have permission to write there
18
19or
20
21 - you've specified an indexing_directory in a place that you're not
22   allowed to write to
23
24or a combination of both.  Your ISP or sysadmin might be able to help you
25further with this problem if you can't figure it out yourself; as a start,
26try setting your indexes directory as world-writeable.
27
28----------------------------------------------------------------------
29
30Important note for those using SQLite:
31
32The user your CGI is running as must have write access to not only the
33database file itself, but the directory that the file is in, in order
34that it can write a lockfile. If it doesn't have write access to the
35database file, you'll see errors like "Unhandled error: [DBD::SQLite::db
36do failed...".
37
38----------------------------------------------------------------------
Note: See TracBrowser for help on using the repository browser.