@qiancai zhou Are you Manually stopping (gracefully) the Zookeeper? (In this case ambari will assume normal scenario) You need to kill (Crash it) the Zookeeper Server to test this feature and then see you get the following kind of output: # ambari-agent --version 2.5.1.0 # kill -9 `cat /var/run/zookeeper/zookeeper_server.pid` . ambari-agent.log INFO 2017-06-23 07:15:24,216 RecoveryManager.py:185 - current status is set to INSTALLED for ZOOKEEPER_SERVER INFO 2017-06-23 07:15:24,216 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs recovery, desired = STARTED, and current = INSTALLED. INFO 2017-06-23 07:15:29,197 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs recovery, desired = STARTED, and current = INSTALLED. INFO 2017-06-23 07:15:29,198 RecoveryManager.py:834 - START command cannot be computed as details are not received from Server. . . INFO 2017-06-23 07:15:39,572 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs recovery, desired = STARTED, and current = INSTALLED. INFO 2017-06-23 07:15:39,572 RecoveryManager.py:834 - START command cannot be computed as details are not received from Server. INFO 2017-06-23 07:15:50,463 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs recovery, desired = STARTED, and current = INSTALLED. INFO 2017-06-23 07:15:50,463 RecoveryManager.py:834 - START command cannot be computed as details are not received from Server. INFO 2017-06-23 07:16:01,346 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs recovery, desired = STARTED, and current = INSTALLED. INFO 2017-06-23 07:16:01,346 RecoveryManager.py:834 - START command cannot be computed as details are not received from Server. INFO 2017-06-23 07:16:21,789 Controller.py:258 - Adding 20 status commands. Heartbeat id = 1282597 . . . INFO 2017-06-23 07:16:23,510 Controller.py:407 - Adding recovery command START for component ZOOKEEPER_SERVER INFO 2017-06-23 07:16:23,511 Controller.py:249 - Adding 1 commands. Heartbeat id = 1282598 INFO 2017-06-23 07:16:23,511 ActionQueue.py:113 - Adding AUTO_EXECUTION_COMMAND for role ZOOKEEPER_SERVER for service ZOOKEEPER of cluster plain_ambari to the queue. INFO 2017-06-23 07:16:23,715 RecoveryManager.py:255 - ZOOKEEPER_SERVER needs recovery, desired = STARTED, and current = INSTALLED. INFO 2017-06-23 07:16:23,891 ActionQueue.py:238 - Executing command with id = 1-0, taskId = 1497010157 for role = ZOOKEEPER_SERVER of cluster plain_ambari. INFO 2017-06-23 07:16:23,892 ActionQueue.py:279 - Command execution metadata - taskId = 1497010157, retry enabled = False, max retry duration (sec) = 0, log_output = True INFO 2017-06-23 07:16:26,078 ActionQueue.py:324 - Quit retrying for command with taskId = 1497010157. Status: COMPLETED, retryAble: False, retryDuration (sec): -1, last delay (sec): 1 INFO 2017-06-23 07:16:26,078 ActionQueue.py:339 - Command with taskId = 1497010157 completed successfully! INFO 2017-06-23 07:16:26,079 RecoveryManager.py:185 - current status is set to STARTED for ZOOKEEPER_SERVER INFO 2017-06-23 07:16:26,080 ActionQueue.py:390 - After EXECUTION_COMMAND (START), with taskId=1497010157, current state of ZOOKEEPER_SERVER to STARTED . ... View more

@qiancai zhou Enabling auto-start for a service causes the ambari-agent to attempt re-starting service components in a stopped state without manual effort by a user. Auto-Start Services is enabled by default, butonlythe Ambari Metrics Collector component is set to auto-start by default. Reference: https://docs.hortonworks.com/HDPDocuments/Ambari-2.5.0.3/bk_ambari-operations/content/ch07s04.html - So if the auto start is not happening (evev after enabling the "Zookeeper Server " AutoStart Enabled button then you should see some messages in the "/var/log/ambari-agent.log" file because it is agents responsibility to do that. Please share the ""/var/log/ambari-agent.log" file with us. Also please share the zookeeper Log file. . ... View more

@qiancai zhou In Ambari 2.5 it is very easy to achieve the Zookeeper or other component auto restart setting from UI itself. Admin UI --> Admin (Drop Down) --> Service Auto Start . ... View more

@Hugo Felix Try this: ###### on Zeppelin Host run the below commans ###### # mv /var/lib/ambari-agent/cache /var/lib/ambari-agent/cache_OLD # mkdir /var/lib/ambari-agent/cache # ambari-agent restart ... View more

@Hugo Felix Try this: ###### on Zeppelin Host run the below commans ###### # mv /var/lib/ambari-agent/cache /var/lib/ambari-agent/cache_OLD # mkdir /var/lib/ambari-agent/cache # ambari-agent restar ... View more

@Hugo Felix Not sure from where did you get the "zeppelin-ambari-plugin-phd30" and "zeppelin-ambari-plugin-phd23" Versions. Duplicate packages of different version. I was just reading about it in google and found this: https://github.com/tzolov/zeppelin-ambari-plugin Not sure if this plugin is causing any issue. zeppelin-ambari-plugin doc says: Apache Zeppelin service for Apache Ambari. It allows you to install and manage Zeppelin as an Ambari service. The plugin is compatible with Ambari 1.7, 2.0.x and 2.1.x and Stacks: PHD3.0, HDP2.2xand HDP2.3. To embed the Zeppelin UI pages within Ambari you can use the Ambari Webpage Embedder project . Also as you mentioned that you are using Ambari 2.5.0, But i do not see any the line number 185 matching your error which is strange. Have you edited any script? File "/var/lib/ambari-agent/cache/stacks/HDP/2.4/services/ZEPPELIN/package/scripts/master.py", line 185, in status + status_params.zeppelin_user + '*.pid')[0] Ambari 2.5.0 Code: https://github.com/apache/ambari/blob/release-2.5.0/ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py , So i am suspecting that may be the ambari-agent is using some older version of "master.py" .... please check this file on ambari server # On ambari Server /var/lib/ambari-server/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py # On Ambari Agent where Zeppelin is installed. /var/lib/ambari-agent/cache/stacks/HDP/2.4/services/ZEPPELIN/package/scripts/master.py . Are these two file same? If those two files are different means the ambari-agent "cache" directory has old version of files. Please clear the agent cache and restart the agent so that it will pull the latest files from ambari server /var/lib/ambari-agent/cache ... View more

@Hugo Felix Can you please share the output of the following command (this is to verify of the ambari-agent and server RPMs are of same version) # rpm -qa | grep ambari . It has something to do with the Zeppelin PID directory ("/var/run/zeppelin"). Can you check if that directory is writable ( i mean write permission). ... View more

@Hugo Felix Removing (Uninstalling) Zeppelin from Ambari UI and Installing it back should be ok. . ... View more

@Hugo Felix The Change in Ambari 2.5 is to remove the "Zeppelin View". It will not affect the "Quick Link" or any other Zeppelin Service. Regarding the following error: Stop command finished but process keep running . It can happen if the Zeppelin process is stopped but due to some reason the Zeppelin PID file is not cleared. So please try to manually remove this file and then check again. # rm -f /var/run/zeppelin/zeppelin-zeppelin-xxxxxxxx.pid . ... View more

@Stefan Kupstaitis-Dunkler Post install upgrades are necessary to be performed like AMS upgrade. The piece of code that you removed is actually added there intentially to fix the issue reported in: AMBARI-20888. wrong ZK parent node (hbase-unsecure) getting configured as part of the jdbc(phoenix) URL on ubuntu secured cluster. . Specially for kerberized environment. ... View more