kinit: Included profile directory could not be read while initializing Kerberos 5 library
1、查看/etc/krb5.conf下的includedir是否存在 2、查看includedir對應的路徑是否正確 如圖： 此時includedir中的路徑下爲空，因此讀取不到Kerberos的配置，會報標題中的錯誤 解決：註釋includedir即可
相關文章
- 1. Error getting authority: Error initializing authority: Could not connect: No such file or directory
- 2. Could not find profile: TwoOrgsOrdererGenesis.
- 3. CLIENT_0004:Unable to find valid Kerberos ticket cache (kinit)
- 4. Crontab could not create directory .ssh
- 5. Ubuntu18.04-The list of sources could not be read-fix it
- 6. The requested profile "pom.xml" could not be activated because it does not exist
- 7. [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
- 8. The requested profile "pom.xml" could not be activated because it does not exist.
- 9. The requested profile 「pom.xml「 could not be activated because it does not e
- 10. eclipase Could not read settings.xml
- 更多相關文章...
- • PHP 5 Directory 函數 - PHP參考手冊
- • ASP Read 方法 - ASP 教程
- • JDK13 GA發佈：5大特性解讀
- • Java Agent入門實戰（一）-Instrumentation介紹與使用
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
歡迎關注本站公眾號,獲取更多信息
相關文章
- 1. Error getting authority: Error initializing authority: Could not connect: No such file or directory
- 2. Could not find profile: TwoOrgsOrdererGenesis.
- 3. CLIENT_0004:Unable to find valid Kerberos ticket cache (kinit)
- 4. Crontab could not create directory .ssh
- 5. Ubuntu18.04-The list of sources could not be read-fix it
- 6. The requested profile "pom.xml" could not be activated because it does not exist
- 7. [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
- 8. The requested profile "pom.xml" could not be activated because it does not exist.
- 9. The requested profile 「pom.xml「 could not be activated because it does not e
- 10. eclipase Could not read settings.xml