Hi Jan,

this is rather generic error saying that ZeppelinServer somehow could not
connect to the interpreter proces on your machine.

Could you please share more from logs/* in particular, .out and .log of the
Zeppelin server AND zepplein-interpreter-spark*.log - usually this is
enough to identify the reason.

Two more questions:
- does this happen on every paragraph run? if you try to click Run multiple
times in a row
- does it still happen if you re-starting Spark interpreter manually from
GUI? ("Anonymous"->Interpreters->Spark->restart)

--
Alex

On Wed, Nov 16, 2016, 12:37 Jan Botorek <jan.boto...@infor.com> wrote:

> Hello,
>
> I am not able to run any Spark code in the Zeppelin. I tried compiled
> versions of Zeppelin as well as to compile the source code on my own based
> on the https://github.com/apache/zeppelin steps.
>
> My configuration is Scala in 2.11 version and spark 2.0.1. Also, I tried
> different versions of Zeppelin available at github (master, 0.6, 0.5.6).
>
>
>
> The result is always the same. The Zeppelin starts but when any code is
> run (e.g. “2 + 1”, “sc.version”), the subsequent exception is thrown.
>
>
>
> java.net.ConnectException: Connection refused: connect at
> java.net.DualStackPlainSocketImpl.connect0(Native Method) at
> java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
> 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.PlainSocketImpl.connect(PlainSocketImpl.java:172) at
> java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at
> java.net.Socket.connect(Socket.java:589) at
> org.apache.thrift.transport.TSocket.open(TSocket.java:182) at
> org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:51)
> at
> org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:37)
> at
> org.apache.commons.pool2.BasePooledObjectFactory.makeObject(BasePooledObjectFactory.java:60)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:861)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
> at
> org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess.getClient(RemoteInterpreterProcess.java:189)
> at
> org.apache.zeppelin.interpreter.remote.RemoteInterpreter.init(RemoteInterpreter.java:163)
> at
> org.apache.zeppelin.interpreter.remote.RemoteInterpreter.getFormType(RemoteInterpreter.java:328)
> at
> org.apache.zeppelin.interpreter.LazyOpenInterpreter.getFormType(LazyOpenInterpreter.java:105)
> at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:260) at
> org.apache.zeppelin.scheduler.Job.run(Job.java:176) at
> org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:328)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
>
>
> Based on googling and my assumptions, there is something wrong with the
> spark interpreter in relation to the Zeppelin.
>
> I also tried to connect the Spark interpreter to Spark running externally
> (in interpreter settings of Zeppelin), but it didn’t work.
>
>
>
> Do you have any ideas about what could possibly be wrong?
>
> Thank you for any help – any ideas and insights would be appreciated.
>
>
>
> Best regards,
>
> Jan Botorek
>
>
>

Reply via email to