Either Solr indexing is still in progress from the first run or the Solr core is still locked from a previous interrupted run.
In either case, you can stop DSpace, delete the write.lock file, restart DSpace and run the reindex again. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette On Mon, Feb 22, 2016 at 4:25 PM, Jose Blanco <[email protected]> wrote: > when I try to index discovery: > ./dspace index-discovery -b > > > I'm getting this > {msg=SolrCore 'search' is not available due to init failure: Index locked > for write for core searc > h,trace=org.apache.solr.common.SolrException: SolrCore 'search' is not > available due to init failure: Ind > ex locked for write for core search > > > On Mon, Feb 22, 2016 at 9:46 AM, Jose Blanco <[email protected]> wrote: >> >> thank you. it just completed a few minutes ago. >> >> On Mon, Feb 22, 2016 at 9:40 AM, helix84 <[email protected]> wrote: >>> >>> Yes, it is equivalent to running it manually. You could interrupt it >>> by stopping DSpace and then running the command manually. >>> >>> >>> Regards, >>> ~~helix84 >>> >>> Compulsory reading: DSpace Mailing List Etiquette >>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette >> >> > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
