Getting ERROR [Timer-Driven Process Thread-8] o.a.n.r.ambari.AmbariReportingTask in nifi log

[#1]

my nifi log file filled by following error and I am not able to run twitter example process because of that. So can some please help me to get it done. Thanks in advance.

2016-07-05 07:46:42,822 ERROR [Timer-Driven Process Thread-7] o.a.n.r.ambari.AmbariReportingTask AmbariReportingTask[id=3b80ba0f-a6c0-48db-b721-4dbc04cef28e] Error running task AmbariReportingTask[id=3b80ba0f-a6c0-48db-b721-4dbc04cef28e] due to javax.ws.rs.ProcessingException: java.net.ConnectException: Connection refused

2016-07-05 07:47:42,827 ERROR [Timer-Driven Process Thread-4] o.a.n.r.ambari.AmbariReportingTask AmbariReportingTask[id=3b80ba0f-a6c0-48db-b721-4dbc04cef28e] Error running task AmbariReportingTask[id=3b80ba0f-a6c0-48db-b721-4dbc04cef28e] due to javax.ws.rs.ProcessingException: java.net.ConnectException: Connection refused

[#2]

Hi @Saurabh Kumar,

Can you please confirm that you can see your Nifi UI at:

Step1:

http://127.0.0.1:9090/nifi/ or http://sandbox.hortonworks.com:9090/nifi/

If not, please ensure that port forwarding is applied as http://hortonworks.com/hadoop-tutorial/how-to-refine-and-visualize-sentiment-data/

Step2:

Can you make sure you created the app and access token, access secret, consumer key and consumer secret keys are all correct.

Sep3:

In case of installation issue, please follow these steps to add Nifi service.

https://community.hortonworks.com/articles/1282/sample-hdfnifi-flow-to-push-tweets-into-solrbanana.h...

Hope this help.

Please let me know in case of issues.

Thanks,

Sujitha

[#3]

Yes @sujitha sanku. Nifi was running fine and I have create twitter id as well.

Actually there was a firewall problem, now I am able to run it through my personal internet.

Thanks for your response.

[#4 · Accepted solution]

The error you provided is saying that the AmbariReportingTask you have running can not connect to the Ambari Metrics Collector. This error will not prevent anything in your flow from working and should have no effect on getting a Twitter example working, it will only stop metrics from going to Ambari.

Please verify the Ambari Metrics Collector is running at the host and port specified on the reporting task in the Metrics Collector URL property, the default value is http://localhost:6188/ws/v1/timeline/metrics

[#5]

@Bryan Bende: Thanks a lot for your reply. Yes as you mentioned ambari Metrics Collector will not create any problem in given workflow.

Actually I was not able to run my workflow because of firewall restriction in our org.