Archived
This forum has been archived. Please start a new discussion on GitHub.
IceGrid node shutdown fails when registry is down
in Help Center
I'm making use of IceGrid and I notice that if the node that contains the registry is stopped, there is no way to cleaning shutdown the other nodes. I understand that it would be preferrable to shut down all other nodes before the registry; however, the registry may be down for an unexpected reason.
If I attempt to use icegridadmin to shut down a node when the registry is down, I see this:
error: couldn't reach the IceGrid registry:
Network.cpp:669: Ice::ConnectionRefusedException:
connection refused: Connection refused
The only fallback appears to be killing the icegridnode process (and all server processes) on the node. Am I overlooking something? Is there a way to run icegridadmin (locally) on the node that I want to shut down and then shut down cleanly?
Thanks in advance.
If I attempt to use icegridadmin to shut down a node when the registry is down, I see this:
error: couldn't reach the IceGrid registry:
Network.cpp:669: Ice::ConnectionRefusedException:
connection refused: Connection refused
The only fallback appears to be killing the icegridnode process (and all server processes) on the node. Am I overlooking something? Is there a way to run icegridadmin (locally) on the node that I want to shut down and then shut down cleanly?
Thanks in advance.
0
Comments
-
icegridadmin only talks to the IceGrid registry. If the registry is down, the only way to cleanly shutdown a node is to send it CTRL-C or a CTRL-C like signal (such as SIGTERM or SIGINT on Unix/Linux).
Cheers,
Bernard0