Member since 
    
	
		
		
		07-08-2013
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                548
            
            
                Posts
            
        
                59
            
            
                Kudos Received
            
        
                53
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 3381 | 08-17-2019 04:05 PM | |
| 3155 | 07-26-2019 12:18 AM | |
| 10205 | 07-17-2019 09:20 AM | |
| 5915 | 06-18-2018 03:38 AM | |
| 15257 | 04-06-2018 07:13 AM | 
			
    
	
		
		
		06-29-2016
	
		
		02:55 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 The backup command is RDBMS vendor specific and it depends on your database server (PostgresSQL, MySQL, or Oracle)   Any idea what is your database type? If you're unsure use the below command to confirm.  # grep -oE 'db.(type|host)=.*' /etc/cloudera-scm-server/db.properties     If it's embedded/Postgres, use the guide 'Backing Up PostgreSQL Databases' [1]        [1] http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ag_backup_dbs.html#cmig_topic_5_6_3 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-20-2016
	
		
		12:46 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Of course [1]           [1] http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_create_local_package_repo.html 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-20-2016
	
		
		07:43 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 > We were intially provided the below URLs to be placed under /etc/yum.repos.d under cloudera-manager.repo 
 > ... we in the bank cannot connect to outside URLs due to security issue 
 You will need to contact the person who created your internal repo [1] to create a repo for Redhat/CentOS 7. 
 Effectively your baseurl = .../redhat/7/...  <== point to Redhat/CentOS 7 packages internal url 
 just an example (notice the 7) ==> baseurl=[base URL] 
   
   
 [1] baseurl=[base url]   
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-17-2016
	
		
		01:00 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 That's the CM Server nagging that your /etc/cloudera-scm-server/db.properties has possibly default/unconfigured configuration*. Review the installation guide in my previous link, and make sure you have a database for CM Server to connect to. If your installation is a playgroun/proof of concept (not intended for production) use the embedded DB guide [1].     [1] http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_embed_pstgrs.html     NB: *The default /etc/cloudera-scm-server/db.properties is set to connnect to a local MySQL database, the error suggests that it's unable to locae the relevant mysql JDBC connector (jar file) 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-17-2016
	
		
		06:48 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Make sense, the package you've downloaded and attempted to install is for RHEL/CentOS 6     [root@lsdne9sgeot cloudera]# yum --nogpgcheck localinstall cloudera-manager-agent-5.7.0-1.cm570.p0.76.el6.x86_64.rpm     Please follow the Installation Guide [1], make sure that you're using the steps specifically for RHEL/CentOS 7 (.el7.) or use the CM 5.7.0 packages intended for RHEL/CentOS 7 - cloudera-manager-agent-5.7.0-1.cm570.p0.76.el7.x86_64.rpm [2]        [1] http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_install_path_b.html#id_gzv_zmm_25  [2] https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.7.0/RPMS/x86_64/ 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-17-2016
	
		
		05:47 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 We have added several improvements in our latest CM 5.7.x that handles OptimisticLockExceptions more grecefully, please consider upgrading your CM to the latest release. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-17-2016
	
		
		05:36 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Here's an example;     $ curl -v -X PUT -u admin:admin -H 'Content-Type:application/json' -d '{ "password" : "new_password" }' 'http://cm.example.com:7180/api/v12/users/type_the_username_here'     [1] https://cloudera.github.io/cm_api/apidocs/v12/ns0_apiUser.html 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-17-2016
	
		
		05:23 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 What OS are you installing this on? The list of depenent packages returns .el7. and you're installing .el6. CM packages/rpms. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-14-2016
	
		
		12:56 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 If you're using Cloudera Manager Server 5.7.0, please consider upgrading to 5.7.1 where the issue is now resolved.     see relevant know issue list [1]     Error creating bean
Occasionally, some users encountered the message Error creating bean with name 'newServiceHandlerRegistry' in the Cloudera Manager Admin Console. This issue has been resolved.
  [1] http://www.cloudera.com/documentation/enterprise/release-notes/topics/cm_rn_fixed_issues.html#concept_dph_sxc_wv    
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-02-2016
	
		
		04:39 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 The services you're referring have their own user/service credentials with /sbin/nologin shell (check /etc/passwd) i.e. for HDFS is hdfs user, which also used to start the hdfs service daemon. Overall there won't be any impact, unless you specifically associated 'System User' [1] with 'cloudera' user to be used with the service daemon you've mentioned.        [1] search for "System User"   http://www.cloudera.com/documentation/enterprise/latest/topics/cm_props_cdh570_hdfs.html#concept_axh_o2n_yk 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		 
        













