Member since
04-06-2017
17
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4450 | 03-07-2018 01:46 AM |
08-18-2019
09:42 PM
Hi @rushi_ns , yours might be completly different issue. Please create a new Question thread stating your issue.
... View more
05-22-2019
08:16 PM
@ajay vembu Here is the cause of the problem Caused by: java.net.BindException: Address already in use This means some process is using the default Node manager port. You will need to kill the process and your name node will start successfully do the following things sudo lsof -i -P -n | grep LISTEN or sudo netstat -ltup It was a simple port collision that has occurred. Can you first stop the Ambari Metrics process HMaster process at times it grabs port 45454 and this blocks the NodeManager from starting? Please do that and revert
... View more
03-07-2018
01:46 AM
Thanks @Geoffrey Shelton Okot The issue has been resolved. Again I came to know the importance of /etc/hosts file. It's not the firewall that was blocking the connection rather the process was spawned internal to the instance - meaning none of the other instance could access the process. Zookeeper process looks for the ip address from /etc/hosts file and spawns the process, instead of fetching the ip address it took the loopback address(127.0.0.1) which made sure the outside world cannot access the process. Followed the thread to resolve the issue MeaningOfIPaddressinProcess
... View more
09-18-2017
07:47 PM
@ajay vembu Awesome, glad to hear. Best of luck with the remainder of the installation.
... View more