Non-production Publisher downtime causes deployment failures in Adobe Experience Manager
This article explains how to troubleshoot deployment failures when a non-production Publisher instance in AEM is unavailable. The issue can affect testing, validation, and deployment activities in UAT or QA environments. To fix this, confirm that the Publisher is unavailable, review the underlying infrastructure and logs, use the approved recovery procedure for the deployment model, and verify that deployments can proceed.
Description description
Environment
- Adobe Experience Manager
- Non-production Publisher environment
- UAT or QA environment
Issue/Symptoms
- The non-production Publisher is unavailable.
- The Publisher URL does not respond or cannot be accessed.
- Deployments targeting the environment fail.
- Testing, validation, and deployment processes in UAT or QA are affected.
Cause
When a non-production publisher instance in AEM becomes unavailable, deployments targeting that environment fails. This issue is typically identified when the publisher URL does not respond or cannot be accessed.
Resolution resolution
Follow these steps to restore the non-production Publisher and verify that deployments can proceed:
- Access the non-production Publisher directly using its URL and confirm that it is unavailable.
- Identify the deployment model and use the approved management interface to verify that the underlying server, virtual machine, or container hosting the Publisher is running and accessible.
- Review the AEM and system logs for errors or warnings that explain why the Publisher is unavailable, including out-of-memory errors, disk-space issues, and service crashes.
- If a recent deployment or configuration change preceded the outage, use the approved rollback procedure to return to a previously working state, or redeploy a known-good snapshot or package.
- After the corrective action, verify that the Publisher is accessible.
- Run or retry the affected deployment and verify that it completes successfully.
- If the Publisher remains unavailable or deployment failures continue, provide the relevant diagnostic information and contact Adobe Support.
Note: The exact infrastructure, log-access, restart, rollback, and snapshot or package procedures depend on the deployment model. Use the approved management process for the applicable Adobe Experience Manager environment.
Related reading
Restart the Publisher instance in Adobe Experience Manager QA environments