source: trunk/TROUBLESHOOTING @ 264

Last change on this file since 264 was 264, checked in by kake, 18 years ago

Junked OpenGuides::Config completely to avoid database password

leakage, and easier install (CPAN RT 3916).

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 2.1 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 see the following message in your webserver error logs:
26
27  "Unable to tie -map_name [...] datafiles directory [...] does not exist
28   and cannot be created."
29
30This means that the directory you specified in your configuration as
31"indexing_directory" does not exist and cannot be created by the user
32that your CGI is running as.  This might mean one of two things:
33
34 - you've specified an indexing_directory within your own webspace but
35   your CGIs are running not as you but as a dedicated webserver user
36   such as 'nobody' or 'www-data'
37
38or
39
40 - you've specified an indexing_directory in a place that you're not
41   allowed to write to
42
43or a combination of both.  Your ISP or sysadmin might be able to help you
44further with this problem if you can't figure it out yourself.
45
46----------------------------------------------------------------------
47
48Again relating to permissions - if you are using SQLite then note that
49the user your CGI is running as must have write access to not only the
50database file itself, but the directory that the file is in (in order
51that it can write a lockfile).
52
53----------------------------------------------------------------------
Note: See TracBrowser for help on using the repository browser.