You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@knox.apache.org by Roshan Punnoose <ro...@gmail.com> on 2014/05/13 20:06:55 UTC

Port 443

Has anyone had any success using a port forwarder (like xinetd) to forward
443 to knox gateway 8443?

I keep getting this exception:

2014-05-13 17:41:13,976 ERROR hadoop.gateway
(GatewayServlet.java:service(122)) - Failed to execute filter:
javax.servlet.ServletException:
org.apache.shiro.subject.ExecutionException:
java.security.PrivilegedActionException: javax.servlet.ServletException:
java.lang.NullPointerException

My initial thought is that the knox url rewriting mechanism is expecting
the port '8443' to exist?

Roshan

Re: Port 443

Posted by Roshan Punnoose <ro...@gmail.com>.

Thanks! I have updated the ticket.


On Wed, May 14, 2014 at 1:58 PM, Kevin Minder
<ke...@hortonworks.com>wrote:

>  Hi Roshan,
>
> I can't think of anything where the port number is used in the rewriting
> rules.
>
> We have done testing with load balancers (e.g.
> ApacheHTTPD+mod_proxy+mod_proxy_balancer but not with a port forwarder.
>
> I've created a jira
> NPE when using xinetd for port forwarding to Knox
> https://issues.apache.org/jira/browse/KNOX-365
>
> Can you please:
> 1) modify <GATEWAY_HOME>/conf/gateway-log4j.properties and change
> log4j.logger.org.apache.hadoop.gateway to DEBUG
> 2) restart the server
> 3) reproduce the issue
> 4) zip up the content of <GATEWAY_HOME>/logs and attach it to the jira
>
> Kevin.
>
>
> On 5/13/14 2:06 PM, Roshan Punnoose wrote:
>
> Has anyone had any success using a port forwarder (like xinetd) to forward
> 443 to knox gateway 8443?
>
>  I keep getting this exception:
>
>  2014-05-13 17:41:13,976 ERROR hadoop.gateway
> (GatewayServlet.java:service(122)) - Failed to execute filter:
> javax.servlet.ServletException:
> org.apache.shiro.subject.ExecutionException:
> java.security.PrivilegedActionException: javax.servlet.ServletException:
> java.lang.NullPointerException
>
>  My initial thought is that the knox url rewriting mechanism is expecting
> the port '8443' to exist?
>
>  Roshan
>
>
>
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

Re: Port 443

Posted by Kevin Minder <ke...@hortonworks.com>.

Hi Roshan,

I can't think of anything where the port number is used in the rewriting 
rules.

We have done testing with load balancers (e.g. 
ApacheHTTPD+mod_proxy+mod_proxy_balancer but not with a port forwarder.

I've created a jira
NPE when using xinetd for port forwarding to Knox
https://issues.apache.org/jira/browse/KNOX-365

Can you please:
1) modify <GATEWAY_HOME>/conf/gateway-log4j.properties and change 
log4j.logger.org.apache.hadoop.gateway to DEBUG
2) restart the server
3) reproduce the issue
4) zip up the content of <GATEWAY_HOME>/logs and attach it to the jira

Kevin.

On 5/13/14 2:06 PM, Roshan Punnoose wrote:
> Has anyone had any success using a port forwarder (like xinetd) to 
> forward 443 to knox gateway 8443?
>
> I keep getting this exception:
>
> 2014-05-13 17:41:13,976 ERROR hadoop.gateway 
> (GatewayServlet.java:service(122)) - Failed to execute filter: 
> javax.servlet.ServletException: 
> org.apache.shiro.subject.ExecutionException: 
> java.security.PrivilegedActionException: 
> javax.servlet.ServletException: java.lang.NullPointerException
>
> My initial thought is that the knox url rewriting mechanism is 
> expecting the port '8443' to exist?
>
> Roshan


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.