When upgrading I made a complete copy of my 1.5.1 folder and continued
installing 1.6.2.
While configuring (and afterward) I made sure that my configuration
files are similar.
When attempting to start the handle server for 1.6.2 it doesn't work.
But the idea came to me last night to use the previous version's handle
server as a test.
So this morning I ran the start handle-server script from my 1.5.1
backup directory - and everything works fine!
The server starts up fine and the hdl.handle.net/ links resolve without
problems, so it doesn't seem to be a problem on the server
(ports/paths/etc..) - in my mind it still points to the 1.6.2 script.
For the time being I will keep it running like this, although I realize
this is not at all ideal (I assume logging isn't working right now), but
the downtime really makes the institution look bad.
Don't know if anyone has any ideas but I'm open to suggestions.
Vrywaringsklousule / Disclaimer:
http://www.nwu.ac.za/it/gov-man/disclaimer.html
Vrywaringsklousule / Disclaimer:
http://www.nwu.ac.za/it/gov-man/disclaimer.html
>>> On 27 September 2010 at 04:52 PM, "Heh, Gregory"
<[email protected]> wrote:
Louw,
I'm not sure about any bugs within the Windows version of the 1.6.1
startup script. Posting this question on the dspace-tech list will
help. Do a file search within the dspace install directory for the
handle-server.log. Sands Alden Fish had a good idea about disabling any
firewall momentarily to rule out a network issue. Just don't give up
checking the log files and working with CNRI and your network team to
find the issue.
Greg
From:Louw Venter [mailto:[email protected]]
Sent: Monday, September 27, 2010 10:36 AM
To: Heh, Gregory
Subject: RE: [Dspace-tech] Handle server on 1.6.2 (Windows)
Greg
Thank you for the response, I appreciate it.
It is the same machine, so nothing changed there. I changed Tomcat to
use those ports temporarily as a test and could connect, so am quite
sure the ports are open and nothing else is using them.
The CNRI answer was that they can't connect to our server, so they
thought the ports were being blocked by some other process, when in fact
the handle server just doesn't start up..
I also think because the server doesn't start up successfully a log
file (other than error.log) isn't created (well, couldn't find one
anyway).
I am scared it might be a problem with the startup script for Windows
specifically as, from what I've read, the script was buggy in version
1.6.1 so it was fixed for linux systems but not Win.
Vrywaringsklousule / Disclaimer:
http://www.nwu.ac.za/it/gov-man/disclaimer.html
>>> On 27 September 2010 at 04:13 PM, "Heh, Gregory"
<[email protected]> wrote:
Louw,
I've had similar issues and errors when trying to configure the handle
server. Granted I was installing on a RHEL 5 virtual server but I think
the general installation instructions remain the same.
· Make sure all necessary ports are open for the appropriate
communication
o port 2641 UDP (input and output)
o port 2641 TCP (input and output)
o port 8000 TCP (input and output)
o These are the default ports but you can choose others, just make
sure that there are no other processes running on these ports as the
handle service needs dedicated ports.
· Double check your handle configurations in dspace.cfg and
/[dspace]/handle-server/config.dct
· Talk with your contact from CNRI, they can help you if the
configuration isn't correct.
Also what is the output from handle-server.log after you run the
/[dspace]/bin/ start-handle-server script? My apologies if anything is
different for a Windows machine.
Greg
From:Louw Venter [mailto:[email protected]]
Sent: Monday, September 27, 2010 9:36 AM
To: [email protected]
Subject: [Dspace-tech] Handle server on 1.6.2 (Windows)
Good day all
Since upgrading (1.5.1 - 1.6.2) last week I've been trying to start the
Handle-server without success.
Has anyone been able to successfully upgrade on the Windows platform
with a working handle server?
The ports are still open and I've changed all the necessary
configuration files as far as I know, but the server does not start.
In the odd occurrence that it does start half-way, it freezes and does
not communicate.
Below is the contents of the error.log after three attempts.
Any help/advice would be greatly appreciated.
Regards
Louw Venter
"2010/09/27 03:28:29 GMT+02:00" 25 Started new run.
"2010/09/27 03:28:29 GMT+02:00" 50 unspecified max_handlers count,
using default: 200
"2010/09/27 03:28:29 GMT+02:00" 50 unspecified max_handlers count,
using default: 200
"2010/09/27 03:28:29 GMT+02:00" 50 unspecified max_handlers count,
using default: 200
"2010/09/27 03:28:29 GMT+02:00" 25 Shutting down server at Mon Sep 27
15:28:29 GMT+02:00 2010
"2010/09/27 03:28:29 GMT+02:00" 75 class
net.handle.server.HdlUdpInterface: Error handling request:
java.net.SocketException: socket closed
java.net.SocketException: socket closed
"2010/09/27 03:28:29 GMT+02:00" 75 class
net.handle.server.HdlTcpInterface: Error handling request:
java.net.SocketException: socket closed
at java.net.TwoStacksPlainDatagramSocketImpl.receive0(Native Method)
at
java.net.TwoStacksPlainDatagramSocketImpl.receive(TwoStacksPlainDatagramSocketImpl.java:84)
at java.net.DatagramSocket.receive(DatagramSocket.java:739)
at
net.handle.server.HdlUdpInterface.serveRequests(HdlUdpInterface.java:156)
at net.handle.server.NetworkInterface.run(NetworkInterface.java:150)
at java.lang.Thread.run(Thread.java:717)
java.net.SocketException: socket closed
at java.net.TwoStacksPlainSocketImpl.socketAccept(Native Method)
at
java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:375)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:179)
at java.net.ServerSocket.implAccept(ServerSocket.java:513)
at java.net.ServerSocket.accept(ServerSocket.java:481)
at
net.handle.server.HdlTcpInterface.serveRequests(HdlTcpInterface.java:155)
at net.handle.server.NetworkInterface.run(NetworkInterface.java:150)
at java.lang.Thread.run(Thread.java:717)
"2010/09/27 03:28:45 GMT+02:00" 25 Started new run.
"2010/09/27 03:28:45 GMT+02:00" 50 unspecified max_handlers count,
using default: 200
"2010/09/27 03:28:45 GMT+02:00" 50 unspecified max_handlers count,
using default: 200
"2010/09/27 03:28:45 GMT+02:00" 50 unspecified max_handlers count,
using default: 200
"2010/09/27 03:28:45 GMT+02:00" 25 Shutting down server at Mon Sep 27
15:28:45 GMT+02:00 2010
"2010/09/27 03:28:45 GMT+02:00" 75 class
net.handle.server.HdlUdpInterface: Error handling request:
java.net.SocketException: socket closed
java.net.SocketException: socket closed
at java.net.TwoStacksPlainDatagramSocketImpl.receive0(Native Method)
at
java.net.TwoStacksPlainDatagramSocketImpl.receive(TwoStacksPlainDatagramSocketImpl.java:84)
at java.net.DatagramSocket.receive(DatagramSocket.java:739)
at
net.handle.server.HdlUdpInterface.serveRequests(HdlUdpInterface.java:156)
at net.handle.server.NetworkInterface.run(NetworkInterface.java:150)
at java.lang.Thread.run(Thread.java:717)
"2010/09/27 03:28:45 GMT+02:00" 75 class
net.handle.server.HdlTcpInterface: Error handling request:
java.net.SocketException: socket closed
java.net.SocketException: socket closed
at java.net.TwoStacksPlainSocketImpl.socketAccept(Native Method)
at
java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:375)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:179)
at java.net.ServerSocket.implAccept(ServerSocket.java:513)
at java.net.ServerSocket.accept(ServerSocket.java:481)
at
net.handle.server.HdlTcpInterface.serveRequests(HdlTcpInterface.java:155)
at net.handle.server.NetworkInterface.run(NetworkInterface.java:150)
at java.lang.Thread.run(Thread.java:717)
"2010/09/27 03:29:06 GMT+02:00" 25 Started new run.
"2010/09/27 03:29:06 GMT+02:00" 50 unspecified max_handlers count,
using default: 200
"2010/09/27 03:29:06 GMT+02:00" 50 unspecified max_handlers count,
using default: 200
"2010/09/27 03:29:06 GMT+02:00" 50 unspecified max_handlers count,
using default: 200
"2010/09/27 03:29:06 GMT+02:00" 25 Shutting down server at Mon Sep 27
15:29:06 GMT+02:00 2010
Vrywaringsklousule / Disclaimer:
http://www.nwu.ac.za/it/gov-man/disclaimer.html
This email message and any files transmitted with it are intended only
for the use of the individual or entity to which it is addressed and may
contain information that is privileged, confidential, and exempt from
disclosure under applicable law. Any use, distribution, copying or
disclosure by anyone other than the intended individual or entity is
prohibited without prior approval. If you have received this
information in error, please notify the sender immediately.
This email message and any files transmitted with it are intended only
for the use of the individual or entity to which it is addressed and may
contain information that is privileged, confidential, and exempt from
disclosure under applicable law. Any use, distribution, copying or
disclosure by anyone other than the intended individual or entity is
prohibited without prior approval. If you have received this information
in error, please notify the sender immediately.
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
