Member since 
    
	
		
		
		08-16-2016
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                642
            
            
                Posts
            
        
                131
            
            
                Kudos Received
            
        
                68
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 3970 | 10-13-2017 09:42 PM | |
| 7458 | 09-14-2017 11:15 AM | |
| 3789 | 09-13-2017 10:35 PM | |
| 6019 | 09-13-2017 10:25 PM | |
| 6592 | 09-13-2017 10:05 PM | 
			
    
	
		
		
		07-20-2017
	
		
		08:21 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							https://community.cloudera.com/t5/Cloudera-Manager-Installation/how-to-rollback-cloudera-manager-tls-configuration-without-UI/m-p/46484/highlight/true#M8455
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-20-2017
	
		
		08:18 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Aww I can work with password must not be null.  I assume that the keytool command did not prompt you for a password.  This means that the Java keystore and possible the private key are not password protected.  Most service require that a password be set.  The challenge here is whether you specified a password in the Cloudera Manager configs.  If yes, and you recall it, you can recreate the key and cert in the JKS with that password and bring CM up.     Note: the key and JKS password must be the same, CM assumes they are.     To revert, you will need to log into the CM database and manually modify it.  Let me track down those instructions. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-19-2017
	
		
		08:10 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							I am not sure about the first portion but the second bit seems to indicate that you did not upgrade your Hive schema during the upgrade process. You will need to stop Hive. In CM, go to the Hive process, the Action menu should have an Upgrade Hive Metastore Database Schema option. Run that to see if it clears up the warning.
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-19-2017
	
		
		07:58 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							I do not beyond the Cloudera docs. I have not seen the second error. The Google translation I got was FileNotFoundException (is a record).    To validate that the keystore is good can you run the below command.    keytool -v -list -keystore /var/lib/cloudera-scm-server/.keystore
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-19-2017
	
		
		05:33 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							Yes. Move it and ensure that the user running the cloudera-scm-server has read access to it.
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-18-2017
	
		
		03:34 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							http://community.cloudera.com/t5/Community-News-Release/ANNOUNCE-Cloudera-Distribution-of-Apache-Spark-2-2-Release-1/m-p/57600
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-18-2017
	
		
		09:21 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Did you read and complete Step 0?     https://www.cloudera.com/documentation/enterprise/5-11-x/topics/cm_sg_tls_browser.html#xd_583c10bfdbd326ba-7dae4aa6-147c30d0933--7a61     This will have you create or obtain a server certificate and put it in a Java keystore.  If yes, is it located in the path listed in the exception, /var/lib/cloudera-scm-server/.keystore?  If yes, is it owned by the user that is trying to launch the cloudera-scm-server process, should be cloudera-scm? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-17-2017
	
		
		01:53 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							All services log that message about the supervisor.conf (not 100% is this is after kerberization or not). You can safely ignore it.    Check the stderr as well as the stdout, also see if there are logs under /var/log/*kafka* on the hosts running the Kafka brokers. That may contain more information and some exceptions and/or errors.    Did you do any config changes to Kafka after you installed it?
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-17-2017
	
		
		11:30 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							The only product that installs postgresql is the Cloudera Manager installer but it doesn't manage it. You will need to check, manage, and troubleshoot it from the command line.    It is possible that something cause postgresql to fail after you installed HMS.
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		07-17-2017
	
		
		11:12 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							Search for all of the javax properties, grep javax -B 1 -A 2.    DON'T POST THE ABOVE as it will likely container the uname and pword for your DB.    Check that postgresql is running on that host on port 7432 and that the 'hive' db exist and that you can log in with the account and password in the Hive configs.
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		 
        













