@mike_bronson7    Yes, in fact, a better solution is mv all the contents of  /opt/confluent/zookeeper/data/version-2   usually ie [log.1,log.18263] there could be many that's why its easier to move  than delete but remember to recreate the version-2 directory with the same user: group and permissions  take note of those details 🙂 HTH  ... View more

@asmarz  When you delete components at times you leave the database in an inconsistent  status. you will need to log onto the Ambari Database to do some manual cleaning. There are 3 important tables that hold the component status hostcomponentstate hostcomponentdesiredstate servicecomponentdesiredstate A  targeted select on the component name to show , run the below  to check if your oozie components are still [root@nakuru ~]# psql ambari ambari Password for user ambari: #default password is "bigdata" psql (8.4.20) Type "help" for help. ambari=> select distinct component_name from hostcomponentstate; If you see the oozie components in the databases then you will have to delete those entries, I have  used 'OOZIE_SERVER','OOZIE_CLIENT' in the below example                      Delete the orphaned  Oozie entries   [root@nakuru ~]# psql ambari ambari Password for user ambari: #default password is "bigdata" psql (8.4.20) Type "help" for help. ambari=> delete from hostcomponentstate where component_name='OOZIE_CLIENT'; DELETE 1 ambari=> delete from hostcomponentstate where component_name='OOZIE_SERVER'; DELETE 1 ambari=> delete from hostcomponentdesiredstate where component_name='OOZIE_CLIENT'; DELETE 1 ambari=> delete from hostcomponentdesiredstate where component_name='OOZIE_SERVER'; DELETE 1 ambari=> delete from servicecomponentdesiredstate where component_name='OOZIE_CLIENT'; DELETE 1 ambari=> delete from servicecomponentdesiredstate where component_name='OOZIE_SERVER'; DELETE 1 ambari=> commit; WARNING: there is no transaction in progress COMMIT ambari=> \q [root@nakuru ~]#   You can then stop all the components in the  cluster and restart the database, you might need to restart some stale configurations  that might have been orphaned  due to the removal of the oozie components    HTH   ... View more

@divya_thaore  Yes please you need to use the Linux CLI to navigate  to those directories ... View more

@fklezin  I think your zeppelin is not aware of the python version in the Zeppelin config at /usr/hdp/current/zeppelin-server/conf/interpreter.json, and change the below line 30 in the config: "zeppelin.pyspark.python": { "type": "string", "name": "zeppelin.pyspark.python", "value": "python" }, To "zeppelin.pyspark.python": { "type": "string", "name": "zeppelin.pyspark.python3", "value": "python" }, Make sure you have these values in Ambari UI--> Zeppelin-->Config-->Advanced zeppelin-env export PYSPARK_PYTHON=python3 export PYSPARK_DRIVER_PYTHON=python3   Restart Zeppelin and retry ... View more

@svasi  read through the documentation in that link and let me know ! ... View more

@Kou_Bou  That shouldn't be a problem, but before getting to the diagnostics can you confirm you have diligently followed this ​Prepare the Environment  newbies always forget that every step is important and hence things look complicated 🙂 Having said that is it a single/multi node cluster? In the logs I see something like  host=ambari.server I hope you it's a pseudonymized value else your ambari should have FQDN  the output of Linux command $ hostname -f I also see an error  NetUtil.py:89 - SSLError: Failed to connect.  That is due to python version To resolve that  do this you have to set verify=disable by editing the /etc/python/cert-verification.cfg file.   [https] verify=platform_default To [https] verify=disable   Can you also share these files  /etc/ambari-server/conf/ambari.properties /etc/ambari-agent/conf/ambari-agent.ini /etc/hosts Please revert      ... View more

@divya_thaore    Th default location is /var/log/hadoop/hdfs and here you wiill get hadoop-hdfs-datanode-<FQDN>.log hadoop-hdfs-datanode-<FQDN>.out hadoop-hdfs-secondarynamenode-<FQDN>.log hadoop-hdfs-secondarynamenode-<FQDN>.out And it's important too to check the  host server messages /var/log/messages Those files should contain the clue  all the .out are informative  look at the .log most probably the last few entries      ... View more