Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

After upgraded Ambari from 1.7 to 2.1.1 then started receiving timeline metrics cannot connect collector socket errors

Solved Go to solution
Highlighted

After upgraded Ambari from 1.7 to 2.1.1 then started receiving timeline metrics cannot connect collector socket errors

Contributor

From ambari-server 2 log:

28 Sep 2015 19:04:23,498 ERROR [qtp-client-6858] MetricsPropertyProvider:183 - Error getting timeline metrics. Can not connect to collector, socket error. 
28 Sep 2015 19:04:28,989 INFO [AlertNoticeDispatchService] AlertNoticeDispatchService:279 - There are 1 pending alert notices about to be dispatched... 
28 Sep 2015 19:04:28,993 INFO [alert-dispatch-96] EmailDispatcher:88 - Sending email: org.apache.ambari.server.state.alert.AlertNotification@35b0f886 
28 Sep 2015 19:04:29,245 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:154 - Heartbeat lost from host blpd813-priv.bhdc.att.com 
28 Sep 2015 19:04:33,519 ERROR [qtp-client-6858] MetricsReportPropertyProvider:223 - Error getting timeline metrics. Can not connect to collector, socket error. 

From the ambari-alerts log:

2015-09-28 18:34:01,981 [CRITICAL] [YARN] [yarn_nodemanager_webui] (NodeManager Web UI) Connection failed to http://blpd852-priv.bhdc.att.com:8042 (<urlopen error timed out>) 
2015-09-28 18:34:03,088 [CRITICAL] [YARN] [yarn_nodemanager_webui] (NodeManager Web UI) Connection failed to http://blpd820-priv.bhdc.att.com:8042 (<urlopen error timed out>) 
2015-09-28 18:34:52,711 [OK] [YARN] [yarn_nodemanager_webui] (NodeManager Web UI) HTTP 200 response in 0.000s 
2015-09-28 18:34:53,709 [OK] [YARN] [yarn_nodemanager_webui] (NodeManager Web UI) HTTP 200 response in 0.000s 
2015-09-28 19:04:05,354 [CRITICAL] [YARN] [yarn_nodemanager_webui] (NodeManager Web UI) Connection failed to http://blpd810-priv.bhdc.att.com:8042 (<urlopen error timed out>) 
2015-09-28 19:04:56,024 [OK] [YARN] [yarn_nodemanager_webui] (NodeManager Web UI) HTTP 200 response in 0.000s
1 ACCEPTED SOLUTION

Accepted Solutions

Re: After upgraded Ambari from 1.7 to 2.1.1 then started receiving timeline metrics cannot connect collector socket errors

Contributor
7 REPLIES 7

Re: After upgraded Ambari from 1.7 to 2.1.1 then started receiving timeline metrics cannot connect collector socket errors

Is Ambari Metrics service up?

Re: After upgraded Ambari from 1.7 to 2.1.1 then started receiving timeline metrics cannot connect collector socket errors

Is AMS configured in embedded or distributed mode?

Re: After upgraded Ambari from 1.7 to 2.1.1 then started receiving timeline metrics cannot connect collector socket errors

Contributor

I don't know if it is setup in distributed or embedded mode, but I will check on that and if metrics services are up and update you.

Re: After upgraded Ambari from 1.7 to 2.1.1 then started receiving timeline metrics cannot connect collector socket errors

Contributor

they are running in embedded mode and ams is up and running

Re: After upgraded Ambari from 1.7 to 2.1.1 then started receiving timeline metrics cannot connect collector socket errors

Can you create an EAR for this an attach the Ambari Metrics Collector logs?

Re: After upgraded Ambari from 1.7 to 2.1.1 then started receiving timeline metrics cannot connect collector socket errors

Expert Contributor

Re: After upgraded Ambari from 1.7 to 2.1.1 then started receiving timeline metrics cannot connect collector socket errors

Contributor
Don't have an account?
Coming from Hortonworks? Activate your account here