Member since 
    
	
		
		
		03-14-2016
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                4721
            
            
                Posts
            
        
                1111
            
            
                Kudos Received
            
        
                874
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 2490 | 04-27-2020 03:48 AM | |
| 4962 | 04-26-2020 06:18 PM | |
| 4042 | 04-26-2020 06:05 PM | |
| 3279 | 04-13-2020 08:53 PM | |
| 4992 | 03-31-2020 02:10 AM | 
			
    
	
		
		
		08-20-2019
	
		
		03:25 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Hi,     We don't share personal information like contacts, As you are facing Ambari Server issue and Agents issue is resolved, Please open a new question for Ambari Server, Also, check the Ambari Server logs you see some exceptions, attach those exceptions. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		08-19-2019
	
		
		06:47 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @kwabstian53   Also as we see that the webhdfs call is actually failing with 404 (resource not found) hence it will be good to find which resource is it ... gthen later we can chekc why it does not exist on HDFS>  We can try grepping the "webhdfs' in the Active NameNode HDFS Audit log exactly when we notice  'HDFS Service check failure'      We can grep the logs as following:  # grep 'proto\=webhdfs' /var/log/hadoop/hdfs/hdfs-audit.log     So when the hdfs service check will fail then exactly at the same time we will know why it failed and for which resource.  .    
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		08-19-2019
	
		
		06:08 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @Koffi   It may or may not be related to the JDK.  As currently based on the error it looks more related to the issue with the SSL keystore/certificate configured for the NodeManager. As we see the following cause of failure.  Caused by: javax.crypto.BadPaddingException: Given final block not properly padded
	at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:989)
	at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:845)    - Can you please let us know how you actually configured the SSL for NodeManager can you please share the exact details / properties that you changed in YARN config?  - Also can you please check if you are able to list the keystore/certificate properly without any issue?  - It will be good to know how did you generate the certificates Self Signed or CA Signed?  - When was it working earlier? Did you recently configure the keystore/certificate for NodeManager? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		08-19-2019
	
		
		11:05 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @jsensharma,     Thank you very much for your prompt reply and clear answer.     The reason for wanting to downgrade was to avoid a complete re-install (for logistical reasons). The version should have been 2.6.2.0 per spec request. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		08-19-2019
	
		
		06:53 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @vinith_alampall   As you are getting this error:  sh: 0: Can't open ./start-yarn.sh     Hence you should check couple of things:     1. Is this file existing in the current directory?  # cd /PATH/TO
# ls -lart  /PATH/TO/start-yarn.sh  2. What is the permission on the file? Can the current user read/execute it?  # chmod  a+x  /PATH/TO/start-yarn.sh
# which sh
# sh -x /PATH/TO/start-yarn.sh     Please replace the '/PATH/TO" with the actual path of the mentioned script.    .          
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		08-19-2019
	
		
		01:25 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							Ambari-server restart Using python /usr/bin/python Restarting ambari-server Ambari Server is not running Ambari Server running with administrator privileges. Organizing resource files at /var/lib/ambari-server/resources... Ambari database consistency check started... Server PID at: /var/run/ambari-server/ambari-server.pid Server out at: /var/log/ambari-server/ambari-server.out Server log at: /var/log/ambari-server/ambari-server.log Waiting for server start...........................................ERROR: Exiting with exit code -1. REASON: Ambari Server java process has stopped. Please check the logs for more information.
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-26-2019
	
		
		09:10 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Think I found the problem, TLDR: firewalld (nodes running on centos7) was still running, when should be disabled on HDP clusters.  From another community post:   For Ambari to communicate during setup with the hosts it deploys to and manages, certain ports must be open and available. The easiest way to do this is to temporarily disable iptables, as follows:   systemctl disable firewalld    service firewalld stop    So apparently  iptables  and  firewalld  need to be disabled across the cluster (supporting docs can be found here, I only disabled them on the Ambari installation node). After stopping these services across the cluster (I recommend using clush), was able to run the upload job without incident. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-24-2019
	
		
		12:57 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 See comments / discussion of accepted answer for the steps that ultimately solved the problem. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-23-2019
	
		
		12:50 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @Jay Kumar SenSharma  Following this post helped pass the Ambari connection test, thanks. Was able to find a bit of explaination for this fix here: https://stackoverflow.com/a/47558163/8236733. However, contrary to what your answer seems to imply, despite the connection test now passing, still getting the  # mysql -u root -p -h <some remote cluster node>
ERROR 2003 (HY000): Can't connect to MySQL server on '<theremote cluster node>' (111)  errors. Any suggestions?     
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-12-2019
	
		
		08:20 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 this is the error   
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		 
         
					
				













