Hello, this issue is not yet completely solved. This is an interim information on the status.
Meanwhile I applied updates to some of the software on my test machine and after that I ran again in exactly the same issue. I checked for the solr URL as well as for file system permissions faults due to my former experience and repeated hints on this list. However no luck. I couldnt find any useful log entries not even when switching to debug logging. I removed the filter that made it impossible to reach solr from a different machine to see the error messages first hand in my browser - no help. Finally I dropped my database on the test server which was updated from a 1.6 installation and contained a handful of items. We also have some additional date fields configured in input-forms and we use a three letter contry code for metadata. I dont know what exactly was defending discovery index creation, but with a fresh and empty database, discovery index could be initialized. This is no solution for migrating our live server, because obviously we have to update our current database, but I thought it might be useful for somebody struggling with this issue to know that there are other reasons of failure besides the solr URL being not set properly. Bye, Christian ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
