Chuyển đến nội dung chính

[CQ/AEM] SegmentNotFoundException

Issue:
When we see the error "org.apache.jackrabbit.oak.plugins.segment.SegmentNotFoundException: Segment 6e0a804f-0d75-48a8-a579-ebf34e58e763 not found" one day, and you can not open any pages, or can access neither crx nor console.

Solution:
We can use oak runnable to check and restore the last good revision into Oak's working directory.

Tool: Oak-run Tool (http://mvnrepository.com/artifact/org.apache.jackrabbit/oak-run)

Check more from http://cqhints.blogspot.com/2015/07/cq6-system-maintaining-repository.html

Step to restore Oak's working directory:
1. Backup all files in ./crx-quickstart/repository/segmentstore/.

2. Run the consistency check
java -jar oak-run-*.jar check -d1 --bin=-1 -p crx-quickstart/repository/segmentstore/

It will search backwards through the revisions until it finds a consistent one:
18:01:51.336 [main] INFO o.a.j.o.p.s.f.t.ConsistencyChecker - Found latest good revision ca9c71ae-1941-4a2d-aaed-c444db7a4c6d:260120

3. Revert the repository to this revision by editing ./crx-quickstart/repository/segmentstore/journal.log and deleting all lines after the line containing the latest good revision.

4. Remove all ./crx-quickstart/repository/segmentstore/*.bak files.

5. Run checkpoint clean-up to remove orphaned checkpoints:
java -jar oak-run-*.jar checkpoints ./crx-quickstart/repository/segmentstore rm-unreferenced

6. Finally compact the repository:
java -jar oak-run-*.jar compact ./crx-quickstart/repository/segmentstore/

If you are using AEM6.0, please do below steps before starting cleanup

Step 1: Download the service pack from Adobe package share (https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/companies/public/adobe/packages/aem600/servicepack/AEM-6.0-Service-Pack). Log on to this link, go to “ASSETS” tab and click on “Download to disk: AEM 6.0 Service Pack 1-1.0” link. This should download the service pack to your local system.
Step 2: Restart the AEM server.
Step 3: Once the AEM server is up, go to package manager using “http:<hostname>:<portname>/crx/packmgr” and upload the “AEM 6.0 Service Pack 1-1.0.zip” file downloaded from the package share and click on install.
Step 4: Wait until the full package is installed.
Step 5: Run a check on the instance if everything is working as expected.


Ref: https://github.com/apache/jackrabbit-oak/blob/trunk/oak-run/README.md#check

Nhận xét

Bài đăng phổ biến từ blog này

[PERFORMANCE] Adobe WEM/CQ performance tuning

Adobe WEM/CQ performance tuning Contents Caching-related configurations CRX Bundle cache CRX Search index handler (Lucene) cache Tar PM index cache Scalability Maintenance Optimizing Tar Files (for Tar Persistence Manager) Data Store Garbage Collection Main documentation you should consult first: http://dev.day.com/docs/en/cq/current/deploying/performance.html http://dev.day.com/content/kb/home/cq5/CQ5Troubleshooting/performancetuningtips.html Caching-related configurations CRX Bundle cache CRX caches bundles, consisting of a node with all its properties. This is used by all bundle-based Persistence Managers. The default size of BundleCache is 8 MB. If this is too small it can cause an excessive number of read-accesses to the underlying persistence layer. Set the bundleCacheSize to something larger than the default. See more here: http://dev.day.com/docs/en/cq/current/deploying/performance.html#CRX%20Bundle%20Cache CRX Search index handler (Lucene...

How to custom CQ Login Module

In order to manage the login process in our project, we will use a custom CQ Login Module. We will admit the root URL of CQ instance is: http://localhost:4502/ . This value may change depending of your environment. The %CQ_HOME% variable we will mention refers to the CQ install path. It admits you have defined %CQ_HOME% as an environment variable. 1.         Update the repository definitions The login module must be referenced in the repository definitions. You have to edit the next file: %CQ_HOME%/crx-quickstart/repository/repository.xml Do a copy of repository.xml to repository.xml.original In repostiory.xml, replace  security  part of repository.xml with following: <Security appName="com.day.crx">         <SecurityManager class="com.day.crx.core.CRXSecurityManager"> <WorkspaceAccessManager class="org.apache.jackrabbit.core.security.simple.SimpleWorkspaceAccessManager"/>  ...

[DAM] Custom DAM management / Add 'Alt' into images

Issue: We need, for each asset to be able to edit the ‘alt’ text. The ‘alt’ text must be used on the site each time an asset is displayed. When displaying an asset, the mechanism is the following : -       Get the Locale from the request -       When getting the asset, get the associated Alt property corresponding to the locale. -       Populate the alt attribute with this value. Resolution: To achieve this, we can customize the DAM Asset Editor. The AssetEditor is the form used to input asset properties and metadata. Below is a screenshot of a customized form with four “alt” input (for four different locales). The DAM uses the following nodes to render Asset Editor forms: -       /libs/dam/content/asseteditors/formitems -       /libs/dam/content/asseteditors/images/formitems -      ...