Help needed in DSpace 6.3
347 views
Skip to first unread message
rdias...@gmail.com
Dec 26, 2023, 10:36:06 AM12/26/23
to DSpace Technical Support
Hi, all.
First I apollogize for using this list to ask for help in DSpace 6.3, yet. But it's needed.
If you think it's not feasible to give help in this old version here, in this list, please tell me where I can find this kind of help.
Finally, the problem.
I have a version of DSpace 6.3 running on a Ubuntu 22.04 box with tomcat 9. It was running smoothly until yesterday, when I made some changes in discovery.xml and issued a
<dspace>/bin/dspace index-discovery -b, during the hollyday (yesterday).
Today, all access have Internal Error messages.
First I apollogize for using this list to ask for help in DSpace 6.3, yet. But it's needed.
If you think it's not feasible to give help in this old version here, in this list, please tell me where I can find this kind of help.
Finally, the problem.
I have a version of DSpace 6.3 running on a Ubuntu 22.04 box with tomcat 9. It was running smoothly until yesterday, when I made some changes in discovery.xml and issued a
<dspace>/bin/dspace index-discovery -b, during the hollyday (yesterday).
Today, all access have Internal Error messages.
Looking at the logs, I found messages like:
2023-12-26 00:00:10,345 ERROR org.dspace.app.webui.discovery.DiscoverUtility @ anonymous:session_id=B90492ADBC912FE95DBC320FD303954F:ip_addr=185.191.171.14:Error in discovery while setting up date facet range:date facet\colon; dateIssued.year
org.dspace.discovery.SearchServiceException: Expected mime type application/octet-stream but got text/html. <!doctype html><html lang="en"><head><title>HTTP Status 500 – Internal Server Error</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 500 – Internal Server Error</h1><hr class="line" /><p><b>Type</b> Status Report</p><p><b>Message</b> {msg=SolrCore 'search' is not available due to init failure: Error opening new searcher,trace=org.apache.solr.common.SolrException: SolrCore 'search' is not available due to init failure: Error opening new searcher
2023-12-26 00:00:10,345 ERROR org.dspace.app.webui.discovery.DiscoverUtility @ anonymous:session_id=B90492ADBC912FE95DBC320FD303954F:ip_addr=185.191.171.14:Error in discovery while setting up date facet range:date facet\colon; dateIssued.year
org.dspace.discovery.SearchServiceException: Expected mime type application/octet-stream but got text/html. <!doctype html><html lang="en"><head><title>HTTP Status 500 – Internal Server Error</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 500 – Internal Server Error</h1><hr class="line" /><p><b>Type</b> Status Report</p><p><b>Message</b> {msg=SolrCore 'search' is not available due to init failure: Error opening new searcher,trace=org.apache.solr.common.SolrException: SolrCore 'search' is not available due to init failure: Error opening new searcher
Caused by: org.apache.solr.common.SolrException: Error opening new searcher
Caused by: org.apache.lucene.index.CorruptIndexException: codec footer mismatch: actual footer=0 vs expected footer=-1071082520 (resource: MMapIndexInput(path="/NovoRIMA/solr/search/data/index/_1bqf_Lucene41_0.tim"))
Caused by: org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Expected mime type application/octet-stream but got text/html. <!doctype html><html lang="en"><head><title>HTTP Status 500 – Internal Server Error</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 500 – Internal Server Error</h1><hr class="line" /><p><b>Type</b> Status Report</p><p><b>Message</b> {msg=SolrCore 'search' is not available due to init failure: Error opening new searcher,trace=org.apache.solr.common.SolrException: SolrCore 'search' is not available due to init failure: Error opening new searcher
At first I thought to reissue the command, at least to see what kind of errors it gives me but I'm really affraid of what more it could cause.
And I also think that if I stop tomcat it will never comes back, because solr will not begin.
Please, any help will be very well appreciated.
Thansk,
Ricardo
rdias...@gmail.com
Dec 28, 2023, 8:39:14 AM12/28/23
to DSpace Technical Support
Well, I tried to make sth I didn't believe could help.
I moved <dspace:/solr/search/data/index to <dspace:/solr/search/data/index.back (why save a corrupted index? I'd say: just in case).
Then I created a new and empty <dspace:/solr/search/data/index directory, with the appropriate permissions.
Stopped tomcat and restarted tomcat, again.
Then I went to the browser to see if anything occurred with the Internal Error. And it did! I could see the home page but with all community counts equal to zero. I could also navigate to every community, collection and item.
I saw that <dspace:/solr/search/data/index had 3 or 4 files, which sounded that DSpace had created a new empty search index.
I issued the <dspace>/bin/dspace index-discovery -b command and waited a lot, but I could see that DSpace was creating a new solr search index.
When the command finished, all the communities and collections counts were there, again.
I moved <dspace:/solr/search/data/index to <dspace:/solr/search/data/index.back (why save a corrupted index? I'd say: just in case).
Then I created a new and empty <dspace:/solr/search/data/index directory, with the appropriate permissions.
Stopped tomcat and restarted tomcat, again.
Then I went to the browser to see if anything occurred with the Internal Error. And it did! I could see the home page but with all community counts equal to zero. I could also navigate to every community, collection and item.
I saw that <dspace:/solr/search/data/index had 3 or 4 files, which sounded that DSpace had created a new empty search index.
I issued the <dspace>/bin/dspace index-discovery -b command and waited a lot, but I could see that DSpace was creating a new solr search index.
When the command finished, all the communities and collections counts were there, again.
Only to close things: before doing any of the steps above, I created a backup of <dspace> directory tree and database in another machine, with DSpace installed and put it to work (with the original errors, of course). Only after that I tried to reproduce the above procedure in the production repository. Fortunately, it worked as expected.
Of course, I could count on the spiritual help of all the participants on this list, even if they were not able to offer support at this time. After all, it is Christmas and we are all imbued with an engaging spirituality, no matter what each person's belief or disbelief is.
Thank you all.
Thank you all.
Reply all
Reply to author
Forward
0 new messages