DSpace stuck on infinite loading on the starting screen - General loading issues

[Petros Grammatikopoulos]

Greetings, hope you are well

I am trying to complete a production-level installation of DSpace 7.1 and so far I believe I have gotten to the point of having a working backend, frontend, database and solr. Over HTTPS with Apache2 and a LetsEncrypt certificate on my current temporary domain.

https://s455778.name-servers.gr/
https://s455778.name-servers.gr/server/#/server/api

The issue is that, when I access the frontend, I am greeted with a loading animation that goes on indefinitely (as per issue1.png). Moreover, that same animation behavior persists when I reach the first screen after logging in as an administrator account. Also, the sidebar seems incomplete (as per issue2.png).

Attached is all the information that I have gathered around the system's functionality/configuration (the database password is hidden on local.cfg).

I think I am meant to focus on the fact that dspace.log contains an exception on line 219, which has a trace right afterwards

2021-11-30 14:33:55,594 ERROR unknown 8ffa97fa-9a7f-4ea9-9223-582e6535f9df org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ An exception has occurred (status:500)

All the logs seem to be pointing to a possible backend or database issue...
yet when using yarn config:check:rest, the frontend seems to be accessing the backend properly.

What else should I check? Any recommendations or guidance would be highly appreciated!
Kind regards,
Petros

-------------------------------
Petros Grammatikopoulos

Web IT Services & System Technician
@
South East European Research Centre - SEERC

Research Centre of CITY College, University of York Europe Campus

24 Pr. Koromila Str, 54622 Thessaloniki, GREECE

Office Tel. +30 2310 253477 (113 office number)

website: www.seerc.org

Email Disclaimer

The content in this e-mail and any attachments is confidential. It is intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, or person responsible for delivering this information to the intended recipient, please notify the sender immediately and delete this e-mail and any attachments from any computer storage or other medium. Unless you are the intended recipient or his/her representative you are not authorized to, and must not, read, copy, distribute, use or retain this message or any part of it. E-mail transmission cannot be guaranteed to be secure or error-free. Any views or opinions presented are solely those of the author and do not necessarily represent those of this organisation.

[Tim Donohue]

Hi Petros,

Based on your dspace.log, you are hitting a 500 error with this exception:

2021-11-30 14:33:55,594 ERROR unknown 8ffa97fa-9a7f-4ea9-9223-582e6535f9df org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ An exception has occurred (status:500)

java.lang.NullPointerException: null

at org.dspace.app.rest.converter.ConverterService.toRest(ConverterService.java:107) ~[classes/:7.1]

at org.dspace.app.rest.converter.ConverterService.toRestPage(ConverterService.java:203) ~[classes/:7.1]

at org.dspace.app.rest.repository.SiteRestRepository.findAll(SiteRestRepository.java:64) ~[classes/:7.1]

That exception/error seems to be saying that the Site object in your DSpace database hasn't been initialized (as it's returning null).  This may mean that one or more of your Database migrations failed.  You might want to run "./dspace database info" to see if there are any migrations that didn't run/succeed. If so, you can trigger them by running "./dspace database migrate".

If all migrations ran successfully, you may force DSpace to recreate this Site object by running "./dspace database migrate force" from the command-line.

Keep in mind, we also have a guide for locating error messages in DSpace 7 at https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)  This is useful to find the real error message either in your browser or in logs, so you don't have to send the entire files via email.

If you run into any other issues, you also should check the Common installation issues at  https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues

Finally, let us know on this list if you run into any other problems which are not already listed in those common installation issues.

Good luck,

Tim

---

From: 'Petros Grammatikopoulos' via DSpace Technical Support <dspac...@googlegroups.com>
Sent: Tuesday, November 30, 2021 7:22 AM
To: dspac...@googlegroups.com <dspac...@googlegroups.com>
Subject: [dspace-tech] Re: DSpace stuck on infinite loading on the starting screen - General loading issues

 

attachments 

-------------------------------
Petros Grammatikopoulos

Web IT Services & System Technician
@
South East European Research Centre - SEERC

Research Centre of CITY College, University of York Europe Campus

24 Pr. Koromila Str, 54622 Thessaloniki, GREECE

Office Tel. +30 2310 253477 (113 office number)

website: www.seerc.org

--
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 dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAHxO-n1KFVJiMKhuzwE4Xwqjx%2BkSiKmDhJC2Udcw%2B%2BRckdh9xw%40mail.gmail.com.

[Petros Grammatikopoulos]

Greetings,

For future reference for anyone that might need it:

For some reason enabling the pgcrypto extension the first recommended way in the docs didn't work for me

and then even "dspace database migrate force" wouldn't initialize the database properly, resulting in the described behavior on the frontend.

What solved it was following the "Alternative method: How to enable pgcrypto via a separate database schema" approach. After this the database was successfully initialized and the service just worked as expected

All the best,

Petros