On Wed, Aug 07, 2024 at 07:52:18PM +0000, DSpace Technical Support wrote: > The separation of the frontend & backend in DSpace 7 (and 8) should have no > impacts on running the Handle Server. The embedded Handle Server that comes > with DSpace 7 (or 8) should still work properly, as it *only* relies on the > DSpace backend.
Here there is one thing I've run into. Front-end is on (let us call it) Bugs and back-end is on Daffy. Both are behind an Apache HTTPD reverse proxy which (for now) runs on Bugs. I haven't yet found a way to configure the proxy to run the Handle server on Daffy (where it is installed by the normal process) so I have a copy of the back end on Bugs to run Handle service there. Other than the proxy issue, the Handle server has no reason to care where it is running. (The issue is that the proxy doesn't grok the Handle protocol so I can't proxy port 2641 at all, and Daffy has no public IP address so it would *have to be* proxied from there. So the Handle server is directly exposed on its usual ports, on Bugs.) That doesn't sound like the problem here, but there do exist layouts where it does make a diffference where the Handle server runs. > If the issue you've found is because you are using a *different* hostname for > the frontend and backend, then one option is to ensure you use the *same* > hostname for both. For instance, on our demo site, the frontend runs at > https://demo.dspace.org/, and the backend is at > https::/demo.dspace.org/server/. So, they share the same hostname, but the > backend is on the /server path. > > If that doesn't help, it may be useful to share the exact command you ran & > the errors you are receiving when you start up the Handle Server (if nothing > is reported on the commandline, then check your logs -- both dspace.log and > see if any logs appear under [dspace]/handle-server/) > > Hopefully that gives you a few tips to get started. Otherwise, we may need > more information about the errors you are seeing in order to provide better > hints/tips. > > Tim > > On Tuesday, August 6, 2024 at 9:56:25 AM UTC-5 [email protected] wrote: > We've just migrated from DS5 to DS7.6.1 with security fix. Our handle server > is broken and when we try to run the script for making a handle config it > doesn't ask any question and doesn't create a file and it writes nothing to > any config files. We found other people saying that it worked for them with a > few changes (changing directories or specifying a directory in the command > line) but none of what helped them worked for us. In this situation I would run the configure script under 'strace' or the like, to see what it does before dying and what killed it. > So I've downloaded the Handle.net software and I'm looking through that. The > question that comes to my mind is how the split between the backend and > frontend servers affects handle configuration. Our official hostname is > uwspace.uwaterloo.ca<http://uwspace.uwaterloo.ca> and that is now our > frontend server, but the software for the handle server is part of the > backend server. It sounds like you run front-end on one host and back-end on another, as we do, so (when you get the Handle server up and running) you may encounter the same issue that we did re: proxying. I haven't given up on that. I am trying to get to a setup in which the proxy runs alone on a tiny virtual host while both back-end and front-end run on other hosts with no public addresses. HAProxy looks promising. -- Mark H. Wood Lead Technology Analyst University Library Indiana University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 library.indianapolis.iu.edu -- 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 on the web visit https://groups.google.com/d/msgid/dspace-tech/ZrS5XuWacI4bH5R9%40iu.edu.
signature.asc
Description: PGP signature
