SUNScholar/Troubleshooting

BACK TO DEVELOPMENT

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.

loglevel.other = DEBUG loglevel.dspace = DEBUG 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!
 * 1) To turn on debugging, visit the $HOME/config/log4j.properties file and modify log levels as needed. You'll need to restart Tomcat after enabling DEBUG mode in the log4j.properties file.
 * 2) To enable DEBUG logging in the $HOME/log/dspace.log file, change the log4j.rootCategory and log4j.logger.org.dspace settings to DEBUG rather than INFO.
 * 3) (XMLUI Only) To enable DEBUG logging in the $HOME/log/cocoon.log file, change the log4j.logger.org.apache.cocoon setting to DEBUG rather than INFO.
 * 4) With DSpace versions =>4.X, log levels can now be set in the $HOME/source/build.properties file. To change log levels, edit the $HOME/source/build.properties file and then rebuild DSpace.
 * Sample "build.properties" config settings for log level.
 * 1) LOGLEVEL SETTINGS #
 * 1) LOGLEVEL SETTINGS #
 * 1) loglevel.other: Log level for other third-party tools/APIs used by DSpace
 * 2) Possible values (from most to least info): DEBUG, INFO, WARN, ERROR, FATAL
 * 1) loglevel.dspace: Log level for all DSpace-specific code (org.dspace.*)
 * 2) Possible values (from most to least info): DEBUG, INFO, WARN, ERROR, FATAL

Also see: https://github.com/DSpace/DSpace/pull/1364