Skip to content

Latest commit

 

History

History
40 lines (30 loc) · 1.32 KB

FixDSpaceWasRunningAsRoot.md

File metadata and controls

40 lines (30 loc) · 1.32 KB
Raw

Fixes to apply if DSpace was running as root

DISCLAIMER

These instructions have been written after the event and may lack accuracy. They are expected to be a guide only. You are expected to understand the consequences of any Linux commands which you invoke. Use at your own risk.

Guidelines

If the DSpace 3.x web app (ie. java tomcat) is started as the root user by mistake, then started later as the unprivileged DSPACE_OWNER, you are likely to encounter ownership problems in the following directory trees.

  1. DSPACE_DIR (where DSPACE_DIR is dspace.dir within the dspace.cfg configuration file)
  2. ~tomcat/logs
  3. /var/cache/tomcat*/work/Catalina/localhost/xmlui/cache-dir

The above problems can probably be fixed with a recursive correction of ownership in each of the above directory trees. Ie.

  chown -R DSPACE_OWNER ...
  • Fixing item 1 should allow you to see permission errors (eg. in DSPACE_DIR/log) and fix SOLR errors.
  • Fixing item 2 should allow you to see some more permission errors. At this point the JSPUI should work.
  • Fixing item 3 should allow the XMLUI to work.

Some useful commands to find ownership/permission problems are given below.

grep -i permission ~tomcat/logs/catalina.out
grep -i permission DSPACE_DIR/log/cocoon.log.YYYY-MM-DD
less DSPACE_DIR/log/dspace.log.YYYY-MM-DD