...

Resources

• DSpace Documentation. Obviously this  - This would be the place to start for any installation or configuration problems
• Use the DSpace Community Resource Search engine to  - Allows you to simultaneously search the DSpace Wiki, Issue Tracker and mailing lists .(via Google)
  • Directly search
  Search
  • or browse all DSpace mailing lists via Nabble: http://dspace.2283337.n4.nabble.com
  /
  • Search Directly search or browse the DSpace Issue Tracker for known/fixed bugs: https://jira.duraspace.org/browse/DS
• StackOverflow ("dspace" tag) - We now encourage technical questions to be asked on StackOverflow, so you may wish to search/browse there to see if anyone has encountered this problem before.
• DSpace Technical FAQ - Describes some common issues that may be encountered

General Instructions

Finding the Error Message in your Log Files

...

Searching for Fixes to Common Errors

• 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).

  Search
  • Directly search or browse all DSpace mailing lists via Nabble: http://dspace.2283337.n4.nabble.com/
  • Directly search or browse the DSpace Issue Tracker for known/fixed bugs: https://jira.duraspace.org/browse/DS

• Finally, check the DSpace Technical FAQ for any possible information. Some commonly reported problems have answers there.

Turning on Debugging (optional)

• 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.rootCategory and log4j.logger.org.dspace settings to DEBUG rather than INFO.

  • (XMLUI Only) To enable DEBUG logging in the cocoon.log file, change the log4j.logger.org.apache.cocoon setting to DEBUG rather than INFO.

  • NOTE: You'll need to restart Tomcat after enabling DEBUG mode in the log4j.properties file.

  • 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!

Send the error message and describe how you encountered it

...

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@lists.sourceforge.net.

...

1. 1. If you are not a member of this list, you can signup at https://lists.sourceforge.net/lists/listinfo/dspace-tech

...

...

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

...

1. , 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

...

1. .

2. The error stack that you found in your log file