Hi,Our AEM 6.1 is not starting. The error.log file has the following warning and error error *WARN* [pool-7-thread-16] org.apache.jackrabbit.oak.plugins.index.lucene.IndexCopier Error occurred while copying file [_sf.cfs] from OakDirectory@78da42b4 lockFactory=org.apache.lucene.store.NoLockFactory@...
Hi,I created the dummy binary file and the log states that the CRX Repository is started. There were some additional errors related to oak:lucene and we are still unable to access the instance. I'll wait a bit and see if AEM ever comes up. I have a ticket open with Support. If they ever provide ...
Hi,The AEM was started with root and the datastore folder has rwx rights for root. I updated the rights to the datastore folder and its contents to 777, just to test if it's permission issues. After restarting AEM, I still see the same error.The full warnings and exceptions logged in error.log are...
Hi,We recently upgraded our CQ 5.6.1 to AEM 6.1 with Mongo DB. Our upgraded AEM 6.1 is throwing the "Missing Authentication Service" error. The error.log file is saying that a blob could not be found and a call was issued to shut down the repository. How do we delete the blob Id in Mongo DB (assu...
This is done. The fork settings was actually causing ldap-config not getting picked up. Setting nofork, we managed to get LDAP working. That is good enough, for now.
Hi,We are not able to successfully integrate CQ with LDAP. Based on the existing LDAP integration documentation, we are unable to get CQ to start when the following updates were done-updated repository.xml, per the steps outlined in the documentation-updated quickstart.bat to include the ldap config...
Hi,I have referred to the steps outlined in http://dev.day.com/docs/en/cq/current/core/administering/ldap_authentication.html to setup LDAP authentication. However, my CQ instance is not starting up at all. In the document, it says to update repository.xml and do the following-Under <SecurityManag...
Hi,We have 3 CQ environments: DEV, QA and PRD. Each environment has 2 authors and 2 publish CQ instances. Author instances to be clustered and publish instances are also to be clustered. We managed to configure the author and publish instances in DEV and QA to be in a cluster. However, when we g...
Hi,The issue was with the replication setup in our instances. Replication was incorrectly set, causing loops, which dragged down performance. After correcting this, performance is back to normal (comparable to a local machine hosted CQ)Thank You.