-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, this is what I had to do just to get it to start up. The latest
on this is that the handle server starts and seems alright; however, it
absolutely _refuses_ to accept the fact that it's the authority for our
handle subdomain.
We opted to use a setup like 1234.abc where the numbers are our
top-level domain and the letters after the period are the institution
code that we're setting DSpace up for. Handle.net seems to be perfectly
fine with this less-than-common setup but I'm wondering how happy DSpace
is with it.
Since DSpace replaces the handle.net database backend with its own, not
only does 1234.abc need to be compatible with handle.net (something I
checked on before registering it) but also with the DSpace code. Unless
I hear back on here, I'm going to post to the developers list tomorrow
asking this very question and, if I turn out to be correct, how soon
they could have a bug fix patch ready.
I think I'll also mention how nice it would be if the next version of
DSpace used the handle.net daemon's API rather than hijacking its entire
backend.
- --
E. Stuart Hicks
Access Manager / Systems Engineer
OhioLINK
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I had this problem while our Dspace was in the internal network.
It had an internal addr 10.x.x.x, and an external IP, that would be
translated to it's internal IP, to all outside requests.
What was the problem with the handle:
Since you have an external IP you have to configure that external IP in
the handle.net, but you cannot start the deamon because the machine has
an internal IP, and not the one you providade to handle.net
To test the handle server i did a little workaround. Don't know if all
the users agree with this situation, or if there's a better situation,
but i did the following:
On the configuration wizard, i gave the external IP, and sent the zip
file to handle.net
Then, I've changed in config.dct the bind_address the external IP to
the 10.x.x.x
Then, started the handle and everything was working. The only problem i
had: When you are on the internal network and you acess you Dspace by
it's internal IP, when acessing via handle, will go to it's external IP.
Altough it's untested, you can avoid this by using it's name, instead
the IP.
Hope this helps,
Marcelo
Citando E. Stuart Hicks [EMAIL PROTECTED]:
We have a rather unorthidox firewall setup and I'm having problems
getting the DSpace handle.net server to work through it.
Basically, the DSpace server doesn't actually know what its
world-accessable IP is - it's on a 10. IP and has its traffic
translated/routed by a firewall. This appears to cause problems with
the handle.net service and I'm not even able to home it properly. Has
anyone encountered this before and been able to come up with a viable
solution that didn't require overhauling the network configuration?
Frankly, we would prefer to put the handle service on an entirely
separate box because this will not be the only DSpace instance that
we'll be hosting; however, that doesn't appear to be an option right
now. Does anyone know if 1.5 will support this?
Any help at all is appreciated. We have an end-of-the-week deadline to
meet and this is the final hurdle to overcome.
--
E. Stuart Hicks
Access Manager / Systems Engineer
OhioLINK
[EMAIL PROTECTED]
- -
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG8G/yqmBbivzHElIRAnAuAKCLOg7SARthuca+bfv5wGfj32zOXQCfReeD
9yQWwU6QD2/KxYJBrzRVMwI=
=QDII
-END PGP SIGNATURE-
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net