*Thank you both Mark and Michael for your responses and suggestions.I really appreciate it!* *Mark, to answer your question, the Tomcat log was perfect. *
It showed: - Tomcat started without any errors. - It used the correct Java 17 version. - It contained the line Deployment of web application directory [/var/lib/tomcat9/webapps/server] has finished, which is the confirmation that the DSpace backend application started successfully. *Michael, for step one I did the following on the backend server:* 1. Attempted to Run DSpace Directly - *Command:* sudo -u tomcat java -jar /dspace/webapps/server/WEB-INF/lib/dspace-server-boot.jar - *Result:* This failed with an "Unable to access jarfile" error. 2. Diagnosed the Missing File To figure out why the file was inaccessible, we tried to list it directly. - *Command:* ls -l /dspace/webapps/server/WEB-INF/lib/dspace-server-boot.jar - *Result:* This produced a *No such file or directory* error. 3. Identified the Root Cause That "No such file or directory" error indicated that the main DSpace application file was completely missing. This meant the original mvn package build had failed silently, without producing the necessary files. 4. Performed a Clean Rebuild To fix the missing file, I performed a complete, clean rebuild of the backend application. 1. *Ran mvn clean* to delete the old, incomplete build artifacts. 2. *Switched to the dspace user* (because the root user was using the wrong Maven version). 3. *Ran mvn package again.* Confirmed this build completed successfully. 5. Re-installed the Backend Files After the successful build, I re-installed the new, complete set of application files. 1. Cleared the old installation with sudo rm -rf /dspace/*. 2. Copied the new files from the build directory with sudo cp -r .... 3. Set the correct ownership with sudo chown -R tomcat:tomcat /dspace. 4. Restarted the solr and tomcat9 services. After all those steps, I confirmed that the backend services were running, but was still seeing the same 404 error and the blank frontend page. I don't know what more to do. *Michael, for step two, I did the following on the Front End server:* 1. *Updated the Configuration* Replaced the config.prod.yml file with the official example file. This pointed the user interface to a public, working DSpace backend (demo.dspace.org). 2. *Rebuilt the Application* Ran the yarn build:prod command to compile the entire user interface with these new settings. 3. *Deployed the New Files* Moved the newly built files into the Nginx web directory (/var/www/html/dspace/) and restarted Nginx. 4. *Fixed a Final Error* Manually created the missing assets/config.json file to resolve a final JavaScript error. The outcome seems to be that the frontend is correctly installed, but the build process on the server has a persistent environmental issue that prevents the configuration from loading correctly, even when using the default settings. *As you both can probably tell, I have been using Gemini to help navigate through all of this. The following* *is how Gemini suggests I describe the problem to you all:* "Hello, I have a DSpace 9 installation on two Ubuntu 22.04 servers that I need help with. I've been troubleshooting for a while and am stuck in a loop. *Backend (209.182.253.58):* The catalina.out log shows a clean startup and reports that the /server application has deployed successfully. Tomcat Manager also says it's Running: true. However, visiting the URL gives a 404 error, and the /dspace/log/dspace.log file is never created, indicating a silent startup failure. *Frontend (209.182.253.60):* The Angular application build completes, and the files are served by Nginx. However, the browser console always shows a TypeError: can't access property "nameSpace", _.ui is undefined. This happens even after multiple clean rebuilds with a verified config.prod.yml. We have already verified all standard issues (Java versions, file permissions, ownership, local.cfg, Solr connection, etc.). I need hands-on help to diagnose this unusual environmental problem." *Do either of you, or anyone you know, provide technical/troubleshooting services for something like this?* Again, many thanks for your responses! Sam On Wednesday, July 2, 2025 at 10:28:54 AM UTC-6 Michael Plate wrote: > Hi Sam, > > Am 02.07.25 um 06:24 schrieb Samuel Stoker: > > Hello everyone, > > > > I've am near completion of my first dSpace 9 installation on two Ubuntu > > 22.04 servers and am stuck on two final, stubborn issues: > > > > 1. > > > > *Backend (209.182.253.58):* The Tomcat Manager says the /server > > application is *Running: true*. Solr and PostgreSQL are also running > > and verified. However, visiting http://209.182.253.58:8080/server > > gives a Tomcat 404 error, and the /dspace/log/dspace.log file is > > never created, indicating a silent startup failure. > > > as a first try, stop tomcat and start dspace directly as the dspace user > on the cli: > > java -jar webapps/server-boot.jar > > it should listen on port 8080, usually localhost (if you configured the > real IP, it might not run w/o TLS, so try localhost first). > If the program returns immediately, you have a problem - remove the > logs/dspace.log file before, it will grow fast… > > > > > > 2. > > > > *Frontend (209.182.253.60):* The Angular application has been built > > and is served by Nginx. However, the browser console shows a > > TypeError: can't access property "nameSpace", _.ui is undefined. > > This happens even after repeatedly rebuilding the application with a > > correct config.prod.yml and deploying it to /var/www/html/dspace. > […] > > try the config.example.yml (with demo.dspace.org) as long as you don't > have a running backend. > > Michael > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- 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/587a0cda-89a6-4788-921c-f99e63130533n%40googlegroups.com.
