Member since 
    
	
		
		
		05-27-2014
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                1499
            
            
                Posts
            
        
                77
            
            
                Kudos Received
            
        
                44
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 3837 | 05-04-2020 11:56 AM | |
| 2497 | 05-01-2020 10:43 AM | |
| 2567 | 04-28-2020 03:11 PM | |
| 4325 | 04-28-2020 10:35 AM | |
| 3312 | 04-13-2020 10:44 AM | 
			
    
	
		
		
		03-08-2019
	
		
		10:11 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Hi @krieger ,     Could you please run this command and see if it returns any result?  # grep '^[[:blank:]]' /etc/cloudera-scm-agent/config.ini  Above command can rule out if there are any leading spaces in the /etc/cloudera-scm-agent/config.ini. See below example. The example showing that there's a leading space in front of server_port=7182. This will cause the config parser to fail.  # grep '^[[:blank:]]' /etc/cloudera-scm-agent/config.ini   server_port=7182     From the content you pasted, I feel there is a leading space before the line "use_tls=0". If the command does return the line, could you please remove the leading space in the line and then try to restart agent again?     Thanks and hope this helps,  Li 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-07-2019
	
		
		09:51 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @krieger ,     Could you please check if /etc/cloudera-scm-agent/config.ini exists on the VM1? If it does, can you please send the content for us to review?      Thanks,  Li 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-05-2019
	
		
		02:45 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							Have you tried to restart the VM? I will check internally with team and see if we can provide any further insights. Thanks!
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-04-2019
	
		
		03:40 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Hi @unix196,     I think you are right about the the host is not in the cluster.      You may have hosts that are already "managed" but are not part of a cluster. You can have managed hosts that are not part of a cluster when you have added hosts to Cloudera Manager either through the Add Host wizard, or by manually installing the Cloudera Manager agent onto hosts where you have not install any other services. This will also be the case if you remove all services from a host so that it no longer is part of a cluster.     See more details about this in documentation here.     Thanks,  Li 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-04-2019
	
		
		02:17 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @krieger,     Since it looks like agent is not running correctly, I suggest you trying to do "Hard Stopping and Restarting Agents" by following below documentation:  https://www.cloudera.com/documentation/enterprise/5-13-x/topics/cm_ag_agents.html#cmug_topic_14_4__section_kmt_zxs_v4     Please note: hard restart will kill all running managed service processes on the host(s) where the command is run.     Thanks,  Li 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-01-2019
	
		
		03:11 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @krieger,     Thanks for your response.     I was not able to see clear error messages from the VM1 agent log. Can you please run below commands on VM1 host and send us the output?     1. ps -ef | grep cmf-agent     2. service cloudera-scm-agent status     Thanks,  Li 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-01-2019
	
		
		10:28 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @krieger,        We need some more details to assist on this issue. Just by upgrading to Spark 2.3 should not cause issue with HMON.     Could you please answer a few questions:  1) What is the CM/CDH version you have in the lab?  2) Where does HMON role install? On which host? If you can, send us a screenshot of the CM hosts page.  3) It sounds like VM2 and VM3 are working fine, but not VM1. Is VM1 CM agent running or not?  4) Is HMON showing down/stopped from CM UI? If you can, send us a screenshot of CM homepage.     Can you please also send us the agent log from a non-working one and working one so we can do some investigation/comparsion to find out why the agent is not starting on one of the hosts.     Thanks,  Li 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		02-27-2019
	
		
		11:47 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							Great to hear the issue got resolved! Thanks for the feedback!
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		02-26-2019
	
		
		03:29 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		2 Kudos
		
	
				
		
	
		
					
							 Hi @prismalytics,     As documented in the Apache Github, we need to execute with hadoop jar command for a file on HDFS filesystem.  ---  #Run from hadoop  See Commands Usage for command to use  hadoop jar ./parquet-tools-<VERSION>.jar <command> my_parquet_file.lzo.parquet  ---     So could you please execute hadoop jar command as following?     hadoop jar /opt/cloudera/parcels/<CDH-VERSION>/jars/parquet-tools-<VERSION>.jar <command> <hdfs path to parquet file>     e.g.  hadoop jar /opt/cloudera/parcels/CDH-6.1.0-1.cdh6.1.0.p0.770702/jars/parquet-tools-1.9.0-cdh6.1.0.jar cat hdfs://tmp/1.parquet     Thanks and hope this helps,  Li 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		02-26-2019
	
		
		02:38 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @Thrisha,     From the same link you pasted, it says:  Python - Cloudera Enterprise 6, with the exception of Hue, is supported on the Python version that is included in the operating system by default, as well as higher versions, but is not compatible with Python 3.0 or higher.  For example, Cloudera Enterprise 6 requires Python 2.6 or higher on RHEL 6 compatible operating systems, but requires Python 2.7 or higher on RHEL 7 compatible operating systems.  Hue in CDH 6 requires Python 2.7 or higher on all operating systems. For RHEL 6 compatible operating systems running Hue, you must manually install Python 2.7.     Based on above, you need to follow the link to manually install Python 2.7 for Hue to work in CDH 6.     Thanks and hope this helps,  Li 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		 
        













