@mayki wogno Can you check the same from Ranger UI->Access->Audit, which will display the audit in more formatted. You can pass the screenshot here to get more details. Ranger UI - http://<ranger_host>:6080 ... View more

@Yukti Agrawal Can you please re-check and confirm if hostname if properly set in below files and commands - $/etc/hosts $/etc/sysconfig/network $hostname $hostname -f Pls perform this on all agents and ambari server. ... View more

@Yukti Agrawal Can you capture $jstack -l <pid_of_ambari_server> Also check you have enough memory on the node. ... View more

@Eon kitex please pass detailed logs to take a look at the issue if this is still not resolved. ... View more

The other issue can be - oozie-env.sh the catalina tmp dir is set to /oozietest. export CATALINA_TMPDIR=${CATALINA_TMPDIR:-/oozietest/} and users did not have write permissions to the directory RESOLUTION: changed oozie-env.sh catalina tmp dir to export CATALINA_TMPDIR=${CATALINA_TMPDIR:-/var/tmp/oozie} ... View more

@Keerthi Mantri Make sure if you have any change/modifications to core hadoop configurations you will have to manually push the changes to the oozie share lib location. Pls try placing the core hadoop configurations into the oozie share lib directory. ... View more

@Vijay Lakshman Can you check the container size allocated ? Seems you are hitting memory issue. ... View more

@Wael Emam Its never recommended to have different OS for same host in cluster. If you still manage to bypass this for ambari agent install you will still face issue while deploying services and running applications on the host. Better is to re-install and use same version of OS. Still you can check - https://community.hortonworks.com/questions/18479/how-to-register-host-with-different-os-to-ambari.html ... View more