Hi George,

On 25/03/15 10:06, George Stanley Kozak wrote:
Thank you for your suggestions.  I did check and my tomcat (tomcat 7) is owned by my dspace user as is my solr index, so tomcat should be able to write to the solr directory (it works OK for 4.2).  So, I am not sure what is causing the permission problem, but I will keep checking.

Have you run a chown with the -c flag on your solr directory? That will tell you about any changes it makes. Might be worth it just so you can go from "tomcat should be able to write to the solr directory" to "tomcat is definitely able to write to the solr directory". Just on the off-chance this is happening to you: I've had nasty surprises when the solr directory was on a different partition and symlinked into [dspace], chown -R didn't work across the symlink (it changed ownership of the symlink but not of the symlinked directory).

Also, if the permissions have been wrong in the past at some point, sometimes the write.lock file sticks around with wrong write permissions. In that case, it helps to stop tomcat, delete the write.lock file, then start tomcat.

cheers,
Andrea

-- 
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to