when I try to register a new item in Dspace 7.5 don't appear

99 views
Skip to first unread message

EDUARDO SE

unread,
Nov 15, 2024, 2:14:15 PM11/15/24
to DSpace Technical Support
Hello group, 
On November 12th I sent to the community a request for help, titled 'Dspace 7.5 news items...' 
I apologize for insisting, but I believe that in the group there are members with much more knowledge than mine, and the problem remains unresolved. Could someone at least guide me where I should investigate?
The problem arose without apparent cause
Thanks in advance

DSpace Technical Support

unread,
Nov 18, 2024, 12:23:07 PM11/18/24
to DSpace Technical Support
Hi,

I tried to provide some general advice in your other message: https://groups.google.com/g/dspace-tech/c/YPdIY9o6LZ8

Tim

EDUARDO SE

unread,
Nov 18, 2024, 5:06:28 PM11/18/24
to DSpace Technical Support
Hello Tim,
First of all, I want to thank you for your help, and I apologize for not having seen your previous response, because I didn't get the notice on the phone.
Following your advice I have consulted the 'Troubleshoot an error' guide, and I have obtained:
1 - in the chrome console:

failed to load resource: the server responded with a status of 404() (3 times)

2 - in dspace.log: many errors, including

2024-11-08 10:52:05,386 ERROR unknown 190daf95-522d-48c5-9398-c2b20449d8c4 org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ An internal read or write operation failed (status:500)
org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe

ERROR unknown unknown org.springframework.boot.web.servlet.support.ErrorPageFilter @ Cannot forward to error page for request [/api/core/bitstreams/7cdf01c8-79ec-45e9-a3bd-27b8c3f6c015/content] as the response has already been committed. As a result, the response may have the wrong status code. If your application is running on WebSphere Application Server you may be able to resolve this problem by setting com.ibm.ws.webcontainer.invokeFlushAfterService to false

Error from server at http://localhost:8983/solr/search: this IndexWriter is closed

Error from server at http://localhost:8983/solr/statistics: Server error writing document id edeb6b52-0e53-4667-8941-b80edc43ef1c to the index
2024-11-18 12:15:58,097 ERROR unknown 7428ee5d-9cf7-4387-84bf-b61fe8898a3f org.dspace.statistics.SolrLoggerUsageEventListener @ Error processing/logging UsageEvent bitstream:view
2024-11-18 12:45:01,161 ERROR unknown b4989358-c500-448b-a839-1ab9657c7804 org.dspace.discovery.IndexEventConsumer @ Failed while indexing object:
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://localhost:8983/solr/search: Server error writing document id Item-29a6a85d-00b2-4769-8faf-7c1b55ff9291 to the index
2024-11-18 12:45:01,178 ERROR unknown b4989358-c500-448b-a839-1ab9657c7804 org.dspace.discovery.indexobject.IndexFactoryImpl @ Error occurred while writing SOLR document for Collection object 4a17ecf5-7ce1-422e-b952-9db0c4f0142d
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://localhost:8983/solr/search: Server error writing document id Collection-4a17ecf5-7ce1-422e-b952-9db0c4f0142d to the index
2024-11-18 12:45:35,242 ERROR 8049f911-bf46-476f-a943-6cc905454bd5 74f75126-60a9-49ac-b2fd-2d322a2dfc65 org.dspace.discovery.IndexEventConsumer @ Failed while UN-indexing object: Item-ede42b64-9792-4a00-a80b-48413f2602c8
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://localhost:8983/solr/search: this IndexWriter is closed

and so.

There are no errors in the Apache and Tomcat logs

That's why I think that all the problems come from some misuse of solr (I have no experience), so I don't know if the solution will be to reinstall it or reindex.
In any case, thank you very much for your help. At least now I know where the problem is and I can investigate how to fix it.

DSpace Technical Support

unread,
Nov 19, 2024, 1:27:56 PM11/19/24
to DSpace Technical Support
Hi,

It definitely sounds like an error writing to Solr, which means that all searching/browsing in DSpace will not work (as Solr is used for all search/browse). The error itself is vague, as it seems to just say that Solr cannot be written to. You may want to also see if the Solr logs have additional details on the error.

If you cannot find more information, then I would recommend trying to reinstall Solr.  It's possible something didn't install properly, or it might be a permissions issue in your current Solr installation.  

Tim

EDUARDO SE

unread,
Nov 27, 2024, 7:42:34 AM11/27/24
to DSpace Technical Support
Hello to the whole group
A few days ago and suddenly I had a problem working with dspace 7.5: I registered new items, and received the message 'Item sent successfully', but the items were not visible in their collections
When I consulted the group about the problem, Tim recommended that I study the dspace and tomcat logs, as well as look at errors in the chrome console
No error appeared in the logs, and in the chrome console it was a very undefined one, something similar to 'solr cannot write the indexes'
Again Tim recommended that I study the solr logs, but the same undefined error appeared.
But, in the solr web console (https://IP:8983), in the 'Loggins' section a new error appeared, something similar to 'there is no space on the solr installation disk.
Therefore I mounted a new larger capacity disk in the virtual machine, stopped the solr service, and directly copied the entire 'solr' folder from its location to the new disk.
I restarted the solr service and everything worked perfectly again
I have also moved the postgresql database to the new disk.
I want to explain this to the group in case it can help someone.
I also want to thank you for the help I have received, and special thanks to Tim.
I'm new to dspace (I've worked on other repositories), so the help has been very useful to me
Reply all
Reply to author
Forward
0 new messages