Hello - We are trying to install a Node agent in a Java Machine which starts successfully without issues but we see an error in the machine -agent logs: WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
There is no data in the Controller also to view details.
Let us know for any possible solutions.
Regards,
Prem
Hello All,
I saw a similar issue , here is how it was fixed:
Problem: Machine Agent (MA) installed on Windows as a service was not able to connect to AppD SAAS Controller(cSAAS).
Error in MA logFile: WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
Good to know: We had to connect to AppD cSAAS via a proxy.
Troubleshooting:
Initial Steps: Check if the telnet / tracert is working. For us that was working well.
Solution: Add the proxy details in the AppD MA configuration.
How to add proxy details in MA configuration?
Location: MahineAgentHome/Bin/MachineAgentService.vmoptions (If you cannot find this file, create one)
Add below parameter at the start of the file:
-Dappdynamics.http.proxyHost=YourProxyServerName
-Dappdynamics.http.proxyPort=YourProxyPortNumber
Check for more parameters here, click here.
Thanks & Reagrds,
Sahil Gupta
Hi Prem,
Could you please attach the zip file of agent log in debug mode.
Steps to enable debug mode
Goto <machineagent-install-dir>/conf/logging/log4j.xml and change level value to debug from info as show below
Look for
<logger name="com.singularity" additivity="false">
<level value="info"/>
<appender-ref ref="FileAppender"/>
</logger>
and change info to debug as show below
<logger name="com.singularity" additivity="false">
<level value="debug"/>
<appender-ref ref="FileAppender"/>
</logger>
run it for 10 - 15 min and attach the logs.
Thanks,
Atyuha
What is the solution on this issue, as I too am facing the same.
Hi Arun,
Could you please share the log in debug mode.
Thanks,
Atyuha
Hello all,
There are a few other community posts that mention this same error. Please have a look at them to see if they help. I have share two below
Hi @Sathish Kumar.N,
I wanted to check in to see if you were able to read those posts and if they provided any help?
I also experienced the same message on an on - premise environment.
I checked the debug log and it was "CN = localhost".
Because it is different from the host name you are accessing, it seems you can not connect.
So, referring to the following URL, when I rebuilt my self certificate,It worked.
https://docs.appdynamics.com/display/PRO44/Controller+SSL+and+Certificates
1, s1as key delete
2, s1as key regenate
3, restart controller
Hi SK,
I have attached the log files and I can’t get the total directory.
I am trying to configure URL monitoring. So only I have added the application and tier and node name in controller-info.xml file manually.
There is no proxies involved, Kindly find the controller connectivity result .
[appd_mon@ip-10-101-1-29 conf]$ curl -v https://nn-dev.saas.appdynamics.com:443/controller/rest/serverstatus
* About to connect() to nn-dev.saas.appdynamics.com port 443 (#0)
* Trying 35.157.174.134...
* Connected to nn-dev.saas.appdynamics.com (35.157.174.134) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* NSS error -5961 (PR_CONNECT_RESET_ERROR)
* TCP connection reset by peer
* Closing connection 0
curl: (35) TCP connection reset by peer