Support Questions
Find answers, ask questions, and share your expertise

Zeppelin won't start in Docker HDP 2.6.1 install

New Contributor

I've installed HDP 2.6.1 on a Macbook running Docker. Virtually everything seems to be working save Zeppelin. When the UI starts, Zeppelin is not running, and attempting to start it results in the "Starting Zeppelin Notebook" operation stalling at 35%. Not only that, but ambari-server itself seems to get killed (is no longer running after the operation stalls).

Looking thru similar issues from previous HDP versions, I checked a number of things, all of which appear to be Ok.

For example, interpreter.json and the other files that should be present are there:

[root@sandbox ~]# ls -l /etc/zeppelin/2.6.1.0-129/0/

total 80

-rwxr-xr-x 1 zeppelin zeppelin1326 May 31 03:22 configuration.xsl

drwxr-xr-x 1 zeppelin zeppelin4096 Jul 28 14:01 external-dependency-conf

-rwxrwxrwx 1 zeppelin zeppelin 15588 Jul 28 14:21 interpreter.json

-rwxr-xr-x 1 zeppelin zeppelin2729 May 31 03:22 interpreter-list

-rwxr-xr-x 1 zeppelin zeppelin 595 Jul 28 14:01 log4j.properties

-rw-r--r-- 1 zeppelin zeppelin1648 Jul 28 14:01 shiro.ini

-rwxr-xr-x 1 zeppelin zeppelin3847 May 31 03:22 shiro.ini.template

-rwxr-xr-x 1 zeppelin zeppelin5312 May 31 03:22 zeppelin-env.cmd.template

-rwxr-xr-x 1 zeppelin zeppelin5500 Oct7 15:04 zeppelin-env.sh

-rwxr-xr-x 1 zeppelin zeppelin6385 May 31 03:22 zeppelin-env.sh.template

-rw-r--r-- 1 zeppelin zeppelin3355 Jul 28 14:01 zeppelin-site.xml

-rwxr-xr-x 1 zeppelin zeppelin 12188 May 31 03:22 zeppelin-site.xml.template

zeppelin-zeppelin-sandbox.hortonworks.com.log doesn't show any errors:

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 16.0px Menlo; color: #000000; background-color: #929292} span.s1 {font-variant-ligatures: no-common-ligatures}

INFO [2017-10-07 05:47:34,144] ({main} ZeppelinConfiguration.java[create]:101) - Load configuration from file:/etc/zeppelin/2.6.1.0-129/0/zeppelin-site.xml

INFO [2017-10-07 05:47:34,544] ({main} ZeppelinConfiguration.java[create]:109) - Server Host: 0.0.0.0

INFO [2017-10-07 05:47:34,545] ({main} ZeppelinConfiguration.java[create]:111) - Server Port: 9995

INFO [2017-10-07 05:47:34,545] ({main} ZeppelinConfiguration.java[create]:115) - Context Path: /

INFO [2017-10-07 05:47:34,565] ({main} ZeppelinConfiguration.java[create]:116) - Zeppelin Version: 0.7.0.2.6.1.0-129

INFO [2017-10-07 05:47:34,662] ({main} Log.java[initialized]:186) - Logging initialized @9429ms

INFO [2017-10-07 05:47:34,987] ({main} ZeppelinServer.java[setupWebAppContext]:353) - ZeppelinServer Webapp path: /usr/hdp/current/zeppelin-server/webapps

INFO [2017-10-07 05:47:36,432] ({main} ZeppelinServer.java[main]:197) - Starting zeppelin server

INFO [2017-10-07 05:47:36,474] ({main} Server.java[doStart]:327) - jetty-9.2.15.v20160210

INFO [2017-10-07 15:56:47,098] ({main} ZeppelinConfiguration.java[create]:101) - Load configuration from file:/etc/zeppelin/2.6.1.0-129/0/zeppelin-site.xml

INFO [2017-10-07 15:56:47,904] ({main} ZeppelinConfiguration.java[create]:109) - Server Host: 0.0.0.0

INFO [2017-10-07 15:56:47,910] ({main} ZeppelinConfiguration.java[create]:111) - Server Port: 9995

INFO [2017-10-07 15:56:47,910] ({main} ZeppelinConfiguration.java[create]:115) - Context Path: /

INFO [2017-10-07 15:56:47,945] ({main} ZeppelinConfiguration.java[create]:116) - Zeppelin Version: 0.7.0.2.6.1.0-129

INFO [2017-10-07 15:56:48,224] ({main} Log.java[initialized]:186) - Logging initialized @3888ms

INFO [2017-10-07 15:56:48,993] ({main} ZeppelinServer.java[setupWebAppContext]:353) - ZeppelinServer Webapp path: /usr/hdp/current/zeppelin-server/webapps

INFO [2017-10-07 15:56:54,548] ({main} ZeppelinServer.java[main]:197) - Starting zeppelin server

INFO [2017-10-07 15:56:54,572] ({main} Server.java[doStart]:327) - jetty-9.2.15.v20160210

INFO [2017-10-07 16:02:27,582] ({main} ZeppelinConfiguration.java[create]:101) - Load configuration from file:/etc/zeppelin/2.6.1.0-129/0/zeppelin-site.xml

INFO [2017-10-07 16:02:28,394] ({main} ZeppelinConfiguration.java[create]:109) - Server Host: 0.0.0.0

INFO [2017-10-07 16:02:28,403] ({main} ZeppelinConfiguration.java[create]:111) - Server Port: 9995

INFO [2017-10-07 16:02:28,404] ({main} ZeppelinConfiguration.java[create]:115) - Context Path: /

INFO [2017-10-07 16:02:28,520] ({main} ZeppelinConfiguration.java[create]:116) - Zeppelin Version: 0.7.0.2.6.1.0-129

INFO [2017-10-07 16:02:28,974] ({main} Log.java[initialized]:186) - Logging initialized @3726ms

INFO [2017-10-07 16:02:29,464] ({main} ZeppelinServer.java[setupWebAppContext]:353) - ZeppelinServer Webapp path: /usr/hdp/current/zeppelin-server/webapps

INFO [2017-10-07 16:02:32,105] ({main} ZeppelinServer.java[main]:197) - Starting zeppelin server

INFO [2017-10-07 16:02:32,153] ({main} Server.java[doStart]:327) - jetty-9.2.15.v20160210

I do see this error in the ambari log:

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 16.0px Menlo; color: #000000; background-color: #929292} span.s1 {font-variant-ligatures: no-common-ligatures} span.Apple-tab-span {white-space:pre}

07 Oct 2017 15:56:03,943 ERROR [ambari-action-scheduler] ServiceComponentHostImpl:1014 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=ZEPPELIN_MASTER, hostName=sandbox.hortonworks.com, currentState=UNKNOWN, eventType=HOST_SVCCOMP_OP_FAILED, event=EventType: HOST_SVCCOMP_OP_FAILED

07 Oct 2017 15:56:03,947WARN [ambari-action-scheduler] ActionScheduler:938 - Unable to transition to failed state.

org.apache.ambari.server.state.fsm.InvalidStateTransitionException: Invalid event: HOST_SVCCOMP_OP_FAILED at UNKNOWN

at org.apache.ambari.server.state.fsm.StateMachineFactory.doTransition(StateMachineFactory.java:297)

at org.apache.ambari.server.state.fsm.StateMachineFactory.access$300(StateMachineFactory.java:39)

at org.apache.ambari.server.state.fsm.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:440)

at org.apache.ambari.server.state.svccomphost.ServiceComponentHostImpl.handleEvent(ServiceComponentHostImpl.java:1008)

at org.apache.ambari.server.actionmanager.ActionScheduler.transitionToFailedState(ActionScheduler.java:921)

at org.apache.ambari.server.actionmanager.ActionScheduler.processInProgressStage(ActionScheduler.java:801)

at org.apache.ambari.server.actionmanager.ActionScheduler.doWork(ActionScheduler.java:417)

at org.apache.ambari.server.actionmanager.ActionScheduler.run(ActionScheduler.java:310)

at java.lang.Thread.run(Thread.java:748)