agent offline at boot server
search cancel

agent offline at boot server

book

Article ID: 131730

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)

Issue/Introduction

When we boot a server the service nolio agent start automatically process is up
  
root 1686 1684 3 09:31 ? 00:00:06 ./jre/bin/NolioAgent -Djava.ext.dirs=./jre/lib/ext:./lib:./libNoUpgrade:./lib/ext:./lib/db -Duser.country=US -Duser.language=en -Djava.library.path=./lib:./bin -classpath ./lib/wrapper.jar -Dwrapper.key=**********-Dwrapper.port=32001 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.disable_console_input=TRUE -Dwrapper.pid=1684 -Dwrapper.version=3.5.6-st
but when we try to deploy the agent is offline in log we have this error 
2019-04-29 09:31:22,833 [WrapperSimpleAppMain] DEBUG (com.nolio.platform.shared.communication.CommunicationNetwork:56) - establishing Communication Network connection... 2019-04-29 09:31:27,337 [WrapperSimpleAppMain] ERROR (com.nolio.platform.agent.DeployerLifecycle:506) - failed to start agent java.lang.Error: this node is not configured with supernode address - without it a node can not function.

but when when start again the service work

Environment

CA Release Automation (CA RA): 6.6.0.10059
Operating system: Red Hat Enterprise 6.3 or others

Cause

From logs it is evident that supernode for this agent for some reason is not getting resolved from the agent server. 

Snippet from nimi.log  

2019-04-29 09:31:27,336 [WrapperSimpleAppMain] ERROR (com.nolio.nimi.keepalive.impl.KeepAliveManagerImpl:141) - Bad supernode address [test.test:6600] - unknown host 
2019-04-29 09:31:27,337 [WrapperSimpleAppMain] ERROR (com.nolio.nimi.keepalive.impl.KeepAliveManagerImpl:141) - Bad supernode address [test.test:6600] - unknown host 
2019-04-29 09:31:27,337 [WrapperSimpleAppMain] ERROR (com.nolio.nimi.keepalive.impl.KeepAliveManagerImpl:101) - this node is not configured with supernode address - without it a node can not function.

This may be the reason why this agent fails to execute an action. 

Trouble shooting:
1: Can you please see if from agent server you are able to ping the supernode via IP/ HOSTNAME/ FQDN
2: Replace the entry which is getting resolved in nimi_config.xml of agent under section <supernodes>....</supernode> and restart agent service 
 

Resolution

Replace the DNS by IP in nimi_config.xml file of agent and restarted the service
Powered by Wolken Software