If you type any linux command you will get an error message usage.
The error message tells you the problem and solution.
If the error message detects a problem and doesnt give you solution then
blame the developer and tell him to take a lesson from using the
operating system.
That was the way I was taught programming.
Standard Operating Procedure.
You may not like my answer but I'm not missing the point.
I am making a different point and if it was taken on board then you
wouldn't need to ask what the problem is.
The only way you are going to find an answer is if somebody else had same
problem and by luck not skill found the solution.
On Sun, 3 May 2020, 04:28 Ravi Pullareddy, <ravi.pullare...@minlog.com.au>
wrote:
> Hi Zahid
>
>
>
> You have completely missed my question. As you would be aware, there are
> four ways to setup Ubuntu…a) Ubuntu as base operating system. B) Ubuntu On
> Docker c) Ubuntu on Windows HyperV and d) Ubuntu on Windows WSL (Windows
> Subsystem for Linux). There are no issues with Zeppelin and Flink running
> with options a,b and c. However, there is an issue with Ubuntu run as
> Windows WSL.
>
>
>
> I request readers of this blog to answer this specific question if they
> have good understanding of Windows WSL. The issue is not with Ubuntu, Flink
> or Zeppelin. It is to do with WSL.
>
>
>
> Thanks
>
>
>
> Ravi Pullareddy
>
>
>
>
>
>
>
> *From:* Zahid Rahman <zahidr1...@gmail.com>
> *Sent:* Sunday, 3 May 2020 12:58 PM
> *To:* users@zeppelin.apache.org
> *Subject:* Re: Zeppelin 0.9 flink interpreter on WSL ubuntu Linux
>
>
>
> I have ran Zeppelin flink interpreter on Zeppelin remotely on two
> different ubuntu machines. Ubuntu Version 19 and 20.
>
>
>
> Your error is quite specific! Looking at the error messages it seems to
> me there is port conflict . Java code describes what it is doing.
>
>
>
> Perhaps try the setup using the instructions I mentioned previously to
> eliminate one cause of error. May be they will work for you. Especially if
> you have flink and Zeppelin installed on same machine.
>
>
>
>
>
> On Sun, 3 May 2020, 01:38 Ravi Pullareddy, <ravi.pullare...@minlog.com.au>
> wrote:
>
> Hi Som
>
>
>
> There is no issue in running flink 1.10.0 on Windows WSL ubuntu linux.
> The issue is running Zeppelin with flink interpreter on WSL ubuntu linux.
> Have you tried running Zeppelin 0.9 on Windows WSL linux and tried
> connecting to Flink instance?
>
>
>
> Thanks
>
>
>
> Ravi Pullareddy
>
>
>
>
>
> *From:* Som Lima <somplastic...@gmail.com>
> *Sent:* Sunday, 3 May 2020 9:51 AM
> *To:* users@zeppelin.apache.org
> *Subject:* Re: Zeppelin 0.9 flink interpreter on WSL ubuntu Linux
>
>
>
> I have ran flink successfully by following the instructions sent on the
> mailing list by Jeff.
>
>
>
> See mailing list archive.
>
>
>
>
>
>
>
> On Sat, 2 May 2020, 22:51 Ravi Pullareddy, <ravi.pullare...@minlog.com.au>
> wrote:
>
> Hi Jeff
>
> Has anyone tried running flink interpreter on Zeppelin 0.8 or Zeppelin 0.9
> on Windows WSL ubuntu? Since WSL does not allow creation of random ports,
> flink interpreter fails as below. Any suggestion is much appreciated.
>
>
> INFO [2020-05-02 07:43:53,211] ({main}
> RemoteInterpreterServer.java[main]:261) -
>
> URL:jar:file:/mnt/d/zeppelin-0.8.1-bin-all/lib/interpreter/zeppelin-interpreter-0.8.1.jar!/org/apache/zeppelin/interpreter/remote/RemoteInterpreterServer.class
> INFO [2020-05-02 07:43:53,274] ({main}
> RemoteInterpreterServer.java[<init>]:162) - Launching ThriftServer at
> 169.254.47.73:62115
> INFO [2020-05-02 07:43:53,282] ({main}
> RemoteInterpreterServer.java[<init>]:166) - Starting remote interpreter
> server on port 62115
> INFO [2020-05-02 07:43:53,283] ({Thread-0}
> RemoteInterpreterServer.java[run]:203) - Starting remote interpreter server
> on port 62115
> INFO [2020-05-02 07:57:47,187] ({main}
> RemoteInterpreterServer.java[main]:261) -
>
> URL:jar:file:/mnt/d/zeppelin-0.8.1-bin-all/lib/interpreter/zeppelin-interpreter-0.8.1.jar!/org/apache/zeppelin/interpreter/remote/RemoteInterpreterServer.class
> INFO [2020-05-02 07:57:47,255] ({main}
> RemoteInterpreterServer.java[<init>]:162) - Launching ThriftServer at
> 169.254.47.73:62223
> INFO [2020-05-02 07:57:47,262] ({main}
> RemoteInterpreterServer.java[<init>]:166) - Starting remote interpreter
> server on port 62223
> INFO [2020-05-02 07:57:47,264] ({Thread-0}
> RemoteInterpreterServer.java[run]:203) - Starting remote interpreter server
> on port 62223
> INFO [2020-05-02 07:57:48,273] ({Thread-1}
> RemoteInterpreterUtils.java[registerInterpreter]:165) - callbackHost:
> 169.254.47.73, callbackPort: 62221, callbackInfo:
> CallbackInfo(host:169.254.47.73, port:62223)
> ERROR [2020-05-02 07:57:48,279] ({Thread-1}
> RemoteInterpreterServer.java[run]:192) - Error while registering
> interpreter: CallbackInfo(host:169.254.47.73, port:62223)
> org.apache.thrift.transport.TTransportException: java.net.SocketException:
> Network is unreachable (connect failed)
> at org.apache.thrift.transport.TSocket.open(TSocket.java:187)
> at
>
> org.apache.zeppelin.interpreter.remote.RemoteInterpreterUtils.registerInterpreter(RemoteInterpreterUtils.java:168)
> at
>
> org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$1.run(RemoteInterpreterServer.java:190)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.net.SocketException: Network is unreachable (connect
> failed)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net
> .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at
> java.net
> .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:606)
> at org.apache.thrift.transport.TSocket.open(TSocket.java:182)
> ... 3 more
> INFO [2020-05-02 07:57:48,281] ({Thread-1}
> RemoteInterpreterServer.java[shutdown]:209) - Shutting down...
>
>
