Deployment troubleshooter – Magento Help Center

Click on each question to reveal the answer details in each step of the troubleshooter.

Step 1

Stuck Deployment – Is Magento Commerce Cloud service up? Check Adobe Magento Magento Commerce Cloud.

a. YES – Proceed to Step 2.
b. NO – Maintenance or global outages. Check for estimated duration and updates.

Step 2

SSH successful to all nodes?

a. YES – Proceed to Step 3.
b. NO – Submit a support ticket.

Step 3

All services running?

a. YES – Proceed to Step 4.
b. NO – Submit a support ticket.

Step 4

Using Bitbucket?

a. YES – Check status.bitbucket.com.
b. NO – Check deployment log errors in Log Locations: Build and Deploy Logs. Proceed to Step 5.

Step 5

Error code reported?

a. YES – Proceed to Step 6.
b. NO – Proceed to Step 7.

Step 6

403 Forbidden?

a. YES – Proceed to Step 15.
b. NO – Proceed to Step 8.

Step 7

Are cron jobs currently running?

a. YES – Login by ssh on integration branch (e.g. master). Kill and unlock cron jobs. This will kill cron jobs and reset the status. Run php vendor/bin/ece-tools cron:kill and then php vendor/bin/ece-tools cron:unlock.
b. NO – Proceed to Step 16.

Step 8

Unable to upload application to the remote cluster error?

a. YES – Proceed to Step 9.
b. NO – Proceed to Step 10.

Step 9

Available storage okay?

a. YES – Proceed with Step 10.
b. NO – Review Manage disk space.

Step 10

<filename> file could not be written Warning?

a. YES – Please increase the disk value in .magento.app.yaml and redeploy. If this does not work, submit a support ticket.
b. NO – Proceed with Step 11.

Step 11

Environment redeployment failed error?

a. YES – Proceed with Step 12.
b. NO – Proceed with Step 7.

Step 12

Elasticsearch being upgraded or deployed?

a. YES – Elasticsearch failed upgrade steps. Refer to Elasticsearch software compatibility. If the Elasticsearch upgrade still doesn't work, submit a support ticket.
b. NO – Proceed to Step 13.

Step 13

File system out of inodes or space?

a. YES – See Manage disk space.
b. NO – Proceed to Step 14.

Step 14

Error about Elasticseach versions?

a. YES – Proceed to Step 15.
b. NO – Proceed to Step 20.

Step 15

Composer config correct?

a. YES – Proceed to Step 9.
b. NO – Review Composer Troubleshooter webpage.

Step 16

Long running processes(es)?

a. YES – Identify long running processes, kill process, and monitor deployments for reoccurrence.
b. NO – Proceed to Step 17.

Step 17

Post hook failure/hang?

a. YES – Database: Free disk space, corruption, incomplete/corrupted tables.
b. NO – Proceed to Step 18.

Step 18

Using third-party extensions?

a. YES – Try Disabling the third-party extensions and running the deployment (to see if they are the cause of the problem), especially if there are extension names in any errors.
b. NO – Proceed to Step 19.

Step 19

Check slow query log and MySQL show processlist. Long running queries?

a. YES – Kill any long running queries. Review MySQL Kill Syntax.
b. NO – Submit a support ticket.

Step 20

Downgrading Elasticsearch versions?

a. YES – Can't be done through configuration. Submit a support ticket.
b. NO – Submit a support ticket.

Back to Step 1

Articles in this section