- How to disable Link Checker or configure to mark links as valid in AEM
- Adobe Campaign: Queries against tsEvent take a long time
- How to reset the truststore in AEM
- Audience creation options
- How to look up Launch Darkly flags?
- “User name and password do not match” on login
- Adobe Campaign Standard: File Fails to upload if email entries contain “double”
- How to reset the admin password in AEM 6.3
- AEM redirects user back to http when accessed through SSL/TLS terminated Load Balancer | AEM
- Adobe Campaign: Is TLS 1.3 Supported?
- The Non-Apple SSO TV Provider Authentication Flow
- How to confirm if an MVPD is enabled for Apple SSO
- Change the minification engine for client libraries in AEM
- Adobe Campaign Standard: Can a collection within a collection be used within a JSON payload
- Error: Unable to parse expression ‘@registrationToken’
- How to debug client-side issues in the AEM Touch UI or Classic UI
- How to optimize Oak Lucene indexes to reduce indexing time
- Fix Inconsistencies in the repository when SegmentNotFound Issue is reported in AEM 6.x
- Marketing Channel Instances on Custom Links
- How to set the Oak login token session expiration
- Generating the missing renditions for AEM Assets
- SegmentNotFoundException and IllegalArgumentException
- How to delete the dispatcher cache without logging into to the Dispatcher server | AEM 6.x
- How to force a recompilation of all Sling scripts jsps, java, and sightly in AEM 6.4
- ACC: Workflow best practices - Configuration and monitoring
- Adobe Campaign: BAS-010015 Cannot open file error causing “DeliveryParts” failure
- How to enable secure cookies in AEM
- “Response is committed” error during page load in AEM6.x
- Adobe Campaign Standard: API updates to profiles and services are not being reflected
- Audience Manager to Campaign
- Adobe Campaign Standard: Imported File Transfer activities cannot change external account
- How to block IP addresses at the Apache HTTP Server level?
- Check and analyze if JCR session leaks in your AEM instance
- SAML IDP POST to /saml_login URL returns 403 response
- Permission denied error from java.io.File.createTempFile
- Discover and Build Audiences
- AEM Thread Dump Analysis
- javax.jcr.NamespaceException: Unknown namespace prefix error in AEM
- How can I confirm if SSO is enabled or disabled for my Channel?
- Publishing of references broken on Touch UI
- DRM Error 3324 MachineTokenInvalid Sub Error Code = 111
- How to capture SSAI and Original Manifests Simultaneously
- Adobe Campaign Standard: Substitution of address for transactional messages
- Migrate users, groups, and ACLs between AEM instances
- How to clone a TarMK instance in AEM
- Adobe Primetime Authentication - Most frequently used terms
- How to reindex a synchronous AEM index | AEM, Oak
- How to run a datastore consistency check via oak-run
Fix Inconsistencies in the repository when SegmentNotFound Issue is reported in AEM 6.x
Description
Observed SegmentNotFound Exceptions in the logs. For example:
-
*ERROR* FelixStartLevel org.apache.sling.event org.apache.sling.event.impl.jobs.queues.QueueManager(1431) The activate method has thrown an exception (org.apache.jackrabbit.oak.plugins.segment.SegmentNotFoundException: Segment da5bcb95-d00a-4c04-a9d9-0f10f2b14e5e not found)
-
*ERROR* pool-6-thread-3 org.apache.sling.commons.scheduler.impl.QuartzScheduler Exception during job execution of org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@1dc173f9 : Segment e669f30b-e886-4b7a-b161-56432601ec6b not found
org.apache.jackrabbit.oak.plugins.segment.SegmentNotFoundException: Segment e669f30b-e886-4b7a-b161-56432601ec6b not found
Environment
AEM 6.*
Cause
Due to some older issues in Oak or some inconsistencies in the repository, a segment can go missing and repository might be inconsistent.
Resolution
Run consistency check on the repository and find the last good revision healthy state and revert back to it. Please do the following:
-
Download a version of oak-run that matches your oak core version from https://mvnrepository.com/artifact/org.apache.jackrabbit/oak-run
-
To revert a corrupt segment store to its latest good state change into CQ’s working directory (the one containing the crx-quickstartfolder) and backup all files in ./crx-quickstart/repository/segmentstore/.
-
Run the consistency check,
java -Xmx6000m -jar oak-run-*.jar check --bin=-1 /path/to/crx-quickstart/repository/segmentstoreThis searches backwards through the revisions until it finds a consistent one:
Look for message like below:
main INFO o.a.j.o.p.s.f.t.ConsistencyChecker - Found latest good revision afdb922d-ba53-4a1b-aa1b-1cb044b535cf:234880
-
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.
-
Remove all ./crx-quickstart/repository/segmentstore/*.bak files.
-
Run checkpoint clean-up to remove orphaned checkpoints:
java -Xmx6000m -jar oak-run-*.jar checkpoints /path/to/crx-quickstart/repository/segmentstore rm-unreferenced -
Finally compact the repository:
java -Xmx6000m -jar oak-run-*.jar compact /path/to/crx-quickstart/repository/segmentstore/
Resources on adobe.com
Resources
Adobe Account
