DSpace log file: {{\[dspace\]/log/dspace.log}} (usually) |
Tomcat log directory: {{\[tomcat\]/logs}} (usually) |
1.5.1 or previous: {{\[tomcat\]/webapps/<name-of-webapp>/WEB-INF/logs/}} |
1.5.2 or later: {{\[dspace\]/log/cocoon.log}} |
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. |
tail -100 dspace.log
).
yyyy-mm-dd time WARN ...
OR,yyyy-mm-dd time ERROR ...
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: |
dspace.log
file, change the log4j.rootCategory
and log4j.logger.org.dspace
settings to DEBUG
rather than INFO
.cocoon.log
file, change the log4j.logger.org.apache.cocoon
setting to DEBUG
rather than INFO
.log4j.properties
file.