| 1 | OpenGuides Troubleshooting Guide |
|---|
| 2 | ================================ |
|---|
| 3 | |
|---|
| 4 | If you wish to install the OpenGuides modules in a private directory, |
|---|
| 5 | you will need to specify this when you run the Build.PL. |
|---|
| 6 | |
|---|
| 7 | If 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 | |
|---|
| 15 | Or for earlier versions of Module::Build, do: |
|---|
| 16 | |
|---|
| 17 | perl Build.PL config='sitelib=/path/to/my/modules/' |
|---|
| 18 | |
|---|
| 19 | ---------------------------------------------------------------------- |
|---|
| 20 | |
|---|
| 21 | If any or all of the modules required by the OpenGuides scripts are in |
|---|
| 22 | a private directory, then you'll need to tell the scripts where to find |
|---|
| 23 | them. From version 0.41 of OpenGuides, you can do this at 'perl Build.PL' |
|---|
| 24 | time - see the INSTALL file included in this distribution. |
|---|
| 25 | |
|---|
| 26 | ---------------------------------------------------------------------- |
|---|
| 27 | |
|---|
| 28 | If you are able to run wiki.cgi from the command line but receive an |
|---|
| 29 | Error 500 when trying to view it in your browser, look for the following |
|---|
| 30 | message in your webserver error logs: |
|---|
| 31 | |
|---|
| 32 | "Unable to tie -map_name [...] datafiles directory [...] does not exist |
|---|
| 33 | and cannot be created." |
|---|
| 34 | |
|---|
| 35 | This means that the directory you specified in your configuration as |
|---|
| 36 | "indexing_directory" is inaccessible by the user that your CGI is running |
|---|
| 37 | as. This might mean one of two things: |
|---|
| 38 | |
|---|
| 39 | - you've specified an indexing_directory within your own webspace |
|---|
| 40 | and the user your CGIs are running as - typically 'nobody' or |
|---|
| 41 | 'www-data' - doesn't have permission to write there |
|---|
| 42 | |
|---|
| 43 | or |
|---|
| 44 | |
|---|
| 45 | - you've specified an indexing_directory in a place that you're not |
|---|
| 46 | allowed to write to |
|---|
| 47 | |
|---|
| 48 | or a combination of both. Your ISP or sysadmin might be able to help you |
|---|
| 49 | further with this problem if you can't figure it out yourself; as a start, |
|---|
| 50 | try setting your indexes directory as world-writeable. |
|---|
| 51 | |
|---|
| 52 | ---------------------------------------------------------------------- |
|---|
| 53 | |
|---|
| 54 | Important note for those using SQLite: |
|---|
| 55 | |
|---|
| 56 | The user your CGI is running as must have write access to not only the |
|---|
| 57 | database file itself, but the directory that the file is in, in order |
|---|
| 58 | that it can write a lockfile. If it doesn't have write access to the |
|---|
| 59 | database file, you'll see errors like "Unhandled error: [DBD::SQLite::db |
|---|
| 60 | do failed...". |
|---|
| 61 | |
|---|
| 62 | ---------------------------------------------------------------------- |
|---|
