Dspace 7.6 deposit issue

[Poulter, Dale]

Good morning,

 

We are running Dspace 7.6 behind an AWS ALB and using Apache mod-proxy in front of tomcat.  We are able to upload documents, add content to the submission form,  save the form and save the form for later.  However when we attempt to deposit if fails with the error that something has gone wrong.  I do not see errors in the tomcat, dspace, apache, or pm2 logs. It does appear in the developer tools that https://dev-irbe.library.vanderbilt.edu/server/api/workflow/workflowitems?projection=full fails (status 504, type xhr).  Has anyone encountered and resolved this issue?  Thanks!

 

 

-Dale

 

Dale Poulter Director, Library Technology and Assessment Services Vanderbilt Libraries | Vanderbilt University 615-343-5388 | dale.p...@Vanderbilt.Edu | https://www.library.vanderbilt.edu Pronouns: he/him/his   My working day may not be your working day. Please do not feel obliged to reply to this email outside of your normal working hours.

 

 

[Michael Plate]

Hi Dale,

Am 20.05.24 um 17:32 schrieb 'Poulter, Dale' via DSpace Technical Support:

> Good morning,
>
> We are running Dspace 7.6 behind an AWS ALB and using Apache mod-proxy
> in front of tomcat.  We are able to upload documents, add content to the
> submission form,  save the form and save the form for later.  However
> when we attempt to deposit if fails with the error that something has
> gone wrong.  I do not see errors in the tomcat, dspace, apache, or pm2
> logs. It does appear in the developer tools that

> https://dev-irbe.library.vanderbilt.edu/server/api/workflow/workflowitems?projection=full <https://dev-irbe.library.vanderbilt.edu/server/api/workflow/workflowitems?projection=full> fails (status 504, type xhr).  Has anyone encountered and resolved this issue?  Thanks!
>
[…]

I had this a while ago, so I'm not sure if this is the same problem.
It helped removing / changing metadata fields from the
submission-forms.xml until the problem vanished.
Look that all XML-elements for the field(s) are complete (the
submission-forms.dtd shows those you _need_, e.g. "hint" wich we missed
partially).
This is somewhat unspecific, sorry - could be the wrong way…

CU

Michael

[DSpace Technical Support]

Hi Dale,

A 504 error is a Gateway Timeout.  That tends to mean there may be a connection issue to the site itself...or between the frontend & backend.

I'd recommend taking a look at our Troubleshooting Guide: https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Specifically, if the UI or REST API is misconfigured, it's possible that the UI is somehow failing to send data to the REST API.  These types of errors will *never* appear in backend logs...they are only visible in your web browser (in DevTools on the Network tab).   So, the best approach would be to open your browser's DevTools and try to reproduce the error.  You should hopefully see a more detailed error in the Network tab (see Troubleshooting guide), which may provide you a hint as to what is going on.

If it is a connection error or configuration error, then you are likely to see one of the errors listed in our Common Installation Issues here: https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues   In which case that page should walk you through steps to try to solve the problem.

Good luck & hopefully this helps!

Tim