Archived
Glacier2 cannot reach PermissionVerfier on server
Is it a configuration issue on the Glacier2 instance? Do I need to have a permanent connection to the backend server set via the ACM (Ice.Glacier2.ACM.Server.Close=0)?
Thanks in advance
Comments
-
Hi Janos,
You don't need a persistent connection with the permission verifier. The best way to diagnostic this is to enable network and protocol tracing in Glacier2 router. You can add the following lines to your Glacier2 router configuration to enable tracing:
Ice.Trace.Network=3 Ice.Trace.Protocol=1
Can you also specify what Ice version are you using?
0 -
Hi xdm,
Here's the error log (suprisingly printed via the Ice.StdOut property) from the Glacier2 instance (
Ice.Warn.Connections=3
):-! 04/07/17 18:54:30.976 Test.Glacier2: warning: unable to contact permissions verifier `Test.CPermissionVerifier@Test-Backends' Reference.cpp:1637: Ice::NoEndpointException: no suitable endpoint available for proxy `Test.CPermissionVerifier -t -e 1.1 @ Test-Backends' -! 04/07/17 18:54:30.981 Test.Glacier2: warning: unable to contact session manager `Test.CSessionManager@Test-Backends' Reference.cpp:1637: Ice::NoEndpointException: no suitable endpoint available for proxy `Test.CSessionManager -t -e 1.1 @ Test-Backends'
Unfortunately the Ice.StdErr and Ice.StdOut properties were not enabled at the time and I cannot reproduce the problem myself. I enabled logging on the router, when it happens again during the week, I will post further details.
I thought the server checked out and removed it's endpoints, but I had no information in the server logs.Does this help you any further?
0 -
For some reason IceGrid returns empty endpoints for the permission verifier/session manager.
Can you enable additional trace for IceGrid:
IceGrid.Registry.Trace.Locator=1
And Glacier2:
Ice.Trace.Locator=1
0