[jira] [Created] (LIVY-686) Exception in SASL negotiation on Ubuntu18.04 - Windows Subsystem for Linux

["Cesar Tenganan (Jira)" <ji...@apache.org>]

Cesar Tenganan created LIVY-686:
-----------------------------------

             Summary: Exception in SASL negotiation on Ubuntu18.04 - Windows Subsystem for Linux
                 Key: LIVY-686
                 URL: https://issues.apache.org/jira/browse/LIVY-686
             Project: Livy
          Issue Type: Bug
          Components: RSC, Server
    Affects Versions: 0.5.0
            Reporter: Cesar Tenganan


Hi,

We have been working to configure Apache livy-0.5.0-incubating with Spark on Windows,  in this case using WSL Windows Subsystem for Linux / Ubuntu-18.04 distribution.
Both Livy and spark have been configured on the linux subsystem, but Livy is throwing an error when it is creating the spark session that says:

 
{code:java}
19/09/17 09:51:41 INFO RpcServer$SaslServerHandler: Exception in SASL negotiation.
java.lang.IllegalArgumentException: Unexpected client ID 'fca3ee25-ae81-42a7-b07d-9613238bd820' in SASL handshake.
at org.apache.livy.rsc.Utils.checkArgument(Utils.java:40)
at org.apache.livy.rsc.rpc.RpcServer$SaslServerHandler.update(RpcServer.java:288)
at org.apache.livy.rsc.rpc.SaslHandler.channelRead0(SaslHandler.java:61)
at org.apache.livy.rsc.rpc.SaslHandler.channelRead0(SaslHandler.java:36)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:321)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267)
at io.netty.handler.codec.ByteToMessageCodec.channelRead(ByteToMessageCodec.java:103)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:321)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1280)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:890)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:564)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:505)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:419)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:391)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
at java.lang.Thread.run(Thread.java:748)
19/09/17 09:51:41 WARN DefaultChannelPipeline: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
java.lang.IllegalArgumentException: Unexpected client ID 'fca3ee25-ae81-42a7-b07d-9613238bd820' in SASL handshake.
at org.apache.livy.rsc.Utils.checkArgument(Utils.java:40)
at org.apache.livy.rsc.rpc.RpcServer$SaslServerHandler.update(RpcServer.java:288)
at org.apache.livy.rsc.rpc.SaslHandler.channelRead0(SaslHandler.java:61)
at org.apache.livy.rsc.rpc.SaslHandler.channelRead0(SaslHandler.java:36)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
{code}

We have tested the same configuration directly on Ubuntu, Centos and MacOS machines and it worked correctly, the error just appeared when we try on Windows Subsystem Linux / Ubuntu-18.04 distro.

Could you please help us to understand what this error means? or how can we validate that the system has the requirements to perform the SASL negotiation correctly?

I have attached a file with more details of trace log

Thanks for your help!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)