Changeset 271 for trunk/TROUBLESHOOTING

Timestamp:

11/06/03 17:05:46 (5 years ago)

Author:

earle

Message:

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

Files:

• trunk/TROUBLESHOOTING (modified) (4 diffs)

trunk/TROUBLESHOOTING

@@ -23 +23 @@
 ----------------------------------------------------------------------
 
-If you see the following message in your webserver error logs:
+If you are able to run wiki.cgi from the command line but receive an 
+Error 500 when trying to view it in your browser, look for the following
+message in your webserver error logs:
 
   "Unable to tie -map_name [...] datafiles directory [...] does not exist
@@ -29 +31 @@
 
 This means that the directory you specified in your configuration as
-"indexing_directory" does not exist and cannot be created by the user
-that your CGI is running as.  This might mean one of two things:
+"indexing_directory" is inaccessible by the user that your CGI is running 
+as.  This might mean one of two things:
 
- - you've specified an indexing_directory within your own webspace but
-   your CGIs are running not as you but as a dedicated webserver user
-   such as 'nobody' or 'www-data'
+ - you've specified an indexing_directory within your own webspace
+   and the user your CGIs are running as - typically 'nobody' or 
+   'www-data' - doesn't have permission to write there
 
 or
@@ -42 +44 @@
 
 or a combination of both.  Your ISP or sysadmin might be able to help you
-further with this problem if you can't figure it out yourself.
+further with this problem if you can't figure it out yourself; as a start,
+try setting your indexes directory as world-writeable.
 
 ----------------------------------------------------------------------
@@ -50 +53 @@
 The user your CGI is running as must have write access to not only the
 database file itself, but the directory that the file is in, in order
-that it can write a lockfile.
-
-A symptom of having incorrect permissions set is being able to run 
-wiki.cgi from the command line but receiving an Error 500 when trying to 
-view it in your browser. 
+that it can write a lockfile. If it doesn't have write access to the
+database file, you'll see errors like "Unhandled error: [DBD::SQLite::db 
+do failed...".
 
 ----------------------------------------------------------------------