Member since 
    
	
		
		
		05-14-2018
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                33
            
            
                Posts
            
        
                2
            
            
                Kudos Received
            
        
                3
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 6905 | 12-04-2018 02:04 PM | |
| 4760 | 07-03-2018 03:27 PM | |
| 6869 | 05-29-2018 01:26 PM | 
			
    
	
		
		
		02-26-2023
	
		
		05:35 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 In case you have a valid kerberos ticket, kindly use --negotiate and submit again.  H!nt curl -X GET "https://master-servere.com:8090/ws/v43/cluster/apps/new-application" -H "accept: application/json" -k -v --negotiate -u admin     You may check for a valid Kerberos ticket using #klist  
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		01-26-2023
	
		
		12:40 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @TimothySpann @knarayanan can you please suggest how to solve this problem ? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		01-24-2023
	
		
		03:32 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 araujo can you please suggest ? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		01-24-2023
	
		
		03:15 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Dear @drewski7 please use this api to get the result.      curl -X POST "https://dev-cm.sever.com:7183/api/v43/clusters/cluster-name/services/service/commands/restart" -H "accept: application/json" -k -u admin:pssword  replace api v43 version with ur version and cluster name. if you dont have tls change 7183 with 7180 and remove -k option 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		11-03-2022
	
		
		11:11 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							  Hi All,     When we use MySQL 8 for HUE DB we get the below error      Unexpected error. Unable to verify the database connection    In Cloudera manager server logs :       2022-11-04 09:18:56,152 INFO scm-web-5325:com.cloudera.enterprise.JavaMelodyFacade: Exiting HTTP Operation: Method:POST, Path:/dbTestConn/checkConnectionResult, Status:200
2022-11-04 09:18:56,575 INFO CommandPusher-1:com.cloudera.server.cmf.CommandPusherThread: Acquired lease lock on DbCommand:547
2022-11-04 09:18:56,578 INFO CommandPusher-1:com.cloudera.cmf.service.AbstractOneOffHostCommand: Unsuccessful 'HueTestDatabaseConnection'
2022-11-04 09:18:56,578 INFO CommandPusher-1:com.cloudera.cmf.service.AbstractDbConnectionTestCommand: Command exited with code: 1
2022-11-04 09:18:56,578 INFO CommandPusher-1:com.cloudera.cmf.service.AbstractDbConnectionTestCommand: self.ensure_connection()
File "/opt/cloudera/parcels/CDH-7.1.6-1.cdh7.1.6.p0.10506313/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11.29-py2.7.egg/django/db/backends/base/base.py", line 213, in ensure_connection
self.connect()
File "/opt/cloudera/parcels/CDH-7.1.6-1.cdh7.1.6.p0.10506313/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11.29-py2.7.egg/django/db/utils.py", line 94, in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/opt/cloudera/parcels/CDH-7.1.6-1.cdh7.1.6.p0.10506313/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11.29-py2.7.egg/django/db/backends/base/base.py", line 213, in ensure_connection
self.connect()
File "/opt/cloudera/parcels/CDH-7.1.6-1.cdh7.1.6.p0.10506313/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11.29-py2.7.egg/django/db/backends/base/base.py", line 189, in connect
self.connection = self.get_new_connection(conn_params)
File "/opt/cloudera/parcels/CDH-7.1.6-1.cdh7.1.6.p0.10506313/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11.29-py2.7.egg/django/db/backends/mysql/base.py", line 274, in get_new_connection
conn = Database.connect(**conn_params)
File "/opt/cloudera/parcels/CDH-7.1.6-1.cdh7.1.6.p0.10506313/lib/hue/build/env/lib/python2.7/site-packages/MySQL_python-1.2.5-py2.7-linux-x86_64.egg/MySQLdb/__init__.py", line 81, in Connect
return Connection(*args, **kwargs)
File "/opt/cloudera/parcels/CDH-7.1.6-1.cdh7.1.6.p0.10506313/lib/hue/build/env/lib/python2.7/site-packages/MySQL_python-1.2.5-py2.7-linux-x86_64.egg/MySQLdb/connections.py", line 193, in __init__
super(Connection, self).__init__(*args, **kwargs2)
django.db.utils.OperationalError: (2059, "Authentication plugin 'caching_sha2_password' cannot be loaded: /usr/lib64/mysql/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory")
2022-11-04 09:18:56,578 ERROR CommandPusher-1:com.cloudera.cmf.model.DbCommand: Command 547(HueTestDatabaseConnection) has completed. finalstate:FINISHED, success:false, msg:Unexpected error. Unable to verify database connection.
2022-11-04 09:18:56,578 INFO CommandPusher-1:com.cloudera.cmf.command.components.CommandStorage: Invoked delete temp files for command:DbCommand{id=547, name=HueTestDatabaseConnection, host=server} at dir:/var/lib/cloudera-scm-server/temp/commands/547
2022-11-04 09:18:59,140 INFO scm-web-5335:com.cloudera.enterprise.JavaMelodyFacade: Entering HTTP Operation: Method:POST, Path:/dbTestConn/checkConnectionResult         What causes this error?     MySQL 8 supports a new authentication method based on improved stronger SH256-based password methods. When you install MySQL 8, this is the new default authentication method (although this can be changed during MySQL server installation).  As MySQL 8 is still relatively new, depending upon your Perl environment, Perl itself (or rather the driver that Perl uses to connect to a MySQL server) may not yet be compatible with the new authentication method in MySQL 8. When this occurs, an "Authentication plugin 'caching_sha2_password' cannot be loaded" error is produced.     How to fix this error?     To resolve this error, and revert your MySQL server back to using "legacy" authentication, you'll need to login to your MySQL server and issue the following command:  ALTER USER 'yourusername'@'localhost' IDENTIFIED WITH mysql_native_password BY 'yourpassword';  (where "yourusername" is the MySQL user account you specified your HUE service to use, and "yourpassword" is the corresponding MySQL user account password)        Solution :  1) alter user 'hue'@'%' IDENTIFIED WITH mysql_native_password BY 'HUEUSERPASSWORD';      OR     2)  You can update your MySQL configuration to use: [mysqld] default_authentication_plugin=mysql_native_password Then alter the user to use "mysql_native_password" with the following sql statement (for the hue MySQL user you created): #ALTER USER 'user'@'host' IDENTIFIED WITH mysql_native_password BY 'password';     DISCLAIMER: This article is contributed by an external user. The steps may not be verified by Cloudera and may not be applicable for all use cases and may be very specific to a particular distribution. Please follow with caution and at your own risk. If needed, raise a support case to get confirmation. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
	
					
			
		
	
	
	
	
				
		
	
	
			
    
	
		
		
		02-16-2022
	
		
		04:40 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @drgenious  please change the dropdown option then you can   1) Document ---> Actions   2) then select shell and write your script.   3) if this option is not coming then check with the Cloudera patch.           
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-01-2021
	
		
		01:36 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hello @khanarshadazmat ,     We do not have a direct method to get the CM Server and Agent version like we have in java -version.     However, you can follow some of the below workarounds to get the required result:  1_). using below command  # hdfs version  # hadoop version  2_). version info available at "/opt/cloudera/parcels/<CDH>/lib/hadoop/cloudera/cdh_version.properties"     Let me know if this helps!     Cheers!  Was your question answered? Make sure to mark the answer as the accepted solution.  If you find a reply useful, say thanks by clicking on the thumbs up button. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		05-31-2021
	
		
		12:42 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hello @khanarshadazmat ,     You may get the role information using CM API for HDFS service.     API:   https://archive.cloudera.com/cm7/7.2.4/generic/jar/cm_api/apidocs/resource_RolesResource.html#resource_RolesResource_ClustersResourceV43_ServicesResourceV42_RolesResourceV41_readRoles_GET     See the below example for a better understanding:  • When I execute the above API, I would get the below details for HDFS service:   "name" : "HDFS-1-NAMENODE-cb7144bc695976e34cfbaaf26c176d21",
    "type" : "NAMENODE",
    "serviceRef" : {
      "clusterName" : "Cluster 1",
      "serviceName" : "HDFS-1",
      "serviceDisplayName" : "HDFS-1",
      "serviceType" : "HDFS"
    },  ...
    "roleState" : "STARTED",
    "healthSummary" : "GOOD",
    "configStalenessStatus" : "FRESH",
    "haStatus" : "STANDBY",
    "maintenanceMode" : false,
    "commissionState" : "COMMISSIONED",
    "roleConfigGroupRef" : {
      "roleConfigGroupName" : "HDFS-1-NAMENODE-BASE"
    },  • and, for the second namenode, I'll get something as below:  "name" : "HDFS-1-NAMENODE-b1d777dd6714507397225b07ea9057ce",
    "type" : "NAMENODE",
    "serviceRef" : {
      "clusterName" : "Cluster 1",
      "serviceName" : "HDFS-1",
      "serviceDisplayName" : "HDFS-1",
      "serviceType" : "HDFS"
    },  ...     "roleState" : "STARTED",
    "healthSummary" : "GOOD",
    "configStalenessStatus" : "FRESH",
    "haStatus" : "ACTIVE",
    "maintenanceMode" : false,
    "commissionState" : "COMMISSIONED",
    "roleConfigGroupRef" : {
      "roleConfigGroupName" : "HDFS-1-NAMENODE-BASE"
    },
    "entityStatus" : "GOOD_HEALTH"  • In both the above examples, check for the keyword "haStatus". The namenode with haStatus as Active would be your Active Namenode.      Let me know if this helps.     Cheers!  Was your question answered? Make sure to mark the answer as the accepted solution.  If you find a reply useful, say thanks by clicking on the thumbs up button. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		01-12-2019
	
		
		07:41 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 @Divya Thaore    If you are on HDP 2.6.x the login using credentials: root / hadoop  and you get the prompt  Did you run this command after   ambari-admin-password-reset  HTH 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-05-2018
	
		
		06:32 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @Arshadullah Khan  Thanks for the suggestion issue got resolved.  Downloaded and Copied jar to /usr/hdp/current/atlas-server/hook/hive/atlas-hive-plugin-impl and issue got resolved after running import-hive.sh script.  Now we are able to see Hive_db and Hive_tables in Atlas Web UI.  Thanks & regards,  Owez 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		 
        













