How to "fix" greyed out Node that won't start up

How to "fix" greyed out Node that won't start up

Sometimes after trusting a node you may notice that it stays greyed out and never actually starts. This may happen during a fresh installation or when migrating an existing installation to a new machine. You may see a messages like the following:

nm.log

WARN 2017-09-18T08:55:39,822+0200 [] nodemanager.service.WorkerhostServiceManager: 
Attempt to tell service 6856dc6b-7f27-4abc-8a43-cd1b00908dea to shutdown failed due to I/O error on GET request for "https://GOT-GMARCHUL-20.gslab.local:9501/6856dc6b-7f27-4abc-8a43-cd1b00908dea/managementService/StopService":
 Connect to GOT-GMARCHUL-20.gslab.local:9501 [GOT-GMARCHUL-20.gslab.local/10.100.41.107, GOT-GMARCHUL-20.gslab.local/fe80:0:0:0:dded:699a:b2d7:8f4%11] failed:
 Connection refused: connect; nested exception is org.apache.http.conn.HttpHostConnectException:
 Connect to GOT-GMARCHUL-20.gslab.local:9501 [GOT-GMARCHUL-20.gslab.local/10.100.41.107, GOT-GMARCHUL-20.gslab.local/fe80:0:0:0:dded:699a:b2d7:8f4%11] failed: Connection refused: connect

server.log

WARN 2017-09-18T08:55:25,795+0200 [heartbeat-31] server.http.HttpCallable: 
Failed to send HeartBeatCommand request to 'https://GOT-GMARCHUL-20.gslab.local:9443/spotfire/nodemanager/command' : 
Connect to GOT-GMARCHUL-20.gslab.local:9443 [GOT-GMARCHUL-20.gslab.local/10.100.41.107] failed: Connection refused: connect

 

WARN 2017-09-18T15:00:07,095+0200 [heartbeat-17032] control.communicator.HttpMonitor: Could not contact the remote. Message: 
ControlCommand [controlCommandType=HEART_BEAT, eventDataType=TERMINAL_COMMAND, anticipatedSteps=1, guid=4793026e-3b7d-4033-8fce-7d0a6cdff9ad, node=Node [serverId=8a837bcb-032d-4fc9-ab6a-8cf8f7281fea, serverName=got-gmarchul--0.gslab.local, port=9443, online=true, siteID=5c2c7b84-e1f4-4187-9799-85a2a48f0ebc]]

The reason is that you are trying to reach the Spotfire Server on a correct address, but this address was not listed under the addresses while creating the bootstrap.xml file.

Example:

Your Spotfire Server IP is 10.100.x.x and FQDN is company.global.com. Both are accessible but you only listed company.global.com when creating bootstrap.xml Then while installing Node Manager you specified the IP as server address. When the installation is complete, Node Manager will show up under Untrusted Nodes because it was trying to reach the correct address (IP) and you can trust it, but it will remain greyed out because it is not aware of the address where the Spotfire Server is registered. Unless you want to recreate a bootstrap.xml file and list all addresses you can apply one of the two solutions:

Option 1:

1). Run

config list-addresses

on the Spotfire Server machine and note down one of the addresses

2). Reinstall the Node Manager and provide one of the listed addresses from Step 1.


Option 2:

1). Run

config list-addresses

on the Spotfire Server machine and note down one of the addresses.

2). Open the <NM installation/nm/config/nodemanager.properties> file, find 'server.name=' and replace the existing value with one of the addresses listed in the previous step. For example:

server.name=company.global.com

If you had any Web Player and/or Automation Services instances, the second option will keep them intact.

Restart the Node Manager service.