由於repoinit錯誤,管道部署失敗
Adobe Experience Manager as a Cloud Service管道部署中的 buildImage 步驟經常因為登入buildImage.log的錯誤而發生錯誤,阻礙部署程式。 本文深入探討常見原因並提供解決方法。
說明 description
環境
Adobe Experience Manager作為Cloud Service
問題/症狀
管道部署在buildImage步驟期間失敗,且buildImage.log中看到以下錯誤(或類似錯誤):
錯誤
Apache Sling Repository Startup Thread #1] com.adobe.granite.repository.impl.SlingRepositoryManager Exception in a SlingRepositoryInitializer, SlingRepository service registration abortedjavax.jcr.RepositoryException: Applying repoinit operation failed despite retry; set loglevel to DEBUG to see all exceptions. Last exception message was: Failed to set ACL (javax.jcr.PathNotFoundException: Cannot set ACL on non-existent path <masked_path>) AclLine DENY {paths=[ <masked_path>] , privileges=[ jcr:all] }Caused by: org.apache.sling.jcr.repoinit.impl.RepoInitException: Failed to set ACL (javax.jcr.PathNotFoundException: Cannot set ACL on non-existent path <masked_path>) AclLine DENY {paths=[ <masked_path>] , privileges=[ jcr:all] }Caused by: javax.jcr.PathNotFoundException: Cannot set ACL on non-existent path <masked_path>
解決方法 resolution
若要修正此錯誤,請先在repoinit指令碼中建立<masked_path>,再指派ACL。
使用此參考檔案來進一步瞭解AEM as a Cloud Service的新架構。
原因:
執行repoinit指令碼時,<masked_path>可能不存在於Golden Master (專門的發佈節點)上。
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f