I don't think pr868 is the reason. It seems your problem is the network
issue.
Can you do the websocket connection test on
http://www.websocket.org/echo.html and share your result?


2016년 5월 13일 금요일, Sunita Koppar<sunita.kop...@verizondigitalmedia.com>님이
작성한 메시지:

> Appreciate your quick responses. Thanks a lot.
>
> I am trying with this exact combination. Its a CDH 5.7 cluster with Spark
> 1.6
>
> https://github.com/apache/incubator-zeppelin/pull/868 could this be the
> reason?
>
> Any suggestions on how to debug the issue. I dont see any errors anywhere.
>
>
> regards
>
> Sunita
>
> On Thu, May 12, 2016 at 9:00 AM, Hyung Sung Shim <hss...@nflabs.com>
> wrote:
>
>> Since 0.5.5 version, Zeppelin uses single port for REST and websocket so
>> you don't need to care about 8092 port in your case.
>>
>> 2016년 5월 13일 금요일, Sunita Koppar<sunita.kop...@verizondigitalmedia.com>님이
>> 작성한 메시지:
>>
>> Thanks for the response.
>>> Yes there is a firewall but that has been opened for access. The
>>> zeppelin server runs on 8091 and that is open. From the comments, it seems
>>> 8092 needs to be open as well. From firewall perspective 8092 is open as
>>> well (we have requested for a bracket of sockets to be opened which
>>> includes 8092), but I am not sure if zeppelin client opens the websocket
>>> over existing connection or as an independent socket connection from
>>> browser back to server. Pardon my ignorance on the subject.
>>>
>>> Here is the netstat output of the node running the server:
>>>
>>> $ netstat -na |grep 8092
>>> $ netstat -na |grep 8091
>>> tcp        0      0 0.0.0.0:8091            0.0.0.0:*
>>> LISTEN
>>> tcp        0      0 0.0.0.0:18091           0.0.0.0:*
>>> LISTEN
>>> tcp        0      0 10.240.41.55:8091       192.229.234.2:20673
>>> FIN_WAIT2
>>> tcp        0      0 10.240.41.55:8091       192.229.234.2:21277
>>> FIN_WAIT2
>>> tcp        0      0 10.240.41.55:8091       192.229.234.2:42529
>>> ESTABLISHED
>>> tcp        0      0 10.240.41.55:8091       192.229.234.2:27722
>>> FIN_WAIT2
>>> tcp        0      0 10.240.41.55:8091       192.229.234.2:63170
>>> FIN_WAIT2
>>> tcp        0      0 10.240.41.55:8091       192.229.234.2:8542
>>>  FIN_WAIT2
>>> tcp        0      0 10.240.41.55:8091       192.229.234.2:7125
>>>  FIN_WAIT2
>>> tcp        0      1 10.240.41.55:8091       192.229.234.2:16906
>>> FIN_WAIT1
>>>
>>>
>>> zeppelin-site.xml has:
>>>
>>> <property>
>>>   <name>zeppelin.server.port</name>
>>>   <value>8091</value>
>>>   <description>Server port.</description>
>>> </property>
>>>
>>>
>>> regards
>>> Sunita
>>>
>>> On Wed, May 11, 2016 at 8:00 PM, Hyung Sung Shim <hss...@nflabs.com>
>>> wrote:
>>>
>>>> Hello.
>>>>
>>>> Zeppelin uses websocket connection. Do you have some firewall/proxy
>>>> between your browser and zeppelin server daemon? If that does not pass
>>>> websocket connection, start page may show 'Disconnected'.
>>>>
>>>>
>>>> 2016-05-12 4:09 GMT+09:00 Sunita Koppar <
>>>> sunita.kop...@verizondigitalmedia.com>:
>>>>
>>>>> Hello Experts,
>>>>>
>>>>> I am beginning to explore Apache Zeppelin and have set it up on one of
>>>>> our development cluster nodes. The hadoop version is Hadoop 
>>>>> 2.6.0-cdh5.7.0,
>>>>> Spark - 1.6, maven 3.3.9 (Had an error while building one of the
>>>>> dependencies and it mentioned the version should be atleast 3.1.0)
>>>>>
>>>>> I have set the below properties in zeppelin-env.sh
>>>>>
>>>>>
>>>>> *export JAVA_HOME=/home/zeppelin/prerequisites/jdk1.7.0_79*
>>>>> *export MASTER=yarn-client                               # Spark
>>>>> master url. eg. spark://master_addr:7077. Leave empty if you want to use
>>>>> local mode.*
>>>>> *export
>>>>> HADOOP_CONF_DIR=/etc/hadoop/conf.cloudera.yarn:/etc/hive/conf.cloudera.hive*
>>>>> *export
>>>>> HADOOP_HOME=/opt/cloudera/parcels/CDH-5.7.0-1.cdh5.7.0.p0.45/lib/hadoop*
>>>>> *export
>>>>> SPARK_HOME=/opt/cloudera/parcels/CDH-5.7.0-1.cdh5.7.0.p0.45/lib/spark*
>>>>>
>>>>> and built as root with below command:
>>>>>
>>>>> *mvn clean package -Pspark-1.6 -Dhadoop.version=2.6.0-cdh5.7.0
>>>>> -Phadoop-2.6 -Pyarn -DskipTests*
>>>>>
>>>>> Since default port 8080 threw address in use exception (some cloudera
>>>>> services use it I guess), I changed this to 8091.
>>>>>
>>>>> ./bin/zeppelin-daemon.sh start -> works and the server is started,
>>>>> however, there is nothing displayed on the home screen and the status 
>>>>> shows
>>>>> disconnected.
>>>>> There are no errors in the zeppelin-root-xxx.log. Only relevant entry
>>>>> could be (which I am not sure is an issue)
>>>>>
>>>>>
>>>>> *INFO [2016-05-11 18:53:05,910] ({main}
>>>>> StandardDescriptorProcessor.java[visitServlet]:297) - NO JSP Support for 
>>>>> /,
>>>>> did not find org.eclipse.jetty.jsp.JettyJspServlet*
>>>>>
>>>>>
>>>>> The zeppelin-root-xxx.out file shows has the below entry as the latest:
>>>>>
>>>>> *May 11, 2016 6:53:08 PM
>>>>> com.sun.jersey.server.impl.application.WebApplicationImpl _initiate*
>>>>> *INFO: Initiating Jersey application, version 'Jersey: 1.13 06/29/2012
>>>>> 05:14 PM'*
>>>>> *May 11, 2016 6:53:09 PM com.sun.jersey.spi.inject.Errors
>>>>> processErrorMessages*
>>>>> *WARNING: The following warnings have been detected with resource
>>>>> and/or provider classes:*
>>>>> *  WARNING: A HTTP GET method, public javax.ws.rs.core.Response
>>>>> org.apache.zeppelin.rest.InterpreterRestApi.listInterpreter(java.lang.String),
>>>>> should not consume any entity.*
>>>>> *  WARNING: A sub-resource method, public javax.ws.rs.core.Response
>>>>> org.apache.zeppelin.rest.NotebookRestApi.createNote(java.lang.String)
>>>>> throws java.io.IOException, with URI template, "/", is treated as a
>>>>> resource method*
>>>>> *  WARNING: A sub-resource method, public javax.ws.rs.core.Response
>>>>> org.apache.zeppelin.rest.NotebookRestApi.getNotebookList() throws
>>>>> java.io.IOException, with URI template, "/", is treated as a resource
>>>>> method*
>>>>>
>>>>>
>>>>> Appreciate any help in this regard
>>>>>
>>>>> [image: Inline image 1]
>>>>>
>>>>> regards
>>>>> Sunita
>>>>>
>>>>>
>>>>
>>>
>

Reply via email to