troubleshoot-replication

Diagnose and fix AEM 6.5 LTS replication issues across author and publish environments.

1|Updated Oct 7, 2024
One-click install
npx skills add https://github.com/valithedge/etisalatedge --skill troubleshoot-replication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-replication
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/troubleshoot-replication
Command: npx skills add https://github.com/valithedge/etisalatedge --skill troubleshoot-replication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix common AEM 6.5 LTS replication issues across author and publish instances, including blocked queues, connectivity failures, authentication problems, dispatcher cache issues, and content propagation gaps.

Core Features & Use Cases

  • Systematic diagnostic workflow covering symptoms, agent status, queue review, and log analysis.
  • Guidance for common replication problems (queue blocks, 401 errors, SSL issues, dispatcher cache).
  • Advanced troubleshooting, logging, and preventive measures to reduce future failures.

Quick Start

Run through the diagnostic workflow by verifying symptoms, agent status, replication queues, and connectivity to identify and resolve replication problems.

Frequently Asked Questions about troubleshoot-replication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot AEM replication issues when the queue is blocked?

To troubleshoot AEM replication queue blocks, verify agent status, review replication logs, and check connectivity between author and publish instances to identify and resolve the root cause.

Why does AEM replication fail with a 401 authentication error?

AEM replication 401 errors occur when authentication credentials are invalid or misconfigured, requiring a systematic check of agent configuration and authentication settings across environments to implement a durable fix.

How do I fix AEM dispatcher cache issues after content replication?

Fix AEM dispatcher cache issues by validating replication agent connectivity, reviewing log outputs, and checking dispatcher configuration to ensure content propagation correctly triggers cache invalidation.

What is the best way to diagnose AEM 6.5 LTS content propagation gaps?

The best way to diagnose AEM 6.5 LTS content propagation gaps is applying a systematic workflow covering symptom verification, agent status review, queue analysis, and OS commands to pinpoint failures.

Does this AEM replication troubleshooting workflow apply to both author and publish environments?

Yes, the AEM replication troubleshooting workflow applies across both author and publish environments to resolve blocked queues, connectivity failures, and configuration problems.