stacktrace?
> On Jul 8, 2016, at 2:08 AM, B00083603 Michael O Brien
> <b00083...@student.itb.ie> wrote:
>
> If I swap the spark home value to use the binaries I installed on the cluster
> that error goes away but I get java.net.ConnectException: Connection refused
> error instead.
>
> If I use the spark console on Master I can run the pi example. I'm not sure
> if it matters but I don't have hadoop setup but do have shared storage
> available to all nodes via the same path
>
>
> From: Mohit Jaggi <mohitja...@gmail.com>
> Sent: 07 July 2016 18:30
> To: users@zeppelin.apache.org
> Subject: Re: Zeppelin reports unable to connect to master but master webUI is
> up and shows connected workers
>
> it seems you have conflicting binaries between the two machines. check the
> version on server running Z and on the master. they should be the same.
>
>> On Jul 7, 2016, at 7:26 AM, B00083603 Michael O Brien
>> <b00083...@student.itb.ie <mailto:b00083...@student.itb.ie>> wrote:
>>
>> Hi,
>> I created a new notebook and added sc as the only paragraph. When I run it I
>> get errors displayed org.apache.thrift.transport.TTransportException
>>
>> Looking at the spark interpreter logs it shows the master as unresponsive.
>>
>> I can view the master webpage on http://vm-20161023-002:8080/
>> <http://vm-20161023-002:8080/> which shows the 2 worker nodes connected
>> which die when I shut them down. There are no applications listed on the Web
>> UI and no historic list of applications as this is my first cluster
>>
>> I can ping from zeppelin the master vm.
>> I also removed the conf/zeppelin.sh setting where i specified my own spark
>> install on zeppelin
>>
>> Any pointers whats I'm doing wrong?
>>
>> Michael
>>
>>
>> INFO [2016-07-07 16:10:39,031] ({appclient-register-master-threadpool-0}
>> Logging.scala[logInfo]:58) - Connecting to master
>> spark://vm-20161023-002:7077
>> <applewebdata://C60A36CD-6799-4EB6-B8DA-C216C262391F>...
>> INFO [2016-07-07 16:10:39,035] ({appclient-register-master-threadpool-0}
>> Logging.scala[logInfo]:58) - Connecting to masterspark://vm-20161023-002:707
>> <applewebdata://C60A36CD-6799-4EB6-B8DA-C216C262391F>7
>> <applewebdata://C60A36CD-6799-4EB6-B8DA-C216C262391F>...
>> WARN [2016-07-07 16:10:39,037] ({pool-2-thread-3}
>> Logging.scala[logWarning]:70) - Application ID is not initialized yet.
>> ERROR [2016-07-07 16:10:39,039] ({appclient-registration-retry-thread}
>> Logging.scala[logError]:74) - Application has been killed. Reason: All
>> masters are unresponsive! Giving up.
>> WARN [2016-07-07 16:10:39,049] ({appclient-register-master-threadpool-0}
>> Logging.scala[logWarning]:91) - Failed to connect to master
>> vm-20161023-002:7077
>> java.lang.RuntimeException: java.io.InvalidClassException:
>> org.apache.spark.rpc.netty.RequestMessage; local class incompatible: stream
>> classdesc serialVersionUID = -2221986757032131007, local class
>> serialVersionUID = -5447855329526097695
>>
>>
>> ITB Email Disclaimer This is a confidential communication and is intended
>> only for the addressee indicated in the message (or duly authorised to be
>> responsible for the delivery of the message to such person). You are
>> specifically prohibited from copying this message or delivering the same, or
>> any part thereof, to any other person, whomsoever or howsoever, unless you
>> receive written authorisation from us to do. If you are anyone other than
>> the intended addressee, or person duly authorised and responsible for the
>> delivery of this message to the intended addressee, you should destroy this
>> message and notify us immediately.
>
> ITB Email Disclaimer This is a confidential communication and is intended
> only for the addressee indicated in the message (or duly authorised to be
> responsible for the delivery of the message to such person). You are
> specifically prohibited from copying this message or delivering the same, or
> any part thereof, to any other person, whomsoever or howsoever, unless you
> receive written authorisation from us to do. If you are anyone other than the
> intended addressee, or person duly authorised and responsible for the
> delivery of this message to the intended addressee, you should destroy this
> message and notify us immediately.
