Difference between revisions of "SUNScholar/Troubleshooting"
Jump to navigation
Jump to search
m |
m |
||
| Line 9: | Line 9: | ||
*To turn on debugging, visit the '''/home/dspace/config/log4j.properties''' file and do the following: | *To turn on debugging, visit the '''/home/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. | + | *To enable DEBUG logging in the '''/home/dspace/log/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. | *(XMLUI Only) To enable DEBUG logging in the cocoon.log file, change the log4j.logger.org.apache.cocoon setting to DEBUG rather than INFO. | ||
Revision as of 09:47, 4 August 2014
Back to Optimisations
Contents
Logs Debug Mode
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 /home/dspace/config/log4j.properties file and do the following:
- To enable DEBUG logging in the /home/dspace/log/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!
