Have you tried restart with 'sudo -u zeppelin'? sudo -u zeppelin /usr/lib/zeppelin/bin/zeppelin-daemon.sh restart
worked for me. Thanks, moon On Sat, Jun 3, 2017 at 11:51 PM Jonathan Kelly <jonathaka...@gmail.com> wrote: > Shyla, > > What release of EMR are you using? There was a problem with earlier > releases of EMR where upstart was not properly tracking 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 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 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 outputs stop: Unknown >> instance: >> 3. sudo start zeppelin outputs . start: Job failed >> to start >> >> Zeppelin is running and able to login as anonymous user, unable to >> restart . Appreciate your input. >> >> Thanks >> >
