Table of Contents:
[dspace]is the location where DSpace is installed.
[tomcat]is the location where Tomcat is installed.
[tomcat]/logs/. For the XMLUI, you may also want to check the Cocoon logs (see above for path) to see if any extra information can be found there.
alert.recipient) as the DSpace Administrator, you should receive an email with this full error listing. If not, move into the DSpace log directory (
[dspace]/log) and view the end of the log file:
tail -100 dspace.logAlternatively, you can open up the dspace.log file in your favorite text editor and look near the bottom of the file for the error message.
yyyy-mm-dd time ERROR ...OR,
yyyy-mm-dd time WARN ...
Use the DSpace Community Resource Search engine to simultaneously search the DSpace Wiki, Issue Tracker and mailing lists (via Google).Search StackOverflow (especially the "dspace" tag) to see if this issue has been reported and solved there (as we now encourage technical questions to be asked on StackOverflow).
Finally, check the DSpace Technical FAQ for any possible information. Some commonly reported problems have answers there.
If you'd like to try and do some debugging yourself, you can change the DSpace logger settings to
DEBUG which will sometimes provide you with more information about the error. To turn on debugging, visit the
[dspace]/config/log4j.properties file and do the following:
To enable DEBUG logging in the
dspace.log file, change the
log4j.logger.org.dspace settings to
DEBUG rather than
(XMLUI Only) To enable DEBUG logging in the
cocoon.log file, change the
log4j.logger.org.apache.cocoon setting to
DEBUG rather than
NOTE: You'll need to restart Tomcat after enabling DEBUG mode in the
WARNING: Make sure to turn off debugging once you are finished. Leaving debugging turned on will cause the log files to grow very large very quickly!
Depending on where you got your Java runtime environment, you may have the
jps -v can show you the options actually used to run your Servlet container, which can be useful in debugging startup issues. A plain
jps command will list process IDs of running JREs, which you can use with your favorite process monitoring tools.
jps can only show processes which your user account is allowed to inspect, so you should run it as the user which runs the container, or as a superuser.
There are two ways you may choose to report this error. However, we ask that you only choose one, depending on which you prefer.
Post a question on StackOverflow and tag it with "dspace". See Guide to Posting Technical Questions to StackOverflow for more information.
OR, email a description of the error along with the error stack listing to email@example.com
If you are not a member of this list, or want more information about DSpace lists, see Mailing Lists
Other support options detailed on the DSpace Support page
MAKE SURE to include the following information:
./dspace version" from the commandline will provide much of this information for you.
The error stack that you found in your log file