You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@zeppelin.apache.org by Hyung Sung Shim <hs...@nflabs.com> on 2016/04/04 13:03:00 UTC
Re: Zeppelin 0.5.6 Disconnected
Hello.
Since 0.5.5, Zeppelin uses single port for REST and websocket.
so Could you try to use same port like follow Nginx configuration?
server {
listen 80 ;
server_name _;
location / {
proxy_set_header Host $host;
proxy_set_header X-Real-IP $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
proxy_pass http://backend;
}
location /ws {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header X-Real-IP $remote_addr;
proxy_pass http://backendWS <http://backendws/>;
}
}
I am fixing the documentation.
Thanks.
2016-04-04 17:24 GMT+09:00 Oren Shani <os...@iucc.ac.il>:
> Hello,
>
>
>
> I installed Zeppelin 0.5.6 on Ubuntu server 14.04, behind Nginx. Zeppelin
> comes up but shows "Disconnected" in the top right corner.
>
>
>
> I found several references to a similar problem on the web and most of
> them suggest that the problem has to do with access to Zeppelin's winsock
> port (8081).
>
>
>
> The thing is that Zeppelin on my server does not listen on 8081 but only
> on 8080. Also I ran pcap on both the server side and my PC's side and never
> saw an attempt to access port 8081 .
>
>
>
> So could it be something else? Maybe I am missing something in my config
> files?
>
>
>
> You can see my zeppelin-site.xml and the relevant lines from my nginx
> config files attached.
>
>
>
> Many thanks,
>
>
>
> Oren
>
>
>
>
>
RE: Zeppelin 0.5.6 Disconnected
Posted by Oren Shani <os...@iucc.ac.il>.
Hello,
Yes it works now.
And I understand that this:
https://issues.apache.org/jira/browse/ZEPPELIN-173
Is no longer a concern, right?
Many thanks,
Oren
From: astroshim@gmail.com [mailto:astroshim@gmail.com] On Behalf Of Hyung Sung Shim
Sent: Tuesday, April 5, 2016 6:56 AM
To: users@zeppelin.incubator.apache.org
Subject: Re: Zeppelin 0.5.6 Disconnected
Hello.
I just did test same with your environment and I got success working.
All your configuration seems good except the "zeppelin.server.allowed.origins" config.
Can you try to set the "zeppelin.server.allowed.origins" value to "*" like the following?
# conf/zeppelin-site.xml
<property>
<name>zeppelin.server.allowed.origins</name>
<value>*</value>
<description>Allowed sources for REST and WebSocket requests (i.e. http://onehost:8080,http://otherhost.com). If you leave * yo
</property>
Please share me know the result.
Thanks.
2016-04-05 1:34 GMT+09:00 Hyung Sung Shim <hs...@nflabs.com>>:
Hello.
I think the "Disconnected" problem is the websocket connection problem.
The "zeppelin.ssl.keystore.path" should be under "~/$ZEPPELIN_HOME/conf/" path.
If it's still not working, can you send the zeppelin log files that is under the "~/$ZEPPELIN_HOME/logs" ?
Thanks.
2016-04-05 0:05 GMT+09:00 Oren Shani <os...@iucc.ac.il>>:
Hi,
Nginx should be configured OK now, but still disconnected.
Could it be something else? For example, did I have to install Spark and/or Hadoop?
Oren
From: astroshim@gmail.com<ma...@gmail.com> [mailto:astroshim@gmail.com<ma...@gmail.com>] On Behalf Of Hyung Sung Shim
Sent: Monday, April 4, 2016 5:17 PM
To: users@zeppelin.incubator.apache.org<ma...@zeppelin.incubator.apache.org>
Subject: Re: Zeppelin 0.5.6 Disconnected
hi.
You could refer to https://github.com/apache/incubator-zeppelin/pull/814.
I just tested on Ubuntu 14.04.3 and it's working well.
Thanks.
2016-04-04 21:08 GMT+09:00 Oren Shani <os...@iucc.ac.il>>:
Sung Shim,
I wasn't sure what http://backend and http://backendWS should refer to so I defined both as upstream to localhost:8080
Also when I defined the following:
proxy_set_header X-Real-IP $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
Nginx complained that it doesn't know the variable proxy_protocol_addr so I omitted these lines.
So now I have the attached nginx config but it doesn't seem to help – Zeppelin is still disconnected
Thanks for your help,
Oren
From: astroshim@gmail.com<ma...@gmail.com> [mailto:astroshim@gmail.com<ma...@gmail.com>] On Behalf Of Hyung Sung Shim
Sent: Monday, April 4, 2016 2:03 PM
To: users@zeppelin.incubator.apache.org<ma...@zeppelin.incubator.apache.org>
Subject: Re: Zeppelin 0.5.6 Disconnected
Hello.
Since 0.5.5, Zeppelin uses single port for REST and websocket.
so Could you try to use same port like follow Nginx configuration?
server {
listen 80 ;
server_name _;
location / {
proxy_set_header Host $host;
proxy_set_header X-Real-IP $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
proxy_pass http://backend<http://backend/>;
}
location /ws {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header X-Real-IP $remote_addr;
proxy_pass http://backendWS<http://backendws/>;
}
}
I am fixing the documentation.
Thanks.
2016-04-04 17:24 GMT+09:00 Oren Shani <os...@iucc.ac.il>>:
Hello,
I installed Zeppelin 0.5.6 on Ubuntu server 14.04, behind Nginx. Zeppelin comes up but shows "Disconnected" in the top right corner.
I found several references to a similar problem on the web and most of them suggest that the problem has to do with access to Zeppelin's winsock port (8081).
The thing is that Zeppelin on my server does not listen on 8081 but only on 8080. Also I ran pcap on both the server side and my PC's side and never saw an attempt to access port 8081 .
So could it be something else? Maybe I am missing something in my config files?
You can see my zeppelin-site.xml and the relevant lines from my nginx config files attached.
Many thanks,
Oren
Re: Zeppelin 0.5.6 Disconnected
Posted by Hyung Sung Shim <hs...@nflabs.com>.
Hello.
I just did test same with your environment and I got success working.
All your configuration seems good except the
"zeppelin.server.allowed.origins" config.
Can you try to set the "zeppelin.server.allowed.origins" value to "*" like
the following?
*# conf/zeppelin-site.xml*
*<property>*
* <name>zeppelin.server.allowed.origins</name>*
* <value>*</value>*
* <description>Allowed sources for REST and WebSocket requests (i.e.
http://onehost:8080 <http://onehost:8080>,http://otherhost.com
<http://otherhost.com>). If you leave * yo*
*</property>*
Please share me know the result.
Thanks.
2016-04-05 1:34 GMT+09:00 Hyung Sung Shim <hs...@nflabs.com>:
> Hello.
> I think the "Disconnected" problem is the websocket connection problem.
>
> The *"zeppelin.ssl.keystore.path"* should be under
> "~/$ZEPPELIN_HOME/conf/" path.
>
> If it's still not working, can you send the zeppelin log files that is
> under the "~/$ZEPPELIN_HOME/logs" ?
>
> Thanks.
>
>
> 2016-04-05 0:05 GMT+09:00 Oren Shani <os...@iucc.ac.il>:
>
>> Hi,
>>
>>
>>
>> Nginx should be configured OK now, but still disconnected.
>>
>>
>>
>> Could it be something else? For example, did I have to install Spark
>> and/or Hadoop?
>>
>>
>>
>> Oren
>>
>>
>>
>> *From:* astroshim@gmail.com [mailto:astroshim@gmail.com] *On Behalf Of *Hyung
>> Sung Shim
>> *Sent:* Monday, April 4, 2016 5:17 PM
>>
>> *To:* users@zeppelin.incubator.apache.org
>> *Subject:* Re: Zeppelin 0.5.6 Disconnected
>>
>>
>>
>> hi.
>>
>> You could refer to https://github.com/apache/incubator-zeppelin/pull/814.
>>
>> I just tested on Ubuntu 14.04.3 and it's working well.
>>
>> Thanks.
>>
>>
>>
>>
>>
>> 2016-04-04 21:08 GMT+09:00 Oren Shani <os...@iucc.ac.il>:
>>
>> Sung Shim,
>>
>>
>>
>>
>>
>> I wasn't sure what http://backend and http://backendWS should refer to
>> so I defined both as upstream to localhost:8080
>>
>>
>>
>> Also when I defined the following:
>>
>>
>>
>> proxy_set_header X-Real-IP $proxy_protocol_addr;
>>
>> proxy_set_header X-Forwarded-For $proxy_protocol_addr;
>>
>>
>>
>>
>>
>> Nginx complained that it doesn't know the variable proxy_protocol_addr so
>> I omitted these lines.
>>
>>
>>
>> So now I have the attached nginx config but it doesn't seem to help –
>> Zeppelin is still disconnected
>>
>>
>>
>> Thanks for your help,
>>
>>
>>
>> Oren
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From:* astroshim@gmail.com [mailto:astroshim@gmail.com] *On Behalf Of *Hyung
>> Sung Shim
>> *Sent:* Monday, April 4, 2016 2:03 PM
>> *To:* users@zeppelin.incubator.apache.org
>> *Subject:* Re: Zeppelin 0.5.6 Disconnected
>>
>>
>>
>> Hello.
>>
>> Since 0.5.5, Zeppelin uses single port for REST and websocket.
>>
>> so Could you try to use same port like follow Nginx configuration?
>>
>>
>>
>> server {
>>
>> listen 80 ;
>>
>> server_name _;
>>
>>
>>
>> location / {
>>
>> proxy_set_header Host $host;
>>
>> proxy_set_header X-Real-IP $proxy_protocol_addr;
>>
>> proxy_set_header X-Forwarded-For $proxy_protocol_addr;
>>
>>
>>
>> proxy_pass http://backend;
>>
>> }
>>
>>
>>
>> location /ws {
>>
>> proxy_http_version 1.1;
>>
>> proxy_set_header Upgrade $http_upgrade;
>>
>> proxy_set_header Connection "upgrade";
>>
>>
>>
>> proxy_set_header X-Real-IP $remote_addr;
>>
>> proxy_pass http://backendWS <http://backendws/>;
>>
>> }
>>
>> }
>>
>>
>>
>> I am fixing the documentation.
>>
>> Thanks.
>>
>>
>>
>>
>>
>> 2016-04-04 17:24 GMT+09:00 Oren Shani <os...@iucc.ac.il>:
>>
>> Hello,
>>
>>
>>
>> I installed Zeppelin 0.5.6 on Ubuntu server 14.04, behind Nginx. Zeppelin
>> comes up but shows "Disconnected" in the top right corner.
>>
>>
>>
>> I found several references to a similar problem on the web and most of
>> them suggest that the problem has to do with access to Zeppelin's winsock
>> port (8081).
>>
>>
>>
>> The thing is that Zeppelin on my server does not listen on 8081 but only
>> on 8080. Also I ran pcap on both the server side and my PC's side and never
>> saw an attempt to access port 8081 .
>>
>>
>>
>> So could it be something else? Maybe I am missing something in my config
>> files?
>>
>>
>>
>> You can see my zeppelin-site.xml and the relevant lines from my nginx
>> config files attached.
>>
>>
>>
>> Many thanks,
>>
>>
>>
>> Oren
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
Re: Zeppelin 0.5.6 Disconnected
Posted by Hyung Sung Shim <hs...@nflabs.com>.
Hello.
I think the "Disconnected" problem is the websocket connection problem.
The *"zeppelin.ssl.keystore.path"* should be under "~/$ZEPPELIN_HOME/conf/"
path.
If it's still not working, can you send the zeppelin log files that is
under the "~/$ZEPPELIN_HOME/logs" ?
Thanks.
2016-04-05 0:05 GMT+09:00 Oren Shani <os...@iucc.ac.il>:
> Hi,
>
>
>
> Nginx should be configured OK now, but still disconnected.
>
>
>
> Could it be something else? For example, did I have to install Spark
> and/or Hadoop?
>
>
>
> Oren
>
>
>
> *From:* astroshim@gmail.com [mailto:astroshim@gmail.com] *On Behalf Of *Hyung
> Sung Shim
> *Sent:* Monday, April 4, 2016 5:17 PM
>
> *To:* users@zeppelin.incubator.apache.org
> *Subject:* Re: Zeppelin 0.5.6 Disconnected
>
>
>
> hi.
>
> You could refer to https://github.com/apache/incubator-zeppelin/pull/814.
>
> I just tested on Ubuntu 14.04.3 and it's working well.
>
> Thanks.
>
>
>
>
>
> 2016-04-04 21:08 GMT+09:00 Oren Shani <os...@iucc.ac.il>:
>
> Sung Shim,
>
>
>
>
>
> I wasn't sure what http://backend and http://backendWS should refer to
> so I defined both as upstream to localhost:8080
>
>
>
> Also when I defined the following:
>
>
>
> proxy_set_header X-Real-IP $proxy_protocol_addr;
>
> proxy_set_header X-Forwarded-For $proxy_protocol_addr;
>
>
>
>
>
> Nginx complained that it doesn't know the variable proxy_protocol_addr so
> I omitted these lines.
>
>
>
> So now I have the attached nginx config but it doesn't seem to help –
> Zeppelin is still disconnected
>
>
>
> Thanks for your help,
>
>
>
> Oren
>
>
>
>
>
>
>
>
>
> *From:* astroshim@gmail.com [mailto:astroshim@gmail.com] *On Behalf Of *Hyung
> Sung Shim
> *Sent:* Monday, April 4, 2016 2:03 PM
> *To:* users@zeppelin.incubator.apache.org
> *Subject:* Re: Zeppelin 0.5.6 Disconnected
>
>
>
> Hello.
>
> Since 0.5.5, Zeppelin uses single port for REST and websocket.
>
> so Could you try to use same port like follow Nginx configuration?
>
>
>
> server {
>
> listen 80 ;
>
> server_name _;
>
>
>
> location / {
>
> proxy_set_header Host $host;
>
> proxy_set_header X-Real-IP $proxy_protocol_addr;
>
> proxy_set_header X-Forwarded-For $proxy_protocol_addr;
>
>
>
> proxy_pass http://backend;
>
> }
>
>
>
> location /ws {
>
> proxy_http_version 1.1;
>
> proxy_set_header Upgrade $http_upgrade;
>
> proxy_set_header Connection "upgrade";
>
>
>
> proxy_set_header X-Real-IP $remote_addr;
>
> proxy_pass http://backendWS <http://backendws/>;
>
> }
>
> }
>
>
>
> I am fixing the documentation.
>
> Thanks.
>
>
>
>
>
> 2016-04-04 17:24 GMT+09:00 Oren Shani <os...@iucc.ac.il>:
>
> Hello,
>
>
>
> I installed Zeppelin 0.5.6 on Ubuntu server 14.04, behind Nginx. Zeppelin
> comes up but shows "Disconnected" in the top right corner.
>
>
>
> I found several references to a similar problem on the web and most of
> them suggest that the problem has to do with access to Zeppelin's winsock
> port (8081).
>
>
>
> The thing is that Zeppelin on my server does not listen on 8081 but only
> on 8080. Also I ran pcap on both the server side and my PC's side and never
> saw an attempt to access port 8081 .
>
>
>
> So could it be something else? Maybe I am missing something in my config
> files?
>
>
>
> You can see my zeppelin-site.xml and the relevant lines from my nginx
> config files attached.
>
>
>
> Many thanks,
>
>
>
> Oren
>
>
>
>
>
>
>
>
>
RE: Zeppelin 0.5.6 Disconnected
Posted by Oren Shani <os...@iucc.ac.il>.
Hi,
Nginx should be configured OK now, but still disconnected.
Could it be something else? For example, did I have to install Spark and/or Hadoop?
Oren
From: astroshim@gmail.com [mailto:astroshim@gmail.com] On Behalf Of Hyung Sung Shim
Sent: Monday, April 4, 2016 5:17 PM
To: users@zeppelin.incubator.apache.org
Subject: Re: Zeppelin 0.5.6 Disconnected
hi.
You could refer to https://github.com/apache/incubator-zeppelin/pull/814.
I just tested on Ubuntu 14.04.3 and it's working well.
Thanks.
2016-04-04 21:08 GMT+09:00 Oren Shani <os...@iucc.ac.il>>:
Sung Shim,
I wasn't sure what http://backend and http://backendWS should refer to so I defined both as upstream to localhost:8080
Also when I defined the following:
proxy_set_header X-Real-IP $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
Nginx complained that it doesn't know the variable proxy_protocol_addr so I omitted these lines.
So now I have the attached nginx config but it doesn't seem to help – Zeppelin is still disconnected
Thanks for your help,
Oren
From: astroshim@gmail.com<ma...@gmail.com> [mailto:astroshim@gmail.com<ma...@gmail.com>] On Behalf Of Hyung Sung Shim
Sent: Monday, April 4, 2016 2:03 PM
To: users@zeppelin.incubator.apache.org<ma...@zeppelin.incubator.apache.org>
Subject: Re: Zeppelin 0.5.6 Disconnected
Hello.
Since 0.5.5, Zeppelin uses single port for REST and websocket.
so Could you try to use same port like follow Nginx configuration?
server {
listen 80 ;
server_name _;
location / {
proxy_set_header Host $host;
proxy_set_header X-Real-IP $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
proxy_pass http://backend<http://backend/>;
}
location /ws {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header X-Real-IP $remote_addr;
proxy_pass http://backendWS<http://backendws/>;
}
}
I am fixing the documentation.
Thanks.
2016-04-04 17:24 GMT+09:00 Oren Shani <os...@iucc.ac.il>>:
Hello,
I installed Zeppelin 0.5.6 on Ubuntu server 14.04, behind Nginx. Zeppelin comes up but shows "Disconnected" in the top right corner.
I found several references to a similar problem on the web and most of them suggest that the problem has to do with access to Zeppelin's winsock port (8081).
The thing is that Zeppelin on my server does not listen on 8081 but only on 8080. Also I ran pcap on both the server side and my PC's side and never saw an attempt to access port 8081 .
So could it be something else? Maybe I am missing something in my config files?
You can see my zeppelin-site.xml and the relevant lines from my nginx config files attached.
Many thanks,
Oren
Re: Zeppelin 0.5.6 Disconnected
Posted by Hyung Sung Shim <hs...@nflabs.com>.
hi.
You could refer to https://github.com/apache/incubator-zeppelin/pull/814.
I just tested on Ubuntu 14.04.3 and it's working well.
Thanks.
2016-04-04 21:08 GMT+09:00 Oren Shani <os...@iucc.ac.il>:
> Sung Shim,
>
>
>
>
>
> I wasn't sure what http://backend and http://backendWS should refer to
> so I defined both as upstream to localhost:8080
>
>
>
> Also when I defined the following:
>
>
>
> proxy_set_header X-Real-IP $proxy_protocol_addr;
>
> proxy_set_header X-Forwarded-For $proxy_protocol_addr;
>
>
>
>
>
> Nginx complained that it doesn't know the variable proxy_protocol_addr so
> I omitted these lines.
>
>
>
> So now I have the attached nginx config but it doesn't seem to help –
> Zeppelin is still disconnected
>
>
>
> Thanks for your help,
>
>
>
> Oren
>
>
>
>
>
>
>
>
>
> *From:* astroshim@gmail.com [mailto:astroshim@gmail.com] *On Behalf Of *Hyung
> Sung Shim
> *Sent:* Monday, April 4, 2016 2:03 PM
> *To:* users@zeppelin.incubator.apache.org
> *Subject:* Re: Zeppelin 0.5.6 Disconnected
>
>
>
> Hello.
>
> Since 0.5.5, Zeppelin uses single port for REST and websocket.
>
> so Could you try to use same port like follow Nginx configuration?
>
>
>
> server {
>
> listen 80 ;
>
> server_name _;
>
>
>
> location / {
>
> proxy_set_header Host $host;
>
> proxy_set_header X-Real-IP $proxy_protocol_addr;
>
> proxy_set_header X-Forwarded-For $proxy_protocol_addr;
>
>
>
> proxy_pass http://backend;
>
> }
>
>
>
> location /ws {
>
> proxy_http_version 1.1;
>
> proxy_set_header Upgrade $http_upgrade;
>
> proxy_set_header Connection "upgrade";
>
>
>
> proxy_set_header X-Real-IP $remote_addr;
>
> proxy_pass http://backendWS <http://backendws/>;
>
> }
>
> }
>
>
>
> I am fixing the documentation.
>
> Thanks.
>
>
>
>
>
> 2016-04-04 17:24 GMT+09:00 Oren Shani <os...@iucc.ac.il>:
>
> Hello,
>
>
>
> I installed Zeppelin 0.5.6 on Ubuntu server 14.04, behind Nginx. Zeppelin
> comes up but shows "Disconnected" in the top right corner.
>
>
>
> I found several references to a similar problem on the web and most of
> them suggest that the problem has to do with access to Zeppelin's winsock
> port (8081).
>
>
>
> The thing is that Zeppelin on my server does not listen on 8081 but only
> on 8080. Also I ran pcap on both the server side and my PC's side and never
> saw an attempt to access port 8081 .
>
>
>
> So could it be something else? Maybe I am missing something in my config
> files?
>
>
>
> You can see my zeppelin-site.xml and the relevant lines from my nginx
> config files attached.
>
>
>
> Many thanks,
>
>
>
> Oren
>
>
>
>
>
>
>
RE: Zeppelin 0.5.6 Disconnected
Posted by Oren Shani <os...@iucc.ac.il>.
Sung Shim,
I wasn't sure what http://backend and http://backendWS should refer to so I defined both as upstream to localhost:8080
Also when I defined the following:
proxy_set_header X-Real-IP $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
Nginx complained that it doesn't know the variable proxy_protocol_addr so I omitted these lines.
So now I have the attached nginx config but it doesn't seem to help – Zeppelin is still disconnected
Thanks for your help,
Oren
From: astroshim@gmail.com [mailto:astroshim@gmail.com] On Behalf Of Hyung Sung Shim
Sent: Monday, April 4, 2016 2:03 PM
To: users@zeppelin.incubator.apache.org
Subject: Re: Zeppelin 0.5.6 Disconnected
Hello.
Since 0.5.5, Zeppelin uses single port for REST and websocket.
so Could you try to use same port like follow Nginx configuration?
server {
listen 80 ;
server_name _;
location / {
proxy_set_header Host $host;
proxy_set_header X-Real-IP $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
proxy_pass http://backend<http://backend/>;
}
location /ws {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header X-Real-IP $remote_addr;
proxy_pass http://backendWS<http://backendws/>;
}
}
I am fixing the documentation.
Thanks.
2016-04-04 17:24 GMT+09:00 Oren Shani <os...@iucc.ac.il>>:
Hello,
I installed Zeppelin 0.5.6 on Ubuntu server 14.04, behind Nginx. Zeppelin comes up but shows "Disconnected" in the top right corner.
I found several references to a similar problem on the web and most of them suggest that the problem has to do with access to Zeppelin's winsock port (8081).
The thing is that Zeppelin on my server does not listen on 8081 but only on 8080. Also I ran pcap on both the server side and my PC's side and never saw an attempt to access port 8081 .
So could it be something else? Maybe I am missing something in my config files?
You can see my zeppelin-site.xml and the relevant lines from my nginx config files attached.
Many thanks,
Oren