In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-17 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >
Share
Shulou(Shulou.com)06/01 Report--
Ambari open keranthus error add_principal: analysis of the main body format is not correct how to solve, many novices are not very clear about this, in order to help you solve this problem, the following small series will explain in detail for everyone, there are people who need this can learn, I hope you can gain something.
problem description
When ambari opens kersei, create principals after stop services gives the following error:
Verify that the error is mycluster-112020@admin/admin@OCDP.COM This principal syntax is illegal
kadmin.local: addprinc mycluster-112020@admin/admin@OCDP.COMadd_principal: Malformed representation of principal while parsing principalusage: add_principal [options] principal options are: [-randkey|-nokey] [-x db_princ_args]* [-expire expdate] [-pwexpire pwexpdate] [-maxlife maxtixlife] [-kvno kvno] [-policy policy] [-clearpolicy] [-pw password] [-maxrenewlife maxrenewlife] [-e keysaltlist] [{+|-}attribute] attributes are: allow_postdated allow_forwardable allow_tgs_req allow_renewable allow_proxiable allow_dup_skey allow_tix requires_preauth requires_hwauth needchange allow_svr password_changing_service ok_as_delegate ok_to_auth_as_delegate no_auth_data_required lockdown_keyswhere, [-x db_princ_args]* - any number of database specific arguments. Look at each database documentation for supported arguments
So why would ambari give us such a Principal name? It's a bit strange.
The ambari database has four tables about keranthus, as shown below:
Error records are found in the following three tables:
solutions
ambari will go to the database to get the principal name. Now this abnormal name causes an error, so delete the relevant records in the database.
These tables have foreign key checking, so turn off foreign key checking before deleting them, and restore them after deleting them.
--turn off foreign key checking show global variables like "%foreign_key_checks%";set global foreign_key_checks=0;show global variables like "%foreign_key_checks%";--delete keroros three tables error reported principldelete from keroros_keytab where keytab_path="/etc/security/keytabs/kerberos.service_check.112020.keytab";delete from keroros_principal where principal_name="mycluster-112020@admin/admin@ ODP.COM"; delete from keranthus_keytab_principal where keytab_path="/etc/security/keytabs/kerberos.service_check.112020.keytab";--restore foreign key checks set global foreign_key_checks=1;show global variables like "%foreign_key_checks%";
Try again keranthus open normal
Did reading the above help you? If you still want to have further understanding of related knowledge or read more related articles, please pay attention to the industry information channel, thank you for your support.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.