2. Troubleshooting
Symptom |
Solution |
Apache refuses to start, complaining that it can't find some of the perl modules, but I installed all of them.
A typical error message is: Can't find packagename in @INC (@INC includes path1,path2,...) |
This usually means one of two things. Either the package named wasn't actually installed, or the @INC used by mod_perl is different than the @INC used by CPAN when you installed the modules (common if you upgraded Perl after compiling mod_perl, or if you installed the modules, upgraded perl, then compiled mod_perl).
Search for the file named in the error message. If it doesn't exist, you will need to install it (see section 2.1.2) then try again. If the file does exist, check its location against the paths listed in the error message; chances are the version information in the paths is different.
If this is the case, you can either recompile mod_perl (2.2) to use the new perl version, or you can add the relevant paths to @INC. To add the paths to @INC, put the following two lines in your startup.pl file, immediately after the line that says ``use strict;''.
BEGIN { push(@INC, '/usr/lib/perl5/site_perl/5.x.y/i586-linux'); }
BEGIN { push(@INC, '/usr/lib/perl5/site_perl/5.x.y'); }
Change the version from 5.x.y to whichever version your modules were installed with (obviously, the version that is not in the @INC in the error message). Those two lines should be sufficient. |
Apache refuses to start, complaining that the <perl> directives are not recognized |
mod_perl is not installed or active; see section 2.2. |
Apache starts, but I see a directory index (may or may not be Scoop's) instead of the front page, or I get a ``Directory index forbidden by rule'' error in my browser |
This usually means your virtualhost setup or your location setup isn't correct, especially if the directory index isn't of Scoop's html/ directory. It may also mean that a higher-level directory has too-restrictive of permissions (such as the Directory / having a ``Deny from All'' command, which would be characterized by client denied by server configuration in the error logs). |
Apache starts, but I see Scoop's html/ directory index instead of the front page, or I get a ``Directory index forbidden by rule'' error in my browser |
This usually means that Apache is indeed looking in the right place, but the mod_perl instructions are not running. See section 2.5.2. |
I can log in, but I'm logged out again on the very next page |
This is a cookie problem. Generally, your server is not configured to send cookies properly; look in the Apache configuration file Scoop generated for you, and make sure the variable cookie_host is set to the URL you use to access the site as described in section 2.5.2.
If your cookie host is set properly, make sure your browser is not rejecting cookies from your domain. You may want to delete the cookie if it already exists, and tell your browser to notify you of attempts to set a cookie, to see if you're being sent one at all. |
I can log in, but when I try to click on any of the Admin Tools, I get a "Permission Denied" error |
See above; you're most likely being logged out, and if you're not logged in you don't have permission to do administrative tasks. |
My site starts up fine, but when I (or anybody else) tries to create an account, no email is sent |
make sure your smtp and email variables in the apache config file (2.5.2) and the Site Controls (3.1) are set properly. Make sure the SMTP server you are using allows your Scoop server to send email through it. Make sure your SMTP server is allowed to send email to the receiving server, too, before messing with its configuration--if it's in a spam blocklist the receiving server is using, no email will get through, through no configuration on your part. |
|