On Fri, May 3, 2013 at 10:20 PM, Will Clarke <[email protected]> wrote: > Very odd indeed. I seem to have confirmed that it is a permissions issue - > but using chown to make dspace the owner did not do the trick. I made the > asset directory world-writeable (don't do this on yours) and uploaded a > file. the new file was owned by tomcat6. Did I miss something in the dspace > setup as far as the dspace user and the tomcat user goes?
So you're running tomcat as the "tomcat6" user while the "dspace" user owns your dspace installation directory? They both need to be the same user. So either run Tomcat as "dspace" or chown -R your dspace installation directory to "tomcat6". This is an important consideration mentioned more than once in the installation chapter because it's known to cause permission issues: https://wiki.duraspace.org/display/DSDOC3x/Installation "This needs to be the same user that Tomcat (or Jetty etc.) will run as" "Note that DSpace will need to run as the same user as Tomcat, so you might want to install and run Tomcat as a user called 'dspace'. Set the environment variable TOMCAT_USER appropriately." Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
