Error messages for ECE-Tools

Last update: February 3, 2025

CREATED FOR:

  • Developer

This error message reference provides information to troubleshoot errors that can occur during the Adobe Commerce on cloud infrastructure build, deploy, and post-deploy processes.

All critical and warning error messages that occur during deployment are written to both the var/log/cloud.log and /var/log/cloud.error.log files. The cloud error log file contains only errors from the latest deployment. An empty file indicates a successful deployment with no errors.

In the cloud.error.log file, each entry is formatted as a JSON string for easier parsing:

{"errorCode":1006,"stage":"build","step":"validate-config","suggestion":"No stores/website/locales found in config.php\n  To speed up the deploy process do the following:\n  1. Using SSH, log in to your Magento Cloud account\n  2. Run \"php ./vendor/bin/ece-tools config:dump\"\n  3. Using SCP, copy the app/etc/config.php file to your local repository\n  4. Add, commit, and push your changes to the app/etc/config.php file","title":"The configured state is not ideal","type":"warning"}

Error messages are categorized by one of the deployment stages: build, deploy, and post-deploy. Each section provides a list of associated errors with the following information for each error:

  • Error code: The Adobe Commerce-assigned identifier for the error message
  • Stage: Indicates whether the error occurred during the build, deploy, or post-deploy stage
  • Step: Indicates the step in the deployment scenario that can return the error. If the Step column is blank, the error is a general error that can be returned by multiple steps, or during pre-processing operations. See Scenario-based deployment for more information about the build, deploy, and post-deploy steps.
  • Suggestion: Provides guidance to troubleshoot and resolve the error
  • Title (Error description): A description that summarizes the cause of the error
  • Type: Indicates whether the error is a critical error or a warning

Critical Errors

Critical errors indicate a problem with the Commerce on cloud infrastructure project configuration that causes deployment failure, for example incorrect, unsupported, or missing configuration for required settings. Before you can deploy, you must update the configuration to resolve these errors.

Build stage

Error code
Build step
Error description (Title)
Suggested action
2
Can not write to the ./app/etc/env.php file
Deployment script can not make required changes to the /app/etc/env.php file. Check your filesystem permissions.
3
Configuration is not defined in the schema.yaml file
Configuration is not defined in the ./vendor/magento/ece-tools/config/schema.yaml file. Check that the config variable name is correct and defined.
4
Failed to parse the .magento.env.yaml file
The ./.magento.env.yaml file format is invalid. Use a YAML parser to check the syntax and fix any errors.
5
Unable to read the .magento.env.yaml file
Unable to read the ./.magento.env.yaml file. Check file permissions.
6
Unable to read the .schema.yaml file
Unable to read the ./vendor/magento/ece-tools/config/magento.env.yaml file. Check file permissions and redeploy (magento-cloud environment:redeploy).
7
refresh-modules
Can not write to the ./app/etc/config.php file
The deployment script can not make required changes to the /app/etc/config.php file. Check your filesystem permissions.
8
validate-config
Can not read the composer.json file
Unable to read the ./composer.json file. Check file permissions.
9
validate-config
The composer.json file is missing required autoload section
Required autoload section is missing from the composer.json file. Compare the autoload section to the composer.json file in the Cloud template, and add the missing configuration.
10
validate-config
The .magento.env.yaml file contains an option that is not declared in the schema, or an option configured with an invalid value or stage
The ./.magento.env.yaml file contains invalid configuration. Check the error log for detailed info.
11
refresh-modules
Command failed: /bin/magento module:enable --all
Try to run composer update locally. Then, commit and push the updated composer.lock file. Also, check the cloud.log for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv' option to the .magento.env.yaml file.
12
apply-patches
Failed to apply patch
13
set-report-dir-nesting-level
Can not write to the file /pub/errors/local.xml
14
copy-sample-data
Failed to copy sample data files
15
compile-di
Command failed: /bin/magento setup:di:compile
Check the cloud.log for more information. Add VERBOSE_COMMANDS: '-vvv' into .magento.env.yaml for more detailed command output.
16
dump-autoload
Command failed: composer dump-autoload
The composer dump-autoload command failed. Check the cloud.log for more information.
17
run-baler
The command to run Baler for Javascript bundling failed
Check the SCD_USE_BALER environment variable to verify that the Baler module is configured and enabled for JS bundling. If you do not need the Baler module, set SCD_USE_BALER: false.
18
compress-static-content
Required utility was not found (timeout, bash)
19
deploy-static-content
Command /bin/magento setup:static-content:deploy failed
Check the cloud.log for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv' option to the .magento.env.yaml file.
20
compress-static-content
Static content compression failed
Check the cloud.log for more information.
21
backup-data: static-content
Failed to copy static content into the init directory
Check the cloud.log for more information.
22
backup-data: writable-dirs
Failed to copy some writable directories into the init directory
Failed to copy writable directories into the ./init folder. Check your filesystem permissions.
23
Unable to create a logger object
24
backup-data: static-content
Failed to clean the ./init/pub/static/ directory
Failed to clean ./init/pub/static folder. Check your filesystem permissions.
25
Can not find the Composer package
If you installed the Adobe Commerce application version directly from the GitHub repository, verify that the DEPLOYED_MAGENTO_VERSION_FROM_GIT environment variable is configured.
26
validate-config
Remove Magento Braintree module configuration which is no longer supported in Adobe Commerce and Magento Open Source 2.4 and later versions.
Support for the Braintree module is no longer included with Magento 2.4.0 and later. Remove the CONFIG__STORES__DEFAULT__PAYMENT__BRAINTREE__CHANNEL variable from the variables section of the .magento.app.yaml file. For Braintree payment support, use an official extension from the Commerce Marketplace instead.