Hi Julio, On 09/06/12 00:49, Julio Pemau wrote: > When sending records via SWORD, in pre-production environment the > process is working properly, but if we do it in the production > environment the record is recorded, but the lucene indexes are not > updated with the new record.
The first thing I'd check is whether this affects only items coming in via Sword or whether there's a general problem with indexing. When you change the metadata of an existing record, is the change reflected in the search indexes then? What happens when you manually try to update the index, ie when you run [dspace]/bin/dspace index-update? Does the user running dspace have write permissions to the index directory in your production environment? The directory is [dspace]/search. Also, when the lucene indexer is killed / crashes, it will leave behind a write lock file in the index directory. When this file is present, subsequent indexing attempts will fail. The file is called write.lock; if it is present in your index directory while no indexing attempt is running, you should try deleting it. See http://dspace.2283337.n4.nabble.com/Dspace-tech-Problem-with-quot-write-lock-quot-file-in-dspace-search-DSpace-1-5-1-td3277358.html for some more information. cheers, Andrea -- Dr Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
