Products | Versions |
---|---|
Spotfire Server | 7.5 and higher |
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
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]]
config list-addresses
config list-addresses
server.name=company.global.com