Re: Knox and Zeppelin UI is not working properly.

2018-08-03 Thread Sandeep Moré 
Nice !

On Fri, Aug 3, 2018 at 1:17 PM Dhruv Goyal <777.dh...@gmail.com> wrote:

> Hi Sandeep,
>
> I figured it was the issue with Zeppelin configuration for authentication,
> it is resolved now, thanks for your inputs.
>
> We had to use :
> /** = authcBasic
> And we were using :
> /** = authc
> In zeppelin shiro
>
>
> Thanks & Regards
> Dhruv Goyal
>
> On 03-Aug-2018, at 10:21 PM, Sandeep Moré  wrote:
>
> never encountered 405
>
>
>

Re: Knox and Zeppelin UI is not working properly.

2018-08-03 Thread Dhruv Goyal 
Hi Sandeep, 

I figured it was the issue with Zeppelin configuration for authentication, it 
is resolved now, thanks for your inputs.

We had to use :
/** = authcBasic
And we were using :
/** = authc
In zeppelin shiro


Thanks & Regards
Dhruv Goyal

> On 03-Aug-2018, at 10:21 PM, Sandeep Moré  wrote:
> 
> never encountered 405

Re: Knox and Zeppelin UI is not working properly.

2018-08-03 Thread Sandeep Moré 
Hello Dhruv,

It appears that the error (405) is coming from Zeppelin, do you see any
errors in Zeppelin log ? can you share zeppelin log and gateway-audit.log
for the above request ?
I have never encountered 405, I tried with Knox 1.1.0 and Zeppelin Version
0.6.0.2.5.0.0-1245 and did not encounter the issue.

is your cluster Kerberized ?

Best,
Sandeep

On Fri, Aug 3, 2018 at 11:41 AM Dhruv Goyal <777.dh...@gmail.com> wrote:

> Hello Sandeep,
>
>
> 1. gateway.websocket.feature.enabled this is set to true in gateway site
> 2. Version of Zeppelin - 0.7.3
>
>
> Gateway Log - This is just a part of it I cannot find any error or issue,
> I can send the complete log if you want:
>
> 2018-08-03 14:41:18,554 DEBUG hadoop.gateway
> (DefaultDispatch.java:executeOutboundRequest(121)) - Dispatch request: GET
> http://platacc002-mst-01.gvs.ggn:9995/api/helium/visualizations/load
> 2018-08-03 14:41:18,554 DEBUG hadoop.gateway
> (UrlRewriteProcessor.java:rewrite(164)) - Rewrote URL:
> https://192.168.134.214:8443/gateway/default/zeppelin/, direction: IN via
> implicit rule: ZEPPELINUI/zeppelin/inbound/root to URL:
> http://platacc002-mst-01.gvs.ggn:9995/
> 2018-08-03 14:41:18,554 DEBUG hadoop.gateway
> (DefaultDispatch.java:executeOutboundRequest(121)) - Dispatch request: GET
> http://platacc002-mst-01.gvs.ggn:9995/app/notebook/notebook.html
> 2018-08-03 14:41:18,558 DEBUG hadoop.gateway
> (DefaultDispatch.java:executeOutboundRequest(134)) - Dispatch response
> status: 302
> 2018-08-03 14:41:18,559 DEBUG hadoop.gateway
> (UrlRewriteProcessor.java:rewrite(164)) - Rewrote URL:
> http://192.168.134.214:8443/api/login;JSESSIONID=02c6810f-00ce-448e-afa8-f87fd50652ed,
> direction: OUT via implicit rule: ZEPPELINUI/zeppelin/outbound/api to URL:
> /gateway/default/zeppelin/api/login;JSESSIONID=02c6810f-00ce-448e-afa8-f87fd50652ed
> 2018-08-03 14:41:18,559 DEBUG hadoop.gateway
> (DefaultDispatch.java:getInboundResponseContentType(209)) - Inbound
> response entity content type not provided.
> 2018-08-03 14:41:18,562 DEBUG hadoop.gateway
> (DefaultDispatch.java:executeOutboundRequest(134)) - Dispatch response
> status: 200
> 2018-08-03 14:41:18,563 DEBUG hadoop.gateway
> (DefaultDispatch.java:getInboundResponseContentType(211)) - Inbound
> response entity content type: text/html
> 2018-08-03 14:41:18,563 DEBUG hadoop.gateway
> (GatewayFilter.java:doFilter(116)) - Received request: GET
> /zeppelin/api/login
> 2018-08-03 14:41:18,564 DEBUG hadoop.gateway
> (UrlRewriteProcessor.java:rewrite(166)) - Rewrote URL:
> https://192.168.134.214:8443/gateway/default/zeppelin/api/login;JSESSIONID=02c6810f-00ce-448e-afa8-f87fd50652ed,
> direction: IN via explicit rule: ZEPPELINUI/zeppelin/inbound/api to URL:
> http://platacc002-mst-01.gvs.ggn:9995/api/login;JSESSIONID=02c6810f-00ce-448e-afa8-f87fd50652ed
> 2018-08-03 14:41:18,564 DEBUG hadoop.gateway
> (UrlRewriteProcessor.java:rewrite(164)) - Rewrote URL:
> https://192.168.134.214:8443/gateway/default/zeppelin/, direction: IN via
> implicit rule: ZEPPELINUI/zeppelin/inbound/root to URL:
> http://platacc002-mst-01.gvs.ggn:9995/
> 2018-08-03 14:41:18,565 DEBUG hadoop.gateway
> (DefaultDispatch.java:executeOutboundRequest(121)) - Dispatch request: GET
> http://platacc002-mst-01.gvs.ggn:9995/api/login;JSESSIONID=02c6810f-00ce-448e-afa8-f87fd50652ed
> 2018-08-03 14:41:18,568 DEBUG hadoop.gateway
> (DefaultDispatch.java:executeOutboundRequest(134)) - Dispatch response
> status: 405
> 2018-08-03 14:41:18,569 DEBUG hadoop.gateway
> (DefaultDispatch.java:getInboundResponseContentType(203)) - Using explicit
> character set ISO-8859-1 for entity of type text/html
> 2018-08-03 14:41:18,569 DEBUG hadoop.gateway
> (DefaultDispatch.java:getInboundResponseContentType(211)) - Inbound
> response entity content type: text/html; charset=ISO-8859-1
>
>
>
> On 03-Aug-2018, at 8:33 PM, Sandeep Moré  wrote:
>
> Hello Dhruv,
> What version of zeppelin are you testing with ? You will need to enable
> websockets or Zeppelin UI to work, make sure you have websocket turned on
> in gateway-site.xml.
>
> Can you share gateway.log failure logs as well so we know where exactly
> Knox is failing.
>
> Best,
> Sandeep
>
> On Fri, Aug 3, 2018 at 10:58 AM Dhruv Goyal <777.dh...@gmail.com> wrote:
>
>> Hi,
>>
>> I am trying to enable Zeppelin with Knox, I have picked the latest
>> changes done in 1.1.0, but I am still facing the issue, when I login to the
>> Knox and then when I provide credentials to login to Zeppelin, it logs out
>> (from zeppelin and not from knox) and ask for credentials again. It makes
>> this calls which throws 405 no such method :
>>
>>
>> https://192.168.134.214:8443/gateway/default/zeppelin/api/login;JSESSIONID=8c7acc28-22c0-4c77-8e1d-b226bbccd8e5
>>
>> However it does work out of the box when I try to access it without Knox,
>> and else the above rest call is not observed when I try to access it
>> without Knox.
>>
>>
>> Regards
>> Dhruv
>
>
>

Re: Knox and Zeppelin UI is not working properly.

2018-08-03 Thread Dhruv Goyal 
Hello Sandeep,


1. gateway.websocket.feature.enabled this is set to true in gateway site 
2. Version of Zeppelin - 0.7.3


Gateway Log - This is just a part of it I cannot find any error or issue, I can 
send the complete log if you want:

2018-08-03 14:41:18,554 DEBUG hadoop.gateway 
(DefaultDispatch.java:executeOutboundRequest(121)) - Dispatch request: GET 
http://platacc002-mst-01.gvs.ggn:9995/api/helium/visualizations/load
2018-08-03 14:41:18,554 DEBUG hadoop.gateway 
(UrlRewriteProcessor.java:rewrite(164)) - Rewrote URL: 
https://192.168.134.214:8443/gateway/default/zeppelin/, direction: IN via 
implicit rule: ZEPPELINUI/zeppelin/inbound/root to URL: 
http://platacc002-mst-01.gvs.ggn:9995/
2018-08-03 14:41:18,554 DEBUG hadoop.gateway 
(DefaultDispatch.java:executeOutboundRequest(121)) - Dispatch request: GET 
http://platacc002-mst-01.gvs.ggn:9995/app/notebook/notebook.html
2018-08-03 14:41:18,558 DEBUG hadoop.gateway 
(DefaultDispatch.java:executeOutboundRequest(134)) - Dispatch response status: 
302
2018-08-03 14:41:18,559 DEBUG hadoop.gateway 
(UrlRewriteProcessor.java:rewrite(164)) - Rewrote URL: 
http://192.168.134.214:8443/api/login;JSESSIONID=02c6810f-00ce-448e-afa8-f87fd50652ed,
 direction: OUT via implicit rule: ZEPPELINUI/zeppelin/outbound/api to URL: 
/gateway/default/zeppelin/api/login;JSESSIONID=02c6810f-00ce-448e-afa8-f87fd50652ed
2018-08-03 14:41:18,559 DEBUG hadoop.gateway 
(DefaultDispatch.java:getInboundResponseContentType(209)) - Inbound response 
entity content type not provided.
2018-08-03 14:41:18,562 DEBUG hadoop.gateway 
(DefaultDispatch.java:executeOutboundRequest(134)) - Dispatch response status: 
200
2018-08-03 14:41:18,563 DEBUG hadoop.gateway 
(DefaultDispatch.java:getInboundResponseContentType(211)) - Inbound response 
entity content type: text/html
2018-08-03 14:41:18,563 DEBUG hadoop.gateway (GatewayFilter.java:doFilter(116)) 
- Received request: GET /zeppelin/api/login
2018-08-03 14:41:18,564 DEBUG hadoop.gateway 
(UrlRewriteProcessor.java:rewrite(166)) - Rewrote URL: 
https://192.168.134.214:8443/gateway/default/zeppelin/api/login;JSESSIONID=02c6810f-00ce-448e-afa8-f87fd50652ed,
 direction: IN via explicit rule: ZEPPELINUI/zeppelin/inbound/api to URL: 
http://platacc002-mst-01.gvs.ggn:9995/api/login;JSESSIONID=02c6810f-00ce-448e-afa8-f87fd50652ed
2018-08-03 14:41:18,564 DEBUG hadoop.gateway 
(UrlRewriteProcessor.java:rewrite(164)) - Rewrote URL: 
https://192.168.134.214:8443/gateway/default/zeppelin/, direction: IN via 
implicit rule: ZEPPELINUI/zeppelin/inbound/root to URL: 
http://platacc002-mst-01.gvs.ggn:9995/
2018-08-03 14:41:18,565 DEBUG hadoop.gateway 
(DefaultDispatch.java:executeOutboundRequest(121)) - Dispatch request: GET 
http://platacc002-mst-01.gvs.ggn:9995/api/login;JSESSIONID=02c6810f-00ce-448e-afa8-f87fd50652ed
2018-08-03 14:41:18,568 DEBUG hadoop.gateway 
(DefaultDispatch.java:executeOutboundRequest(134)) - Dispatch response status: 
405
2018-08-03 14:41:18,569 DEBUG hadoop.gateway 
(DefaultDispatch.java:getInboundResponseContentType(203)) - Using explicit 
character set ISO-8859-1 for entity of type text/html
2018-08-03 14:41:18,569 DEBUG hadoop.gateway 
(DefaultDispatch.java:getInboundResponseContentType(211)) - Inbound response 
entity content type: text/html; charset=ISO-8859-1



> On 03-Aug-2018, at 8:33 PM, Sandeep Moré  wrote:
> 
> Hello Dhruv,
> What version of zeppelin are you testing with ? You will need to enable 
> websockets or Zeppelin UI to work, make sure you have websocket turned on in 
> gateway-site.xml. 
> 
> Can you share gateway.log failure logs as well so we know where exactly Knox 
> is failing.
> 
> Best,
> Sandeep
> 
> On Fri, Aug 3, 2018 at 10:58 AM Dhruv Goyal <777.dh...@gmail.com 
> > wrote:
> Hi,
> 
> I am trying to enable Zeppelin with Knox, I have picked the latest changes 
> done in 1.1.0, but I am still facing the issue, when I login to the Knox and 
> then when I provide credentials to login to Zeppelin, it logs out (from 
> zeppelin and not from knox) and ask for credentials again. It makes this 
> calls which throws 405 no such method :
> 
> https://192.168.134.214:8443/gateway/default/zeppelin/api/login;JSESSIONID=8c7acc28-22c0-4c77-8e1d-b226bbccd8e5
>  
> 
> 
> However it does work out of the box when I try to access it without Knox, and 
> else the above rest call is not observed when I try to access it without 
> Knox. 
> 
> 
> Regards
> Dhruv

Re: Knox and Zeppelin UI is not working properly.

2018-08-03 Thread Sandeep Moré 
Hello Dhruv,
What version of zeppelin are you testing with ? You will need to enable
websockets or Zeppelin UI to work, make sure you have websocket turned on
in gateway-site.xml.

Can you share gateway.log failure logs as well so we know where exactly
Knox is failing.

Best,
Sandeep

On Fri, Aug 3, 2018 at 10:58 AM Dhruv Goyal <777.dh...@gmail.com> wrote:

> Hi,
>
> I am trying to enable Zeppelin with Knox, I have picked the latest changes
> done in 1.1.0, but I am still facing the issue, when I login to the Knox
> and then when I provide credentials to login to Zeppelin, it logs out (from
> zeppelin and not from knox) and ask for credentials again. It makes this
> calls which throws 405 no such method :
>
>
> https://192.168.134.214:8443/gateway/default/zeppelin/api/login;JSESSIONID=8c7acc28-22c0-4c77-8e1d-b226bbccd8e5
>
> However it does work out of the box when I try to access it without Knox,
> and else the above rest call is not observed when I try to access it
> without Knox.
>
>
> Regards
> Dhruv

Knox and Zeppelin UI is not working properly.

2018-08-03 Thread Dhruv Goyal 
Hi,

I am trying to enable Zeppelin with Knox, I have picked the latest changes done 
in 1.1.0, but I am still facing the issue, when I login to the Knox and then 
when I provide credentials to login to Zeppelin, it logs out (from zeppelin and 
not from knox) and ask for credentials again. It makes this calls which throws 
405 no such method :

https://192.168.134.214:8443/gateway/default/zeppelin/api/login;JSESSIONID=8c7acc28-22c0-4c77-8e1d-b226bbccd8e5

However it does work out of the box when I try to access it without Knox, and 
else the above rest call is not observed when I try to access it without Knox. 


Regards
Dhruv