Table of Contents:

Error Log Files

Resources

General Instructions

Finding the Error Message in your Log Files

  1. If the expected information simply never appears, leaving a blank browser screen, the problem is likely with either a servlet (for JSPUI) or an XSLT Theme (for XMLUI). The error message should be in either [dspace]/log/dspace.log OR [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.
  2. If you get an "Internal Server Error" message, you will have to check the log files for a full error listing. If your email address is set up in dspace.cfg (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:
  3. Usually, the culprit error is in the first five to ten lines of the error stack listing. The error stack starts with a line similar to one of the following:

Searching for Fixes to Common Errors

Turning on Debugging (optional)

Report the Error and Describe How You Encountered It

There are two ways you may choose to report this error. However, we ask that you only choose one, depending on which you prefer.

  1. Post a question on StackOverflow and tag it with "dspace".  See  Guide to Posting Technical Questions to StackOverflow for more information.

  2. OR, email a description of the error along with the error stack listing to dspace-tech@googlegroups.com

    1. If you are not a member of this list, or want more information about DSpace lists, see Mailing Lists

  3. Other support options detailed on the DSpace Support page

MAKE SURE to include the following information:

  1. Your environment: Operating system, version of DSpace, version of Tomcat, Java, etc.
    1. NOTE: on DSpace 4.x or above, simply running "./dspace version" from the commandline will provide much of this information for you.
  2. The exact steps you took to encounter the error, as this will help us in investigating the problem. Often, we need to understand how to replicate the error before we can determine what the underlying cause is.
  3. The error stack that you found in your log file