Support Questions
Find answers, ask questions, and share your expertise
Announcements
Check out our newest addition to the community, the Cloudera Innovation Accelerator group hub.

Cloudera manager failed to regenerate missing credentials

New Contributor

Failed to regenerate the missing credentials in cm, the error log is as follows:

SHUAIPENG_0-1631863646055.jpegSHUAIPENG_1-1631863672800.jpeg

Key log information:

com.cloudera.cmf.command.CmdExecException: java.lang.IllegalArgumentException

Caused by: java.lang.IllegalArgumentException

ERROR CommandPusher-1:com.cloudera.cmf.model.DbCommand: Command 61246(GenerateCredentials) has completed. finalstate: CANCELLED,success:false,msg:java.lang.IllegalArgumentException

 

It is worth noting that the import of kerberos account manager credentials in CM is successful.

And the keytab in the /var/run/cloudera-scm-server directory can be kinit successfully

 

/var/log/cloudera-scm-server/cloudera-scm-server.log The log error is as follows:

SHUAIPENG_2-1631864318179.jpeg

SHUAIPENG_3-1631864338390.jpeg

Key log information:

ERROR Staleness-Detector-1: com.cloudera.cmf.service.config.components.ProcessStalenessDetector: Failed to check staleness for service client configs : DbService{id=75,name=atlas}

 

com.cloudera.cmf.service.config.ConfigGenException: Failed to generate client configs

 

Caused by: java.lang.RuntimeException: com.cloudera.cmf.service.config.ConfigGenException: Failed to generate client configs

 

Caused by: java.lang.RuntimeException: com.cloudera.cmf.service.config.ConfigGenException: No dependent roles found

 

Caused by:com.cloudera.cmf.service.config.ConfigGenException: No dependent roles found

 

Do you technical engineers have any solutions? Grateful.

 

 

 

 

1 ACCEPTED SOLUTION

New Contributor

@GangWar 

 

Hello,

This problem has been solved because the atlas service has been deleted, but there are dependencies in other service configurations that have not been cleared.

 

This can also be seen from the log:

ERROR Staleness-Detector-1: com.cloudera.cmf.service.config.components.ProcessStalenessDetector: Failed to check staleness for service client configs : DbService{id=75,name=atlas}

 

After adding the deleted atlas service back, I succeeded in generating the missing Kerberos credentials again.

In short, thank you very much for your reply and wish you a happy life!

View solution in original post

2 REPLIES 2

@SHUAIPENG  I would suggest to deploy Kerberos Client Configuration once from CM > Cluster > Action menu and Also restart the CM server after that and try again to generate the credentials and see how it goes. 


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.

New Contributor

@GangWar 

 

Hello,

This problem has been solved because the atlas service has been deleted, but there are dependencies in other service configurations that have not been cleared.

 

This can also be seen from the log:

ERROR Staleness-Detector-1: com.cloudera.cmf.service.config.components.ProcessStalenessDetector: Failed to check staleness for service client configs : DbService{id=75,name=atlas}

 

After adding the deleted atlas service back, I succeeded in generating the missing Kerberos credentials again.

In short, thank you very much for your reply and wish you a happy life!