question Re: HiveServer2 can't connect to host on HDP sandbox in Archives of Support Questions (Read Only)

HiveServer2 can't connect to host on HDP sandbox

kelson1 — Tue, 12 Sep 2017 00:28:24 GMT

I downloaded the latest HDP sandbox Docker image and haven't made any configuration changes but HiveServer2 wont start up. I followed the instructions here: https://hortonworks.com/tutorial/learning-the-ropes-of-the-hortonworks-sandbox/

The error I'm getting from ambari is:
resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -sS -L -w '%{http_code}' -X GET 'http://sandbox.hortonworks.com:50070/webhdfs/v1/user/hcat?op=GETFILESTATUS&user.name=hdfs' 1>/tmp/tmp8jppwO 2>/tmp/tmplTA4jO' returned 7. curl: (7) couldn't connect to host 000

This is the last error I'm getting from ambari server logs:

[ERROR] [09/11/2017 17:14:37.184] [HiveViewActorSystem-akka.actor.jdbc-connector-dispatcher-7] [akka://HiveViewActorSystem/user/7f19f4e8-f652-43ff-9c60-7a73ba2d4892:syncjdbcConnector] null java.lang.NullPointerException at org.apache.ambari.view.hive2.actor.JdbcConnector.postStop(JdbcConnector.java:611)

The hive logs just say connection refused.

I'm not sure if its a docker issue or something on sandbox. Any help would be appreciated.

Re: HiveServer2 can't connect to host on HDP sandbox

gdeleon — Tue, 12 Sep 2017 05:45:41 GMT

Successfully, I was able to deploy HDP 2.6.1 sandbox (Docker) on MacOS.

Which OS are you using?
Can you please confirm MD5 for your downloaded file is 745d557ba182e401158fff914829cade.

Re: HiveServer2 can't connect to host on HDP sandbox

kelson1 — Tue, 12 Sep 2017 08:17:52 GMT

I fixed the issue, it seems stopping all of the services and then bringing them up one by one seems to fix it. Specifically I started HDFS, Zookeeper, Yarn, MapReduce2, Tez, then finally Hive. Still not sure what the problem was, I'm guessing one of the other services was blocking hive somehow.

Re: HiveServer2 can't connect to host on HDP sandbox

kelson1 — Tue, 12 Sep 2017 08:19:08 GMT

I'm on windows and the MD5 matches. I think we fixed the issue but we had to stop all the services first.