Versions Compared

Old Version 5

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 6

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Wiki Markup
    *The source directory:*:  This is where (surprise\!) the source code lives. Note that the config files here are used only during the initial install process. After the install, config files should be changed in the install directory. It is referred to in this document as _\[dspace-source\]_.
  • Wiki Markup
    *The install directory:*:  This directory is populated during the install process and also by DSpace as it runs. It contains config files, command-line tools (and the libraries necessary to run them), and usually \-\- although not necessarily \-\- the contents of the DSpace archive (depending on how DSpace is configured). After the initial build and install, changes to config files should be made in this directory. It is referred to in this document as _\[dspace\]_.
  • Wiki Markup
    *The web deployment directory:*:  This directory is generated by the web server the first time it finds a dspace.war file in its webapps directory. It contains the unpacked contents of dspace.war, i.e. the JSPs and java classes and libraries necessary to run DSpace. Files in this directory should never be edited directly; if you wish to modify your DSpace installation, you should edit files in the source directory and then rebuild. The contents of this directory aren't listed here since its creation is completely automatic. It is usually referred to in this document as _\[tomcat\]/webapps/dspace_.

...

Log File

What's In It

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0e379ebad541cae0-dc641c66-4d624906-b3209b4f-8f1547c01c676ce837e3361f"><ac:plain-text-body><![CDATA[

[dspace]/log/dspace.log

Main DSpace log file. This is where the DSpace code writes a simple log of events and errors that occur within the DSpace code. You can control the verbosity of this by editing the [dspace-source]/config/templates/log4j.properties file and then running "ant init_configs".

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f1a97b0b68ccd471-577d4bb8-48ea4c50-a9f9bd0e-6649bd34e953c653292b593f"><ac:plain-text-body><![CDATA[

[tomcat]/logs/catalina.out

This is where Tomcat's standard output is written. Many errors that occur within the Tomcat code are logged here. For example, if Tomcat can't find the DSpace code (dspace.jar), it would be logged in catalina.out.

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e6f237186d6188cd-2c689c94-444541b1-b744b31f-1b72ec8235f502e881bfba67"><ac:plain-text-body><![CDATA[

[tomcat]/logs/hostname_log.yyyy-mm-dd.txt

If you're running Tomcat stand-alone (without Apache), it logs some information and errors for specific Web applications to this log file. hostname will be your host name (e.g. dspace.myu.edu) and yyyy-mm-dd will be the date.

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="6a251eb394e9ad21-0f9cd7c8-448245e9-8346976d-c8c98cd942c21d50ce7b5165"><ac:plain-text-body><![CDATA[

[tomcat]/logs/apache_log.yyyy-mm-dd.txt

If you're using Apache, Tomcat logs information about Web applications running through Apache (mod_webapp) in this log file (yyyy-mm-dd being the date.)

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="969e0b701d386e84-dae36e05-46ed4330-ba2eb3c6-ac41aad0f7250eda0711490e"><ac:plain-text-body><![CDATA[

[apache]/error_log

Apache logs to this file. If there is a problem with getting mod_webapp working, this is a good place to look for clues. Apache also writes to several other log files, though error_log tends to contain the most useful information for tracking down problems.

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b6be938ef0706aa4-35cc62d5-49cf4471-af9381f1-93c4b3b993869c609a65ce3f"><ac:plain-text-body><![CDATA[

[dspace]/log/handle-plug.log

The Handle server runs as a separate process from the DSpace Web UI (which runs under Tomcat's JVM). Due to a limitation of log4j's 'rolling file appenders', the DSpace code running in the Handle server's JVM must use a separate log file. The DSpace code that is run as part of a Handle resolution request writes log information to this file. You can control the verbosity of this by editing [dspace-source]/config/templates/log4j-handle-plugin.properties.

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="122000a392b3f8e6-181a6825-465342aa-bcc5987c-621a25635a479d0accb94718"><ac:plain-text-body><![CDATA[

[dspace]/log/handle-server.log

This is the log file for CNRI's Handle server code. If a problem occurs within the Handle server code, before DSpace's plug-in is invoked, this is where it may be logged.

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d8ca7081180aba31-2bb53042-4fda4707-9c31b3ca-9ffbb7a648a1ba3935dd4d70"><ac:plain-text-body><![CDATA[

[dspace]/handle-server/error.log

On the other hand, a problem with CNRI's Handle server code might be logged here.

]]></ac:plain-text-body></ac:structured-macro>

PostgreSQL log

PostgreSQL also writes a log file. This one doesn't seem to have a default location, you probably had to specify it yourself at some point during installation. In general, this log file rarely contains pertinent information--PostgreSQL is pretty stable, you're more likely to encounter problems with connecting via JDBC, and these problems will be logged in dspace.log.

...