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

Re: [Handle-info] Creating new handles problem



Good.  Note that local_nas and resolver_site are client configuration.  If they exist on the same machine and user account that runs the server, then the server's internal client will use that configuration, which is usually not what you want.  In particular if the prefix handle (0.NA/...) is used for administration, then the server's internal client needs to access the Handle global in order to resolve the authentication information.

Robert

> On Oct 10, 2017, at 8:04 AM, Nicolas Larrousse <nicolas.larrousse@huma-num.fr> wrote:
> 
> Dear Robert,
> 
> Here is a sample of my logs.
> 
> After some tests, it seems that I can bypass the problem by: 
> - getting rid of « local_nas »  and «  resolver_site » in .handle directory
> - recreating the « root_info » file by trying to create a handle
> - restarting the server
> 
> Thanks for your answer.
> 
> Best regards. 
> 
> Nicolas
> 
> "2017-10-09 12:55:19.839+0200" 25 Shutting down server at Mon Oct 09 12:55:19 CEST 2017
> "2017-10-09 12:56:16.074+0200" 25 Started new run.
> "2017-10-09 12:56:16.075+0200" 25 HANDLE.NET Server Software version 7.3
> "2017-10-09 12:56:16.831+0200" 50 Error refreshing root info: HandleException (CANNOT_CONNECT_TO_SERVER) 134.158.33.202: java.net.ConnectException: Connection refused (Connection refused)
> HandleException (CANNOT_CONNECT_TO_SERVER) 134.158.33.202: java.net.ConnectException: Connection refused (Connection refused)
>        at net.handle.hdllib.HandleResolver.sendHttpRequest(HandleResolver.java:2920)
>        at net.handle.hdllib.HandleResolver.sendRequestToInterface(HandleResolver.java:2234)
>        at net.handle.hdllib.HandleResolver.sendRequestToServerByProtocol(HandleResolver.java:1916)
>        at net.handle.hdllib.HandleResolver.sendRequestToServerInSiteByProtocol(HandleResolver.java:1637)
>        at net.handle.hdllib.HandleResolver.sendRequestToSite(HandleResolver.java:1615)
>        at net.handle.hdllib.HappyEyeballsResolver.sendRequestToSiteViaProtocol(HappyEyeballsResolver.java:205)
>        at net.handle.hdllib.HappyEyeballsResolver.sendRequestToSites(HappyEyeballsResolver.java:173)
>        at net.handle.hdllib.HappyEyeballsResolver.sendRequestAndSetResponseOrPublicException(HappyEyeballsResolver.java:151)
>        at net.handle.hdllib.HappyEyeballsResolver.run(HappyEyeballsResolver.java:90)
>        at net.handle.hdllib.HandleResolver.sendRequestToService(HandleResolver.java:1153)
>        at net.handle.hdllib.HandleResolver.processRequest(HandleResolver.java:586)
>        at net.handle.hdllib.HandleResolver.processRequest(HandleResolver.java:603)
>        at net.handle.hdllib.Configuration.refreshRootInfoFromNet(Configuration.java:489)
>        at net.handle.server.AbstractServer$RootInfoUpdater.run(AbstractServer.java:114)
> "2017-10-09 12:56:52.411+0200" 75 class net.handle.server.HdlTcpRequestHandler: Exception processing request: HandleException (INTERNAL_ERROR) Unknown opCode in message: 0
> HandleException (INTERNAL_ERROR) Unknown opCode in message: 0
>        at net.handle.hdllib.Encoder.decodeMessage(Encoder.java:399)
>        at net.handle.server.HdlTcpRequestHandler.run(HdlTcpRequestHandler.java:207)
>        at java.lang.Thread.run(Thread.java:748)
> "2017-10-09 12:58:15.983+0200" 50 Unable to find admin group while creating handle
> "2017-10-09 12:59:07.829+0200" 50 Unable to find admin group while creating handle
> "2017-10-09 13:01:53.334+0200" 75 class net.handle.server.HdlTcpRequestHandler: Exception processing request: java.lang.Exception: Expecting 269 bytes, only received 0
> java.lang.Exception: Expecting 269 bytes, only received 0
>        at net.handle.server.HdlTcpRequestHandler.run(HdlTcpRequestHandler.java:144)
>        at java.lang.Thread.run(Thread.java:748)
> "2017-10-09 13:03:29.199+0200" 50 Unable to find admin group while creating handle
> "2017-10-09 13:06:53.275+0200" 75 class net.handle.server.HdlTcpRequestHandler: Exception processing request: java.lang.Exception: Expecting 269 bytes, only received 0
> java.lang.Exception: Expecting 269 bytes, only received 0
>        at net.handle.server.HdlTcpRequestHandler.run(HdlTcpRequestHandler.java:144)
>        at java.lang.Thread.run(Thread.java:748)
> 
> 
>> Le 10 oct. 2017 à 04:42, Robert R Tupelo-Schneck <schneck@cnri.reston.va.us> a écrit :
>> 
>> Try adding "trace_resolution" = "yes" to the "server_config" section of config.dct, restart the server, and try to create a handle.  Then send me the error.log file.
>> 
>> Robert
>> 
>>> On Oct 9, 2017, at 12:24 PM, Nicolas Larrousse <Nicolas.Larrousse@huma-num.fr> wrote:
>>> 
>>> Dear all,
>>> 
>>> I run a handle server (version 7.3) since 4 years with no problems on a Linux Red-Hat OS.
>>> 
>>> Friday, after a reboot I began to experiment problems creating new handles and I find in the logs this message.
>>> «  Unable to find admin group while creating handle »
>>> 
>>> The handle server is up and running and answer correctly 
>>> hdl.handle.net/11280/1be55432
>>> So I assume that the connection to the MySQL storage is OK and we didn’t modify anything (at least we think that).
>>> 
>>> Do you have an idea of what to check as normally nothing had (or should no have)  changed on this machine. 
>>> 
>>> Thanks in advance.
>>> 
>>> Nicolas Larrousse
>>> _______________________________________________
>>> Handle-Info mailing list
>>> Handle-Info@cnri.reston.va.us
>>> http://www.handle.net/mailman/listinfo/handle-info
>> 
>> _______________________________________________
>> Handle-Info mailing list
>> Handle-Info@cnri.reston.va.us
>> http://www.handle.net/mailman/listinfo/handle-info
> 

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