Member since
07-18-2017
4
Posts
0
Kudos Received
0
Solutions
09-27-2018
07:22 AM
What is the port used by the NodeManager. Check the nodeManager is up and running and also logs for any issues reported. What is the Ambari version? there are known issues of false alerts being reported prior to Ambari 2.4/2.5 releases.
... View more
08-24-2017
10:49 AM
@Radhia BEZZINE The ErrorCode : 111
[ Connection refused] means that either there is no server or the connection is
blocked by firewall. Here the issue seems to be that the ambari-agent running on the server is unable to connect to the ndoemanager on the machine and perform a health-check. Points to check:
Check if the node-manager is
running on the Machine tconglobal.com and in port 8042. For
instance , you can use "netstat -tunlp |grep 8042" command, to know
the PID of the java process that is listening on this port and the status. Then
use command "ps -ef|grep <pid>" to know the actual process that is
listening on the port, if it is nodemanager. You can also check if the nodemanager is running with below command and validate the PID accessing the port. >ps -ef|grep nodemanager
Check if the Hostname is
correctly resolved from the server where the script is run. Run
telnet command from the machine, where script is executed from and check if
hostname is resolved and port is accessible. >telnet <hostname> <port>
Check the nodemanager log for
error message or issues logged , if any issue with nodemanager process.
... View more