king the Zeppelin PID,
>>> so "sudo stop zeppelin" wouldn't work. This has been fixed for a while, but
>>> I don't remember what version contained the fix. If you are not using the
>>> latest release, you might want to try that. Otherwise, if you're alrea
t; latest release, you might want to try that. Otherwise, if you're already
>> using the latest version, there might be something else going on.
>>
>> ~ Jonathan
>> On Sat, Jun 3, 2017 at 8:28 PM shyla deshpande <deshpandesh...@gmail.com>
>> wrote:
>>
&g
you might want to try that. Otherwise, if you're already
> using the latest version, there might be something else going on.
>
> ~ Jonathan
> On Sat, Jun 3, 2017 at 8:28 PM shyla deshpande <deshpandesh...@gmail.com>
> wrote:
>
>> I changed some configuration and want to r
o restart zeppelin on AWS EMR, but
> unable to do. My local Zeppelin works fine.
>
> I have tried
> 1. zeppelin-daemon.sh restart outputs[ OK ] but has
> no effect.
> 2. sudo stop zeppelin outputsstop: Unknown
> instance:
> 3.
.apache.org>>
Date: Sunday, June 4, 2017 at 11:28 AM
To: "users@zeppelin.apache.org<mailto:users@zeppelin.apache.org>"
<users@zeppelin.apache.org<mailto:users@zeppelin.apache.org>>
Subject: unable to restart zeppelin on AWS EMR
I changed some configuration a
I changed some configuration and want to restart zeppelin on AWS EMR, but
unable to do. My local Zeppelin works fine.
I have tried
1. zeppelin-daemon.sh restart outputs[ OK ] but has
no effect.
2. sudo stop zeppelin outputsstop: Unknown
instance:
3
