Page History

Error Log Files:

• DSpace log file: dspace Code Block<dspace>/log/dspace.log (usually)
• Tomcat log directory: Tomcat Code Block<tomcat>/logs (usually)
• (XMLUI Only) Cocoon log file:
  • 1.5.1 or previous: tomcat Code Block<tomcat>/webapps/ webapp Code Block<name-of-webapp>/WEB-INF/logs/
  • 1.5.2 or later: dspace Code Block <dspace>/log/cocoon.log

Resources:

• DSpace technical FAQ: Code Blockhttp: //wiki.dspace.org/TechnicalFaq
• Search dspace-tech mailing list: Code Block http://sourceforge.net/mailarchive/forum.php?forum=dspace-tech^{Image Added}

General Instructions:

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 Code Block''[dspace]''<dspace>/log/dspace.log or Code Block''[Tomcat]'' 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", you will have to check the log files for a full error listing. If your email address is set up in dspace.cfg as the DSpace Administrator, you should receive an email with this full error listing. If not, move into the DSpace log directory and Code Blocktail view the end of the log file (e.g. tail -100 dspace.log).
   • (Windows) Go to the DSpace log directory, and open dspace.log in your favorite text editor. Look near the bottom for the error message.
3. Usually, the culprit file is in the first five to ten lines of the error stack listing. The error stack starts with a line similar to: Code Block{{yyyy-mm-dd time WARN ... }}(OR) Code Block{{yyyy-mm-dd time ERROR ... }}
4. Search the DSpace technical FAQ and the dspace-tech mailing list for information on the error. Key words in the error often are useful search terms.
5. If you'd like to try and do some debugging yourself, you can change the DSpace logger settings to Code BlockDEBUG which will sometimes provide you with more information about the error. To turn on debugging, visit the dspace Code Block<dspace>/config/log4j.properties file and do the following:
   • To enable DEBUG logging in the Code Blockdspace.log file, change the Code Blocklog4j.rootCategory and Code Blocklog4j.logger.org.dspace settings to Code BlockDEBUG rather than Code BlockINFO.
   • (XMLUI Only) To enable DEBUG logging in the Code Blockcocoon.log file, change the Code Blocklog4j.logger.org.apache.cocoon setting to Code BlockDEBUG rather than Code BlockINFO.
   *
   • 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!
6. If all else fails, email a description of the error along with the error stack listing to dspace-tech@lists.sourceforge.net^{Image Removed}. Try to include the following in your email:
   • Your environment: Operating system, version of DSpace, version of Tomcat, Java, etc.
   • The exact steps you took to encounter the error
   • The error stack that you found in your log file