Restarting a Node

For large deployments, you might need to change the configuration of a Node frequently and then restart the Node to make sure the changes are reflected in the Administrator. Using this option, you can easily apply all the changes related to the Node.

Note: “SystemNode” (Administrator Node) cannot be restarted for security reasons.

Pre-requisites

  • The Node must be running.

GUI

Using the GUI, you can restart a single or multiple Nodes under the same environment.

  1. Navigate to Infrastructure > Nodes.
  2. In the Nodes list, select one or more Nodes.
  3. Click Restart.

On a successful restart, the Node State displays as "Running".

CLI

Using the CLI, you can restart a single or multiple Nodes under the same or different environments.

The data.xml file is identical to that shown for start action.

Example of build.xml

<target name="restart">
		<AMXAdminTask
			action="restart"
			objectSelector="Environment/Node"
			remote="true"
			propsFile="${instanceProperties}"
			dataFile="${dataFile}"
			failOnError="false"/>
</target>

Example of restart action using CLI

Command: 

D:\installation\data\admin\amxadmin\samples> ant -f node_build.xml restart

Sample output: 

Buildfile: D:\installation\\data\admin\amxadmin\samples\node_build.xml

restart:
[AMXAdminTask] 30 Jun 2017 20:43:36  INFO - Initializing JSSE's crypto provider class com.sun.net.ssl.internal.ssl.Provider in default mode
[AMXAdminTask] 30 Jun 2017 20:43:36  INFO - Connecting to AMX Admin server at 'http://kavalask-w540:8120' as user 'root'.
[AMXAdminTask] 30 Jun 2017 20:43:36  INFO - Executing action 'restart' for 1 objects from data file 'D:\installation\\data\admin\amxadmin\samples\node_data.xml'
[AMXAdminTask] 30 Jun 2017 20:43:37  INFO - Restarting Node 'node1' in background
[AMXAdminTask] 30 Jun 2017 20:43:37  INFO - Action finished in Admin at 30/6/17 8:43 PM in 0.063 seconds. Waiting for runtime tasks to be finished. Action tracked in log(s) by action-id [root:Node-Restart:30]
[AMXAdminTask] 30 Jun 2017 20:43:38  INFO - .
[AMXAdminTask] 30 Jun 2017 20:43:42  INFO - .
[AMXAdminTask] 30 Jun 2017 20:43:47  INFO - Node Restart finished successfully
[AMXAdminTask] 30 Jun 2017 20:43:47  INFO - Action finished at 30/6/17 8:43 PM in 9.442 seconds

BUILD SUCCESSFUL
Total time: 13 seconds

What to Expect After Restarting a Node

  • During this process, the Action History displays as "Restart (In Progress)" .
  • On successful restart, the Node state displays as "Running" and Action History displays "Restart Successful".
  • On a failure to start or register, the Node state displays as "Stopped" if it fails after stop action otherwise it displays its previous state and Action History displays as "Restart Failed". The SystemNode.log on the remote machine provides more information for restart errors.