Adobe Commerce deployment troubleshooter
Stuck deployments and failed deployments on Adobe Commerce can be solved using the Deployment troubleshooter tool. Click on each question to reveal the answer in each step of the troubleshooter.
Step 1 - Verify the service is running step-1
Stuck Deployment – Is Adobe Commerce on cloud infrastructure service up? Check Adobe Commerce Cloud.
a. YES – Proceed to Step 2.
b. NO – Maintenance or global outages. Check for estimated duration and updates.
Step 2 - Check deployments in other environments step-2
To get a list of ongoing activities run the following command using magento-cloud CLI (if you have only been added to one cloud project). Note: Check you are on the latest version of magento-cloud CLI. For steps, refer to Update the CLI in the Commerce on Cloud Infrastructure guide.
| code language-bash |
|---|
|
To get a list of ongoing activities run the following command using magento-cloud CLI (if you have been added to multiple projects):
| code language-bash |
|---|
|
To find information about an existing deployment activity (refer to Checking deployment log if Cloud UI has “log snipped” error
for details) you can run this command to obtain a running log of that activity:
| code language-bash |
|---|
|
a. YES – Troubleshoot the other environment blocking deployment in the existing environment. Proceed to Step 3.
b. NO – Troubleshoot the current environment. Proceed to Step 3.
Step 3 - Verify SSH on all nodes step-3
Step 4 - Verify all services running step-4
Step 5 - Verify Bitbucket running step-5
b. NO – Check deployment log errors in the Build and Deploy logs. Proceed to Step 6.
Step 6 - Check error codes step-6
Step 7 - 403 Forbidden error step-7
Step 8 - Verify cron jobs running step-8
ps aufxx |grep cron.php vendor/bin/ece-tools cron:kill and then php vendor/bin/ece-tools cron:unlock. If you were in the process of merging one environment into another, check both environments for running crons.b. NO – Proceed to Step 17.
Step 9 - Application deployable to remote cluster error step-9
Step 10 - Check sufficient storage step-10
Step 11 - Verify disk space step-11
b. NO – Proceed with Step 12.
Step 12 - Environment redeployment failed error step-12
Step 13 - Check for Elasticsearch upgrade fail step-13
b. NO – Proceed to Step 14.
Step 14 - Check space limits step-14
Step 15 - Elasticsearch version error step-15
Step 16 - Verify Composer config step-16
Step 17 - Check for long running processes step-17
a. YES – Identify long running processes and then kill processes:
- Run the following command in the terminal:
ps aufx. - Locate the PID of the long-running process.
- Terminate the process using
kill -9 <PID>.
Monitor deployments for reoccurrence.
b. NO – Proceed to Step 18.
Step 18 - Check for post hook failure step-18
b. NO – Proceed to Step 19.
Step 19 - Check if third-party extensions block deployment step-19
b. NO – Proceed to Step 20.
Step 20 - Check for slow queries step-20
Check slow query log and MySQL show processlist.
a. YES – Kill any long running queries. Review MySQL Kill Syntax.
b. NO – Submit a support ticket.
Step 21 - Downgrade Elasticsearch version step-21
b. NO – Submit a support ticket.