Archived
This forum has been archived. Please start a new discussion on GitHub.
node is down
hello,
I have a trouble of icepackadmain.
There are three computers:
One is used as the locator(10.0.38.126;Red Hat Enterprise Linux Server release 5.2), one is used as the server(10.0.38.3;Red Hat Enterprise Linux AS release 4 (Nahant Update 6)), and the other is used as the client(10.0.38.2;Red Hat Enterprise Linux AS release 4 (Nahant Update 6)).
The ICE version is 2.1.0.
I want to make a test of the example in the ICE directory"Ice-2.1.0/demo/IcePack/hello"
1, I modified the config in the three computers.
a. In the locator,the config file is modified as follows:
#
# The IcePack locator proxy.
#
Ice.Default.Locator=IcePack/Locator:default -p 12000 -h 10.0.38.126
#
# IcePack registry configuration.
#
IcePack.Registry.Client.Endpoints=default -p 12000 -h 10.0.38.126
IcePack.Registry.Server.Endpoints=default -h 10.0.38.126
IcePack.Registry.Internal.Endpoints=default -h 10.0.38.126
IcePack.Registry.Admin.Endpoints=default -h 10.0.38.126
IcePack.Registry.Data=db/registry
IcePack.Registry.Trace.ServerRegistry=2
IcePack.Registry.Trace.AdapterRegistry=2
#
# IcePack node configuration.
#
IcePack.Node.Name=node
IcePack.Node.Endpoints=default
IcePack.Node.Data=db/node
#IcePack.Node.CollocateRegistry=1
#
# Trace properties.
#
IcePack.Node.Trace.Activator=3
IcePack.Node.Trace.Adapter=2
IcePack.Node.Trace.Server=3
b.In the server, the config file is modified as follows:
#
# The IcePack locator proxy.
#
Ice.Default.Locator=IcePack/Locator:default -p 12000 -h 10.0.38.126
#
# IcePack registry configuration.
#
IcePack.Registry.Client.Endpoints=default -p 12000 -h 10.0.38.126
IcePack.Registry.Server.Endpoints=default -h 10.0.38.126
IcePack.Registry.Internal.Endpoints=default -h 10.0.38.126
IcePack.Registry.Admin.Endpoints=default -h 10.0.38.126
IcePack.Registry.Data=db/registry
IcePack.Registry.Trace.ServerRegistry=2
IcePack.Registry.Trace.AdapterRegistry=2
#
# IcePack node configuration.
#
#IcePack.Node.Name=node
#IcePack.Node.Endpoints=default
#IcePack.Node.Data=db/node
#IcePack.Node.CollocateRegistry=1
#
# Trace properties.
#
#IcePack.Node.Trace.Activator=3
#IcePack.Node.Trace.Adapter=2
#IcePack.Node.Trace.Server=3
c.In the client, the config file is modified as follows:
#
# The IcePack locator proxy.
#
Ice.Default.Locator=IcePack/Locator:default -p 12000 -h 10.0.38.126
#
# IcePack registry configuration.
#
IcePack.Registry.Client.Endpoints=default -p 12000
IcePack.Registry.Server.Endpoints=default
IcePack.Registry.Internal.Endpoints=default
IcePack.Registry.Admin.Endpoints=default
IcePack.Registry.Data=db/registry
IcePack.Registry.Trace.ServerRegistry=2
IcePack.Registry.Trace.AdapterRegistry=2
#
# IcePack node configuration.
#
IcePack.Node.Name=node
IcePack.Node.Endpoints=default
IcePack.Node.Data=db/node
#IcePack.Node.CollocateRegistry=1
#
# Trace properties.
#
IcePack.Node.Trace.Activator=3
IcePack.Node.Trace.Adapter=2
IcePack.Node.Trace.Server=3
2, I run the "icepackregistry --Ice.Config=config" command in the locator, and start the icepackregistry. It can normally run.
3, I run the " icepacknode --Ice.Config=config" command in the server, it seems that the icepacknode runs normally because there are no errors or warnings.
4. I run the "icepackadmin --Ice.Config=config" command in the locator, and I input "node list" in the manage interface, it shows the node name "node", but when I input "node ping 'node' ", the result is "node is down", the detailed result is as follows:
>>> node list
node
>>> node ping 'node'
node is down



How can I solve the problem?
Thank you for your help.
I have a trouble of icepackadmain.
There are three computers:
One is used as the locator(10.0.38.126;Red Hat Enterprise Linux Server release 5.2), one is used as the server(10.0.38.3;Red Hat Enterprise Linux AS release 4 (Nahant Update 6)), and the other is used as the client(10.0.38.2;Red Hat Enterprise Linux AS release 4 (Nahant Update 6)).
The ICE version is 2.1.0.
I want to make a test of the example in the ICE directory"Ice-2.1.0/demo/IcePack/hello"
1, I modified the config in the three computers.
a. In the locator,the config file is modified as follows:
#
# The IcePack locator proxy.
#
Ice.Default.Locator=IcePack/Locator:default -p 12000 -h 10.0.38.126
#
# IcePack registry configuration.
#
IcePack.Registry.Client.Endpoints=default -p 12000 -h 10.0.38.126
IcePack.Registry.Server.Endpoints=default -h 10.0.38.126
IcePack.Registry.Internal.Endpoints=default -h 10.0.38.126
IcePack.Registry.Admin.Endpoints=default -h 10.0.38.126
IcePack.Registry.Data=db/registry
IcePack.Registry.Trace.ServerRegistry=2
IcePack.Registry.Trace.AdapterRegistry=2
#
# IcePack node configuration.
#
IcePack.Node.Name=node
IcePack.Node.Endpoints=default
IcePack.Node.Data=db/node
#IcePack.Node.CollocateRegistry=1
#
# Trace properties.
#
IcePack.Node.Trace.Activator=3
IcePack.Node.Trace.Adapter=2
IcePack.Node.Trace.Server=3
b.In the server, the config file is modified as follows:
#
# The IcePack locator proxy.
#
Ice.Default.Locator=IcePack/Locator:default -p 12000 -h 10.0.38.126
#
# IcePack registry configuration.
#
IcePack.Registry.Client.Endpoints=default -p 12000 -h 10.0.38.126
IcePack.Registry.Server.Endpoints=default -h 10.0.38.126
IcePack.Registry.Internal.Endpoints=default -h 10.0.38.126
IcePack.Registry.Admin.Endpoints=default -h 10.0.38.126
IcePack.Registry.Data=db/registry
IcePack.Registry.Trace.ServerRegistry=2
IcePack.Registry.Trace.AdapterRegistry=2
#
# IcePack node configuration.
#
#IcePack.Node.Name=node
#IcePack.Node.Endpoints=default
#IcePack.Node.Data=db/node
#IcePack.Node.CollocateRegistry=1
#
# Trace properties.
#
#IcePack.Node.Trace.Activator=3
#IcePack.Node.Trace.Adapter=2
#IcePack.Node.Trace.Server=3
c.In the client, the config file is modified as follows:
#
# The IcePack locator proxy.
#
Ice.Default.Locator=IcePack/Locator:default -p 12000 -h 10.0.38.126
#
# IcePack registry configuration.
#
IcePack.Registry.Client.Endpoints=default -p 12000
IcePack.Registry.Server.Endpoints=default
IcePack.Registry.Internal.Endpoints=default
IcePack.Registry.Admin.Endpoints=default
IcePack.Registry.Data=db/registry
IcePack.Registry.Trace.ServerRegistry=2
IcePack.Registry.Trace.AdapterRegistry=2
#
# IcePack node configuration.
#
IcePack.Node.Name=node
IcePack.Node.Endpoints=default
IcePack.Node.Data=db/node
#IcePack.Node.CollocateRegistry=1
#
# Trace properties.
#
IcePack.Node.Trace.Activator=3
IcePack.Node.Trace.Adapter=2
IcePack.Node.Trace.Server=3
2, I run the "icepackregistry --Ice.Config=config" command in the locator, and start the icepackregistry. It can normally run.
3, I run the " icepacknode --Ice.Config=config" command in the server, it seems that the icepacknode runs normally because there are no errors or warnings.
4. I run the "icepackadmin --Ice.Config=config" command in the locator, and I input "node list" in the manage interface, it shows the node name "node", but when I input "node ping 'node' ", the result is "node is down", the detailed result is as follows:
>>> node list
node
>>> node ping 'node'
node is down



How can I solve the problem?
Thank you for your help.
0
Comments
-
See my other post, you should first upgrade to the latest Ice version.
Cheers,
Benoit.0 -
See my other post, you should first upgrade to the latest Ice version.
Cheers,
Benoit.
Actually, I need to use the old OS version, so the relative ICE version should be 2.1.0.
So, when I run the "icepackadmin --Ice.Config=config -e "application
add 'application.xml'" " command, it will show the error as follows:
error: IcePack::DeploymentException:
couldn't contact node `node'
Exception: Network.cpp:545: Ice::ConnectionRefusedException:
connection refused: Connection refused
But when I deploy the test environment in another computers, it runs normally.
It is so strange of the results between the two test environment.
Thank you for help.0 -
SlovedSee my other post, you should first upgrade to the latest Ice version.
Cheers,
Benoit.
Aha,I have already solved the problem!:D
For each computer, it should have another hostname, but not the hostname of "localhost.localhost". It can be changed as follows:
1. modified the file:
/etc/sysconfig/network
HOSTNAME=yourhostname
2. add the three hosts in the file of all the three computers
/etc/hosts
IP yourhost1
IP yourhost2
IP yourhost3
3. run “hostname yourhost” in each terminal
Then,the problem of “node is down” can be solved, it will show "node is up".:cool:0