I was doing config changes on EMR (EMR Release label:emr-5.7.0) Zeppelin
(Zeppelin 0.7.2) and struggled with Zeppelin server restart, finally I was able
to narrow down to the steps to reproduce below (it's reproducible for any newly
created EMR if following the steps below):
1) provision a EMR c
Hi,
Can you try restart Zeppelin with 'zeppelin' user permission?
sudo -u zeppelin /usr/lib/zeppelin/bin/zeppelin-daemon.sh restart
Thanks,
moon
On Wed, Jul 19, 2017 at 3:21 PM Richard Xin wrote:
> I was doing config changes on EMR (EMR Release label:emr-5.7.0) Zeppelin
> (Zeppelin 0.7.2) and
nope, not working
[ec2-user@ip-xxx-xxx-xx-xxx ~]$ sudo -u zeppelin
/usr/lib/zeppelin/bin/zeppelin-daemon.sh restart
find: failed to restore initial working directory: Permission denied
Zeppelin is not running
Zeppelin start [ OK ]
Zeppelin process died
Hey Moon,
Can you remove me from this mailing list? Thanks,
-Steven
From: moon soo Lee
Reply-To: "users@zeppelin.apache.org"
Date: Wednesday, July 19, 2017 at 5:39 PM
To: "users@zeppelin.apache.org"
Subject: Re: restarting zeppelin on EMR causing exceptions
Hi,
Can you try restart Zeppelin
EMR uses upstart to manage all daemons/services running on the cluster, so
the best way to restart Zeppelin on EMR is to use "sudo stop zeppelin; sudo
start zeppelin". (Note: normally you'd use "sudo restart", but this doesn't
actually work due to the way that upstart is configured for all of these
for newly installed Zeppelin (0.7.2), I renamed zeppelin-site.xml.template to
zeppelin-site.xml, and restart zeppelin, zeppelin-site.xml already have the
following enabled:
zeppelin.notebook.storage
org.apache.zeppelin.notebook.repo.GitNotebookRepo
versioned notebook persistence layer impl
