[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Handle-info] Failure to replicate mirror handle server 7.3.1 from primary handle 6.2.5 server



Robert, 

  I have checked things over and over. I do have the latest distribution of 7.3.1 and attempt to 
use it agains the older handle server 6.2.5.  Here's what I found. 

I can create a mirror handle server with 6.2.5 and then modify its config.dct by adding the following two lines:
   "storage_type" = "BDBJE"
   "db_directory" = "/handle-test/handle/hdl6.2.5_02/1712-mirror/bdbje"
and they bring up this site with the 7.3.1 handle server code. I can query, add and modify handles.

However, when I create a mirror handle server with 7.3.1 by running hdl-sertup-server and try to bring it up 
with 7.3.1 server code, the replication fails with the following error, which is not quite what you see: 

"2013-12-16 15:07:59.929-0600" 25 HANDLE.NET Server Software version 7.3.1
Saving global values to: /home/handletsu/.handle/root_info
Opening Berkeley database in /handle-test/handle/hsj-7.3.1/1712-mirror/bdbje
starting replication thread
"2013-12-16 15:08:00.470-0600" 50 unspecified max_handlers count, using default: 200
"2013-12-16 15:08:00.470-0600" 50 unspecified max_handlers count, using default: 200
"2013-12-16 15:08:00.471-0600" 50 unspecified max_handlers count, using default: 200
"2013-12-16 15:08:00.483-0600" 100 class net.handle.server.HdlUdpInterface: Error setting up server socket: java.net.BindException: Cannot assign requested address
"2013-12-16 15:08:00.483-0600" 100 class net.handle.server.HdlUdpInterface: Error setting up server socket: java.net.BindException: Cannot assign requested address
"2013-12-16 15:08:00.484-0600" 100 class net.handle.server.HdlTcpInterface: Error setting up server socket: java.net.BindException: Cannot assign requested address
"2013-12-16 15:08:00.484-0600" 100 class net.handle.server.HdlTcpInterface: Error setting up server socket: java.net.BindException: Cannot assign requested address
"2013-12-16 15:08:00.511-0600" 100 class net.handle.server.HdlHttpInterface: Error setting up server socket: java.net.BindException: Cannot assign requested address
"2013-12-16 15:08:00.511-0600" 100 class net.handle.server.HdlHttpInterface: Error setting up server socket: java.net.BindException: Cannot assign requested address
"2013-12-16 15:08:00.710-0600" 50 Error doing replication at server: 1 144.92.161.120 (TCP/2645/adm+qry,UDP/2645/qry,HTTP/2646/adm+qry): HandleException (MISSING_OR_INVALID_SIGNATURE) Unable to verify signature for message: version=2.1; oc=1001; rc=402; snId=2 crt caCrt noAuth expires:Tue Dec 17 03:08:00 CST 2013
HandleException (MISSING_OR_INVALID_SIGNATURE) Unable to verify signature for message: version=2.1; oc=1001; rc=402; snId=2 crt caCrt noAuth expires:Tue Dec 17 03:08:00 CST 2013
       at net.handle.hdllib.HandleResolver.verifyResponse(HandleResolver.java:2368)
       at net.handle.hdllib.HandleResolver.sendHttpRequest(HandleResolver.java:3077)
       at net.handle.hdllib.HandleResolver.sendRequestToInterface(HandleResolver.java:2268)
       at net.handle.hdllib.HandleResolver.sendRequestToServerByProtocol(HandleResolver.java:1943)
       at net.handle.hdllib.HandleResolver.sendRequestToServerByProtocol(HandleResolver.java:1818)
       at net.handle.hdllib.HandleResolver.sendRequestToServerInSiteByProtocol(HandleResolver.java:1649)
       at net.handle.hdllib.HandleResolver.sendRequestToServer(HandleResolver.java:1737)
       at net.handle.hdllib.HandleResolver.sendRequestToServer(HandleResolver.java:1688)
       at net.handle.server.replication.ReplicationDaemon.run(ReplicationDaemon.java:435)
Caused by: HandleException (UNKNOWN_ALGORITHM_ID) Unknown signature type: HS_MAC
       at net.handle.hdllib.AbstractMessage.verifyMessage(AbstractMessage.java:503)
       at net.handle.hdllib.HandleResolver.verifyResponse(HandleResolver.java:2362)
       ... 8 more
~                         

I need to migrate the data from 6.2.5 to 7.3.1 since we are  changing the persistence layer to PostgreSQL. 
Please advise on what I could do next to successfully run 7.3.1 mirror against 6.2.5 primary handle server? 

Thank you,
Ev


On Dec 4, 2013, at 10:25 AM, Robert R Tupelo-Schneck <schneck@cnri.reston.va.us> wrote:

I can assure you that the DSA vs DSAwithSHA1 issue was a purely cosmetic issue in the code.  

What's really happening here is that the mirror is initiating a session with the primary, but then can't validate the server's response within that session.  I thought that somehow an incompatibility might have been introduced, but I tried this with a 6.2.5 server and a 7.3.1 server and didn't get the error.

I do not know what is causing your error.  Would you be willing to upgrade your primary to 7.3.1 in order to see if that helps?  This should be as easy as stopping the primary, and then restarting with the 7.3.1 software.  No data migration will occur; it will simply run the 7.3.1 code with the existing data store.

Robert

On 2013-12-03, at 17:46 , Evguenia Krylova <evguenia.krylova@doit.wisc.edu> wrote:

I have a mirror server setup with Handle 7.3.1 against the primary Handle 6.2.5 server.
Followed the instructions to configure the mirror "6.1 Setting up a Single Mirror Handle Server"
from http://www.handle.net/tech_manual/Handle_Tech_Manual_7_v1-1-22Dec10.pdf

The replication fails with the following error:

starting replication thread
"2013-12-03 15:25:14.286-0600" 50 unspecified max_handlers count, using default: 200
"2013-12-03 15:25:14.287-0600" 50 unspecified max_handlers count, using default: 200
"2013-12-03 15:25:14.287-0600" 50 unspecified max_handlers count, using default: 200
"2013-12-03 15:25:14.690-0600" 50 Error doing replication at server: 1 144.92.161.120 (TCP/2645/adm+qry,UDP/2645/qry,HTTP/2646/adm+qry): HandleException (MISSING_OR_INVALID_SIGNATURE) Unable to verify signature for message: version=2.1; oc=1001; rc=402; snId=1 crt caCrt noAuth expires:Wed Dec 04 03:25:14 CST 2013
HandleException (MISSING_OR_INVALID_SIGNATURE) Unable to verify signature for message: version=2.1; oc=1001; rc=402; snId=1 crt caCrt noAuth expires:Wed Dec 04 03:25:14 CST 2013
       at net.handle.hdllib.HandleResolver.verifyResponse(HandleResolver.java:2368)
       at net.handle.hdllib.HandleResolver.sendHttpRequest(HandleResolver.java:3077)
       at net.handle.hdllib.HandleResolver.sendRequestToInterface(HandleResolver.java:2268)
       at net.handle.hdllib.HandleResolver.sendRequestToServerByProtocol(HandleResolver.java:1943)
       at net.handle.hdllib.HandleResolver.sendRequestToServerByProtocol(HandleResolver.java:1818)
       at net.handle.hdllib.HandleResolver.sendRequestToServerInSiteByProtocol(HandleResolver.java:1649)
       at net.handle.hdllib.HandleResolver.sendRequestToServer(HandleResolver.java:1737)
       at net.handle.hdllib.HandleResolver.sendRequestToServer(HandleResolver.java:1688)
       at net.handle.server.replication.ReplicationDaemon.run(ReplicationDaemon.java:435)
Caused by: HandleException (UNKNOWN_ALGORITHM_ID) Unknown signature type: HS_MAC
       at net.handle.hdllib.AbstractMessage.verifyMessage(AbstractMessage.java:503)
       at net.handle.hdllib.HandleResolver.verifyResponse(HandleResolver.java:2362)
       ... 8 more


Has anybody successfully done this?

I suspect that the error might be caused by this change from 7.3 release notes:
"Signature code now uses algorithm DSAwithSHA1 instead of just DSA."
Any ideas how I can force 7.3.1 to use  DSA instead of DSAwithSHA1?

Ev



_______________________________________________
Handle-Info mailing list
Handle-Info@cnri.reston.va.us
http://www.handle.net/mailman/listinfo/handle-info