AppD Archive
×

Are you a member of the Splunk Community?

Sign in or Register with your Splunk account to get your questions answered, access valuable resources and connect with experts!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Ask a Question

Unable to connect to SAAS controller

CommunityUser
Splunk Employee
Splunk Employee
‎03-29-2015 01:58 PM

AD Thread-Metric Reporter0] 29 Mar 2015 16:44:40,921 WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.
[AD Thread Pool-Global1] 29 Mar 2015 16:45:00,918 WARN EventHandler - Failed to send events for timeslice [Sun Mar 29 16:41:00 EDT 2015]. The agent will try to resend the events again during the next 1 min window.
[AD Thread Pool-Global1] 29 Mar 2015 16:45:01,395 INFO ControllerTimeSkewHandler - Controller Time Skew Handler Run Aborted - Skew Check is Disabled
[AD Thread Pool-Global1] 29 Mar 2015 16:45:25,959 INFO ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:1071888, Name:appdynamics.ip.addresses, Value:172.30.9.70,fe80:0:0:0:403:ed5:f90d:eb07%11,fe80:0:0:0:0:5efe:ac1e:946%12,fe80:0:0:0:e0:0:0:0%13, Name:supportsDevMode, Value:true]
[AD Thread Pool-Global1] 29 Mar 2015 16:45:25,959 INFO ConfigurationChannel - Sending Registration request with: Application Name [pcs], Tier Name [MyTier], Node Name [igt-nyl-08], Host Name [CID-ACCENTURE08] Node Unique Local ID [igt-nyl-08], Version [Server Agent v4.0.1.0 GA #2015-02-03_10-28-53 r8deac13d7ec074a610054d21bee3bf0ce8e8a2d1 31-4.0.1.next]
[AD Thread-Metric Reporter0] 29 Mar 2015 16:45:40,922 WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.
[AD Thread Pool-Global1] 29 Mar 2015 16:45:47,123 ERROR ConfigurationChannel - Fatal transport error: Connect to newyorklifeinsurance7662.saas.appdynamics.com:443 [newyorklifeinsurance7662.saas.appdynamics.com/69.27.44.162] failed: Connection timed out: connect
[AD Thread Pool-Global1] 29 Mar 2015 16:45:47,123 WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [newyorklifeinsurance7662.saas.appdynamics.com], port[443], exception [Fatal transport error: Connect to newyorklifeinsurance7662.saas.appdynamics.com:443 [newyorklifeinsurance7662.saas.appdynamics.com/69.27.44.162] failed: Connection timed out: connect]
[AD Thread Pool-Global1] 29 Mar 2015 16:45:47,123 WARN AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.singularity.CONFIG.ConfigurationChannel - org.apache.http.conn.HttpHostConnectException,2147483647]
[AD Thread Pool-Global1] 29 Mar 2015 16:45:47,123 WARN AgentErrorProcessor - 0 instance(s) remaining before error log is silenced
[AD Thread Pool-Global1] 29 Mar 2015 16:45:47,123 ERROR ConfigurationChannel - Exception: Connect to newyorklifeinsurance7662.saas.appdynamics.com:443 [newyorklifeinsurance7662.saas.appdynamics.com/69.27.44.162] failed: Connection timed out: connect
org.apache.http.conn.HttpHostConnectException: Connect to newyorklifeinsurance7662.saas.appdynamics.com:443 [newyorklifeinsurance7662.saas.appdynamics.com/69.27.44.162] failed: Connection timed out: connect
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
at com.singularity.ee.util.httpclient.k.a(k.java:209)
at com.singularity.ee.rest.h.G(h.java:376)
at com.singularity.ee.rest.h.F(h.java:328)
at com.singularity.ee.rest.controller.request.sb.F(sb.java:106)
at com.singularity.ee.rest.controller.request.tb.a(tb.java:35)
at com.singularity.ee.agent.appagent.kernel.config.xml.j.a(j.java:1220)
at com.singularity.ee.agent.appagent.kernel.config.xml.j.a(j.java:103)
at com.singularity.ee.agent.appagent.kernel.config.xml.q.a(q.java:587)
at com.singularity.ee.agent.appagent.kernel.config.xml.j.a(j.java:393)
at com.singularity.ee.agent.appagent.kernel.config.xml.bb.run(bb.java:650)
at com.singularity.ee.util.javaspecific.scheduler.n.run(n.java:107)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at com.singularity.ee.util.javaspecific.scheduler.x.e(x.java:322)
at com.singularity.ee.util.javaspecific.scheduler.a.b(a.java:148)
at com.singularity.ee.util.javaspecific.scheduler.b.a(b.java:117)
at com.singularity.ee.util.javaspecific.scheduler.b.b(b.java:204)
at com.singularity.ee.util.javaspecific.scheduler.b.run(b.java:234)
at com.singularity.ee.util.javaspecific.scheduler.i.a(i.java:694)
at com.singularity.ee.util.javaspecific.scheduler.i.run(i.java:726)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at com.singularity.ee.util.httpclient.b.connectSocket(b.java:204)
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:117)
... 28 more

0 Karma
Reply

Arun_Dasetty
Super Champion
‎03-31-2015 05:58 AM

Hi ,

Can you check whether host and port newyorklifeinsurance7662.saas.appdynamics.com 443 are not blocked due to any firewall rules from your network end, we could see the settings in agent config looks fine, but would like to check whether there are any proxy involved between in your network if yes please use the proxy properties as part of jvm args in addition to -javaagent entry added , referred in doc https://docs.appdynamics.com/display/PRO40/Java+Agent+Configuration+Properties#JavaAgentConfiguratio... and see how it goes post jvm restart

Let us know if that information helps. 

Regards,

Arun

0 Karma
Reply

CommunityUser
Splunk Employee
Splunk Employee
‎03-31-2015 08:06 AM

[AD Thread Pool-Global1] 31 Mar 2015 10:34:40,989 INFO ConfigurationChannel - Sending Registration request with: Application Name [pcs], Tier Name [MyTier], Node Name [igt-nyl-08], Host Name [CID-ACCENTURE08] Node Unique Local ID [igt-nyl-08], Version [Server Agent v4.0.1.0 GA #2015-02-03_10-28-53 r8deac13d7ec074a610054d21bee3bf0ce8e8a2d1 31-4.0.1.next]
[AD Thread Pool-Global1] 31 Mar 2015 10:34:41,256 WARN XMLConfigManager - Certificate chain validation failed sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target attempting validation.
[AD Thread Pool-Global1] 31 Mar 2015 10:34:41,256 ERROR ConfigurationChannel - Fatal transport error: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[AD Thread Pool-Global1] 31 Mar 2015 10:34:41,256 WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [newyorklifeinsurance7662.saas.appdynamics.com], port[443], exception [Fatal transport error: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]
[AD Thread Pool-Global1] 31 Mar 2015 10:34:41,257 WARN AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.singularity.CONFIG.ConfigurationChannel - javax.net.ssl.SSLHandshakeException,2147483647]
[AD Thread Pool-Global1] 31 Mar 2015 10:34:41,257 WARN AgentErrorProcessor - 2 instance(s) remaining before error log is silenced
[AD Thread Pool-Global1] 31 Mar 2015 10:34:41,257 ERROR ConfigurationChannel - Exception: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source)
at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)
at sun.security.ssl.Handshaker.processLoop(Unknown Source)
at sun.security.ssl.Handshaker.process_record(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at com.singularity.ee.util.httpclient.b.createLayeredSocket(b.java:185)
at org.apache.http.impl.conn.HttpClientConnectionOperator.upgrade(HttpClientConnectionOperator.java:169)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.upgrade(PoolingHttpClientConnectionManager.java:329)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:398)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
at com.singularity.ee.util.httpclient.k.a(k.java:209)
at com.singularity.ee.rest.h.G(h.java:376)
at com.singularity.ee.rest.h.F(h.java:328)
at com.singularity.ee.rest.controller.request.sb.F(sb.java:106)
at com.singularity.ee.rest.controller.request.tb.a(tb.java:35)
at com.singularity.ee.agent.appagent.kernel.config.xml.j.a(j.java:1220)
at com.singularity.ee.agent.appagent.kernel.config.xml.j.a(j.java:103)
at com.singularity.ee.agent.appagent.kernel.config.xml.q.a(q.java:587)
at com.singularity.ee.agent.appagent.kernel.config.xml.j.a(j.java:393)
at com.singularity.ee.agent.appagent.kernel.config.xml.bb.run(bb.java:650)
at com.singularity.ee.util.javaspecific.scheduler.n.run(n.java:107)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at com.singularity.ee.util.javaspecific.scheduler.x.e(x.java:322)
at com.singularity.ee.util.javaspecific.scheduler.a.b(a.java:148)
at com.singularity.ee.util.javaspecific.scheduler.b.a(b.java:117)
at com.singularity.ee.util.javaspecific.scheduler.b.b(b.java:204)
at com.singularity.ee.util.javaspecific.scheduler.b.run(b.java:234)
at com.singularity.ee.util.javaspecific.scheduler.i.a(i.java:694)
at com.singularity.ee.util.javaspecific.scheduler.i.run(i.java:726)
at java.lang.Thread.run(Unknown Source)
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.validator.PKIXValidator.doBuild(Unknown Source)
at sun.security.validator.PKIXValidator.engineValidate(Unknown Source)
at sun.security.validator.Validator.validate(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
at com.singularity.ee.util.httpclient.d.checkServerTrusted(d.java:220)
at sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(Unknown Source)
... 38 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown Source)
at java.security.cert.CertPathBuilder.build(Unknown Source)
... 46 more

0 Karma
Reply

Arun_Dasetty
Super Champion
‎04-01-2015 01:21 AM

Hi,

Can you please import the attached certificates to your truststore and see if that errors in agent logs occurs still?

https://docs.appdynamics.com/display/OTHER/FAQ+on+SSL+Certificate+Change#FAQonSSLCertificateChange-I...

https://docs.appdynamics.com/display/PRO39/Controller+SSL+and+Certificates

Keep  us posted how it goes after making changes suggested and server is restarted.

Regards,

Arun

digicert.int.cer
digicert.root.cer
0 Karma
Reply

CommunityUser
Splunk Employee
Splunk Employee
‎04-01-2015 06:47 PM

Hello Arun,

could import digicert.int.cer, however while importing digicert.root.cer gets error 

keytool error: java.lang.Exception: Certificate not imported, alias <mykey> already exists

Attached are the logs

Thanks for all the help

0 Karma
Reply
Get Updates on the Splunk Community!

September Community Champions: A Shoutout to Our Contributors!

As we close the books on another fantastic month, we want to take a moment to celebrate the people who are the ...

Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps

It’s Monday morning, and your phone is buzzing with alert escalations – your customer-facing portal is running ...

What’s New in Splunk Observability – September 2025

What's NewWe are excited to announce the latest enhancements to Splunk Observability, designed to help ITOps ...