Changeset 271 for trunk/TROUBLESHOOTING


Ignore:
Timestamp:
Nov 6, 2003, 5:05:46 PM (18 years ago)
Author:
Earle Martin
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/TROUBLESHOOTING

    r270 r271  
    2323----------------------------------------------------------------------
    2424
    25 If you see the following message in your webserver error logs:
     25If you are able to run wiki.cgi from the command line but receive an
     26Error 500 when trying to view it in your browser, look for the following
     27message in your webserver error logs:
    2628
    2729  "Unable to tie -map_name [...] datafiles directory [...] does not exist
     
    2931
    3032This means that the directory you specified in your configuration as
    31 "indexing_directory" does not exist and cannot be created by the user
    32 that your CGI is running as.  This might mean one of two things:
     33"indexing_directory" is inaccessible by the user that your CGI is running
     34as.  This might mean one of two things:
    3335
    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'
     36 - you've specified an indexing_directory within your own webspace
     37   and the user your CGIs are running as - typically 'nobody' or
     38   'www-data' - doesn't have permission to write there
    3739
    3840or
     
    4244
    4345or a combination of both.  Your ISP or sysadmin might be able to help you
    44 further with this problem if you can't figure it out yourself.
     46further with this problem if you can't figure it out yourself; as a start,
     47try setting your indexes directory as world-writeable.
    4548
    4649----------------------------------------------------------------------
     
    5053The user your CGI is running as must have write access to not only the
    5154database file itself, but the directory that the file is in, in order
    52 that it can write a lockfile.
    53 
    54 A symptom of having incorrect permissions set is being able to run
    55 wiki.cgi from the command line but receiving an Error 500 when trying to
    56 view it in your browser.
     55that it can write a lockfile. If it doesn't have write access to the
     56database file, you'll see errors like "Unhandled error: [DBD::SQLite::db
     57do failed...".
    5758
    5859----------------------------------------------------------------------
Note: See TracChangeset for help on using the changeset viewer.