You should be able to enable logging for the interpreter group. It's the log
properties file under conf. There are instructions around, but let me know if
you aren't able to get it working.
> On May 11, 2016, at 12:06 AM, Samuel Alexander
> wrote:t
>
> Hi Amos,
>
> It doesn't contain any ot
Hi Amos,
It doesn't contain any other information apart what I've sent earlier.
Thanks,
Sam.
On Tue, May 10, 2016 at 2:10 AM, Amos Elberg wrote:
> Yes, please.
>
> On May 9, 2016, at 12:14 PM, Samuel Alexander
> wrote:
>
> Hi Amos,
>
> I am using ubuntu docker in a ubuntu system.
>
> Yes, it
Yes, please.
> On May 9, 2016, at 12:14 PM, Samuel Alexander
> wrote:
>
> Hi Amos,
>
> I am using ubuntu docker in a ubuntu system.
>
> Yes, it seems spark is not starting. I don't see the statement "--
> Create new SparkContext" in my console as well.
>
> I see a single file in zeppe
Hi Amos,
I am using ubuntu docker in a ubuntu system.
Yes, it seems spark is not starting. I don't see the statement "--
Create new SparkContext" in my console as well.
I see a single file in zeppelin\logs zeppelin--7ed5948b0d52.log and
attached the same. It doesn't contain any errors. Do y
Sam - it should run fine in docker, but if you are running a Linux docker on
Windows, I have heard that sometimes the environment can become flaky.
What you're seeing sounds like spark is failing to start.
You should be able to get Zeppelin to output a log for the entire spark
interpreter grou
