Re: unable to restart zeppelin on AWS EMR

I found from the spark History server , that my old Zeppelin application was still alive and using up the resources. After I killed that application, it is working fine. Thanks everyone for all your help. On Sun, Jun 4, 2017 at 8:48 PM, shyla deshpande wrote: > Thanks everyone for the reply. Sti

Re: unable to restart zeppelin on AWS EMR

Thanks everyone for the reply. Still having issues. Moon, I had tried sudo -u zeppelin /usr/lib/zeppelin/bin/zeppelin-daemon.sh restart and it did not work. I am using the Zeppelin Version 0.7.1. I checked the logs and in the logs, I saw the error message that the port 8890 already in use. Sin

Re: unable to restart zeppelin on AWS EMR

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 wrote: > Shyla, > > What release of EMR are you using? There was a problem with earlier > releases of E

Re: unable to restart zeppelin on AWS EMR

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

Re: unable to restart zeppelin on AWS EMR

Please check the zeppelin log Best Regard, Jeff Zhang From: shyla deshpande mailto:deshpandesh...@gmail.com>> Reply-To: "users@zeppelin.apache.org" mailto:users@zeppelin.apache.org>> Date: Sunday, June 4, 2017 at 11:28 AM To: "users@zeppelin.apache.org