@David Manukian That's the image I forgot to attach sorry ... View more

@David Manukian My previous hosts file was from my windows laptop I am not conversant with Macbooks 🙂 MacOSFirewall setting Go to System Preferences, Security & Privacy, Firewall, Firewall Options... see attached screenshot Your ambari UI should be accessible http://192.168.0.75:8080 or http://ambari.training:8080 Port forwarding Quite simple to do, Firstly you will need to enable the remote login service on your mac (System Preferences -> Sharing -> Remote Login). This starts your ssh server. Then run the following command in your OS X Terminal: The format is thus basically: ssh -L local_addr:local_port:remote_addr:remote_port -N 127.0.0.1 example ssh -L 200.234.XXX.XXX:10000:10.211.55.5:80 -N 127.0.0.1 You may need to accept the server fingerprint initially as well as type in your local password for ssh login. (You can also set up a local to local ssh public/private key to make it not prompt for a password, but that it a different exercise.) ... View more

@David Manukian Can you share your local hosts entry, make sure you commented out the below #127.0.0.1 localhost #::1 localhost Please revert ... View more

@Ajay Jayswal Can you ping your vm IP from Windows? restart the ambari server and agent # ambari-server restart # ambari-agent restart Whats your cluster configuration single node or multi-node? ... View more

@David Manukian Check this HCC learning rope link it should help you with the port forwarding that's the problem you are encountering ... View more

@Artur Bukowski I am not an oozie expert but the error "Caused by: ERROR 42X05: Table/View 'DBS' does not exist." where does it pick the DBS table name from? But in the oozie workflow I don't see the name of the table shouldn't it be an argument before the --hcatalog-storage-stanza <arg>table-name</arg> <arg>--hcatalog-storage-stanza</arg> Ain't you missing the location ie --hcatalog-storage-stanza "stored as orcfile LOCATION /bla/bla" Please revert ... View more

@Vinay K It seems the disk the journals are on is just too busy. If it's not a big and production cluster can you reboot it. Can you also adjust the following in the two files and retry! hdfs-site.xml dfs.qjournal.start-segment.timeout.ms = 90000 dfs.qjournal.select-input-streams.timeout.ms = 90000 dfs.qjournal.write-txns.timeout.ms = 90000 core-site.xml ipc.client.connect.timeout = 90000 Please revert ... View more

@Vinay K How many zookeepers do you have up and running? Make sure all the 3 JournalManager are running too. ... View more

@Aymen Rahal Check my update !!!! ... View more