registry describe Master failed with "error: couldn't reach the IceGrid registry"

in Help Center
Ice Version:
3.5.1
I try to run the following command,
icegridadmin --Ice.Config=/etc/icegridregistry.conf
user id: admin
password:
Ice 3.5.1 Copyright (c) 2003-2013 ZeroC, Inc.
>>> registry list
Master
>>> registry describe Master
error: couldn't reach the IceGrid registry:
Outgoing.cpp:443: Ice::ObjectNotExistException:
object does not exist:
identity: `DemoIceGrid/C54CE694-5A6E-4D51-9344-007DA3CE50CD'
facet:
operation: getRegistryInfo
I can list the Master registry, which means my icegridregistry.conf is right.
But why it is failed on describing?
In my opinion the Object name is a fixed value, but not a uuid.
thx!
3.5.1
I try to run the following command,
icegridadmin --Ice.Config=/etc/icegridregistry.conf
user id: admin
password:
Ice 3.5.1 Copyright (c) 2003-2013 ZeroC, Inc.
>>> registry list
Master
>>> registry describe Master
error: couldn't reach the IceGrid registry:
Outgoing.cpp:443: Ice::ObjectNotExistException:
object does not exist:
identity: `DemoIceGrid/C54CE694-5A6E-4D51-9344-007DA3CE50CD'
facet:
operation: getRegistryInfo
I can list the Master registry, which means my icegridregistry.conf is right.
But why it is failed on describing?
In my opinion the Object name is a fixed value, but not a uuid.
thx!
0
Comments
For some reasons the connection to the IceGrid registry times out when you run the registry describe command. Can you reproduce it with the IceGrid demos? The identity shown in the exception is the identity of the administrative session so the UUID is expected.
You could try running icegridadmin with --Ice.Trace.Network=2 and --Ice.Trace.Protocol=2 and attach the traces in a file here, I will take a look and see if this helps figuring out why the session times out.
Cheers,
Benoit.
The server closed the session, I've set the "IceGrid.Registry.SessionTimeout=300" in icegridregistry.conf.
I just found a workaround by,
Move the "Ice.Default.Locator=DemoIceGrid/Locator:tcp -h 192.168.248.113 -p 4061" to the begining of the icegridregistry.conf file, then restart the icegridregistry service.
Is this a bug?
Can you provide your IceGrid registry configuration file?
Did you try to reproduce the problem with the IceGrid demos by updating the configuration of the demos with a similar configuration?
Cheers,
Benoit.