Error messages for ECE-Tools
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 Adobe 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
./app/etc/env.php
file/app/etc/env.php
file. Check your filesystem permissions.schema.yaml
file./vendor/magento/ece-tools/config/schema.yaml
file. Check that the config variable name is correct, and that it is defined..magento.env.yaml
file./.magento.env.yaml
file format is invalid. Use a YAML parser to check the syntax and fix any errors..magento.env.yaml
file./.magento.env.yaml
file. Check file permissions..schema.yaml
file./vendor/magento/ece-tools/config/magento.env.yaml
file. Check file permissions and redeploy (magento-cloud environment:redeploy
)../app/etc/config.php
file/app/etc/config.php
file. Check your filesystem permissions.composer.json
file./composer.json
file. Check file permissions.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..magento.env.yaml
contains an option that is not declared in the schema, or an option configured with an invalid value or stage./.magento.env.yaml
file contains invalid configuration. Check the error log for detailed info./bin/magento module:enable --all
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./pub/errors/local.xml
/bin/magento setup:di:compile
cloud.log
for more information. Add VERBOSE_COMMANDS: '-vvv'
into .magento.env.yaml
for more detailed command output.composer dump-autoload
composer dump-autoload
command failed. Check the cloud.log
for more information.Baler
for JavaScript bundling failedSCD_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
./bin/magento setup:static-content:deploy
failedcloud.log
for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv'
option to the .magento.env.yaml
file.cloud.log
for more information.init
directorycloud.log
for more information.init
directory./init
folder. Check your filesystem permissions../init/pub/static/
directory./init/pub/static
folder. Check your filesystem permissions.DEPLOYED_MAGENTO_VERSION_FROM_GIT
environment variable is configured..magento.app.yaml
file. For Braintree payment support, use an official extension from the Commerce Marketplace instead.Deploy stage
server
or port
. Check the cloud.log
for more information../app/etc/env.php
file/app/etc/env.php
file. Check your filesystem permissions.schema.yaml
file./vendor/magento/ece-tools/config/schema.yaml
file. Check that the config variable name is correct, and that it is defined..magento.env.yaml
file./vendor/magento/ece-tools/config/schema.yaml
file. Check that the config variable name is correct, and that it is defined..magento.env.yaml
file./.magento.env.yaml
file. Check file permissions..schema.yaml
file/bin/magento maintenance:enable
failedcloud.log
for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv'
option to the .magento.env.yaml
file.DATABASE_CONFIGURATION
environment variable is configured correctly.SESSION_CONFIGURATION
environment variable is configured correctly. The configuration must contain at least the save
parameter.SEARCH_CONFIGURATION
environment variable is configured correctly. The configuration must contain at least the engine
parameter.RESOURCE_CONFIGURATION
environment variable is configured correctly. The configuration must contain at least connection
parameter.SEARCH_CONFIGURATION
environment variable is configured correctly, and verify that the Elasticsearch service is available.SEARCH_CONFIGURATION
environment variable to enable Elasticsearch, and verify the Elasticsearch service configuration in the services.yaml
file./bin/magento setup:install
failedcloud.log
and install_upgrade.log
for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv'
option to the .magento.env.yaml
file.app:config:import
failedcloud.log
for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv'
option to the .magento.env.yaml
file./bin/magento setup:static-content:deploy
failedcloud.log
for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv'
option to the .magento.env.yaml
file.cloud.log
for more information../pub/static/deployed_version.txt
file. Check your filesystem permissions./bin/magento setup:db-schema:split
failedcloud.log
for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv'
option to the .magento.env.yaml
file.var/view_preprocessed
folder./var/view_preprocessed
folder. Check your filesystem permissions./var/credentials_email.txt
file/var/credentials_email.txt
file. Check your filesystem permissions./bin/magento setup:upgrade
failedcloud.log
and install_upgrade.log
for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv'
option to the .magento.env.yaml
file./bin/magento cache:flush
failedcloud.log
for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv'
option to the .magento.env.yaml
file./bin/magento maintenance:disable
failedcloud.log
for more information. Add VERBOSE_COMMANDS: '-vvv'
into .magento.env.yaml
for more detailed command output.php ./bin/magento cache:enable
php ./bin/magento cache:enable
runs only when Adobe Commerce was installed but ./app/etc/env.php
file was absent or empty at the beginning of the deployment. Check the cloud.log
for more information. Add VERBOSE_COMMANDS: '-vvv'
into .magento.env.yaml
for more detailed command output.crypt/key
key value does not exist in the ./app/etc/env.php
file or the CRYPT_KEY
cloud environment variable./app/etc/env.php
file is not present when Adobe Commerce deployment begins, or if the crypt/key
value is undefined. If you migrated the database from another environment, retrieve the crypt key value from that environment. Then, add the value to the CRYPT_KEY cloud environment variable in your current environment. See Add the Magento encryption key. If you accidentally removed the ./app/etc/env.php
file, use the following command to restore it from the backup files created from a previous deployment: ./vendor/bin/ece-tools backup:restore
CLI command.".magento.app.yaml
file. For Braintree support, use an official Braintree Payments extension from the Commerce Marketplace instead.engine
option. If it is configured, remove the option, or set the value to “elasticsearch”.Post-deploy stage
./app/etc/env.php
file is not writable/app/etc/env.php
file. Check your filesystem permissions.schema.yaml
file./vendor/magento/ece-tools/config/schema.yaml
file. Check that the config variable name is correct, and that it is defined..magento.env.yaml
file./.magento.env.yaml
file format is invalid. Use a YAML parser to check the syntax and fix any errors..magento.env.yaml
file.schema.yaml
file/bin/magento cache:flush
failedcloud.log
for more information. Add VERBOSE_COMMANDS: '-vvv'
into .magento.env.yaml
for more detailed command output.General
schema.yaml
file.magento.env.yaml
file./.magento.env.yaml
file format is invalid. Use a YAML parser to check the syntax and fix any errors..magento.env.yaml
file./.magento.env.yaml
file. Check file permissions..schema.yaml
filecloud.log
for more information.cloud.log
for more information.Warning Errors
Warning errors indicate a problem with the Commerce on cloud infrastructure project configuration such as incorrect, deprecated, unsupported, or missing configuration settings for optional features that can affect site operation. Although a warning does not cause deployment failure, you should review warning messages and update the configuration to resolve them.
Build stage
Deploy stage
bin/magento admin:user:create
command.app/etc/env.php
configuration file was missing or empty.cloud.log
for more information.