| 1 | OpenGuides Troubleshooting Guide |
|---|
| 2 | ================================ |
|---|
| 3 | |
|---|
| 4 | If you are able to run wiki.cgi from the command line but receive an |
|---|
| 5 | Error 500 when trying to view it in your browser, look for the following |
|---|
| 6 | message in your webserver error logs: |
|---|
| 7 | |
|---|
| 8 | "Unable to tie -map_name [...] datafiles directory [...] does not exist |
|---|
| 9 | and cannot be created." |
|---|
| 10 | |
|---|
| 11 | This means that the directory you specified in your configuration as |
|---|
| 12 | "indexing_directory" is inaccessible by the user that your CGI is running |
|---|
| 13 | as. 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 | |
|---|
| 19 | or |
|---|
| 20 | |
|---|
| 21 | - you've specified an indexing_directory in a place that you're not |
|---|
| 22 | allowed to write to |
|---|
| 23 | |
|---|
| 24 | or a combination of both. Your ISP or sysadmin might be able to help you |
|---|
| 25 | further with this problem if you can't figure it out yourself; as a start, |
|---|
| 26 | try setting your indexes directory as world-writeable. |
|---|
| 27 | |
|---|
| 28 | ---------------------------------------------------------------------- |
|---|
| 29 | |
|---|
| 30 | Important note for those using SQLite: |
|---|
| 31 | |
|---|
| 32 | The user your CGI is running as must have write access to not only the |
|---|
| 33 | database file itself, but the directory that the file is in, in order |
|---|
| 34 | that it can write a lockfile. If it doesn't have write access to the |
|---|
| 35 | database file, you'll see errors like "Unhandled error: [DBD::SQLite::db |
|---|
| 36 | do failed...". |
|---|
| 37 | |
|---|
| 38 | ---------------------------------------------------------------------- |
|---|
