Dear DSpace Technical Support Team,

I am writing to request your urgent assistance in resolving a critical 
issue with our DSpace repository.

We are currently using *DSpace 6.3 (JSPUI)* on *Ubuntu 20.04 LTS*. Our 
repository was working previously, but it is now displaying an *Internal 
System Error*, preventing users from accessing the repository.
System Environment
   
   - 
   
   DSpace Version: 6.3 (JSPUI)
   - 
   
   Operating System: Ubuntu 20.04 LTS
   - 
   
   Database: PostgreSQL 12
   - 
   
   Application Server: Apache Tomcat 9
   - 
   
   Search Engine: Apache Solr
   
Error Displayed

When opening the DSpace website, the following message appears:

*Internal System Error*

The system has experienced an internal error. Please try to do what you 
were doing again, and if the problem persists, please contact us so we can 
fix the problem.

Troubleshooting Performed

To resolve the issue, I have already performed the following checks:

   - 
   
   Verified that PostgreSQL is running normally.
   - 
   
   Verified that Apache Tomcat 9 is running.
   - 
   
   Confirmed that the DSpace database is accessible and contains 
   approximately *1,352 items*.
   - 
   
   Checked the DSpace configuration files.
   - 
   
   Reviewed Tomcat and DSpace log files.
   - 
   
   Corrected ownership and permissions of the /dspace directory.
   - 
   
   Corrected permissions on the /dspace/log and /dspace/solr directories.
   - 
   
   Added the Tomcat user to the DSpace group.
   - 
   
   Restarted Tomcat several times.
   - 
   
   Checked the Solr application.
   - 
   
   Attempted to rebuild the Solr search index.
   - 
   
   Verified that the filesystem is writable.
   
Errors Found

During troubleshooting, I observed the following issues:

   - 
   
   Solr search core initialization failure.
   - 
   
   Search core reported as unavailable.
   - 
   
   Permission-related errors involving the /dspace/log and /dspace/solr 
   directories.
   - 
   
   Previous log entries showed "Permission denied" and "Read-only file 
   system" errors.
   - 
   
   Although these permission issues have been corrected, the repository 
   still displays the same *Internal System Error*.
   
Current Status
   
   - 
   
   PostgreSQL service: Running
   - 
   
   Apache Tomcat 9: Running
   - 
   
   Solr application: Accessible
   - 
   
   DSpace Web Interface: Displays *Internal System Error*
   
Request for Assistance

I would greatly appreciate your help in identifying the root cause of this 
problem and restoring the repository to normal operation.

Could you please advise:

   1. 
   
   What could be causing the Internal System Error?
   2. 
   
   How can I resolve the Solr search core initialization problem?
   3. 
   
   Are there any additional configuration files or services that should be 
   checked?
   4. 
   
   What diagnostic steps do you recommend to identify the exact cause?
   5. 
   
   Is there any procedure to safely rebuild the DSpace search indexes 
   without affecting the existing repository?
   
If required, I can provide the following information:

   - 
   
   DSpace log (dspace.log)
   - 
   
   Tomcat logs (catalina.out)
   - 
   
   Solr logs
   - 
   
   PostgreSQL logs
   - 
   
   local.cfg
   - 
   
   Configuration files
   - 
   
   Directory permissions
   - 
   
   Any additional information needed for diagnosis
   
This repository is actively used by our institution, so your assistance in 
resolving this issue would be greatly appreciated.

Thank you very much for your time and support. I look forward to your 
guidance.


-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://lyrasis.org/code-of-conduct/
--- 
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 view this discussion visit 
https://groups.google.com/d/msgid/dspace-tech/94f90a98-6398-43e8-bee3-55105452e576n%40googlegroups.com.

Reply via email to