۶Ƶ

Documentation

Deployment failed on cache flush: “There are no commands defined in the ‘cache’ namespace” error

Last update: Mon Feb 24 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

When deployment fails in ۶Ƶ Commerce on cloud infrastructure with a There are no commands defined in the ‘cache’ namespace error, identify the invalid rows left from those configurations. If you have only have one website, then the second test for the websites doesn’t apply, and you only need to test for stores.

Description description

Environment

۶Ƶ Commerce on cloud infrastructure 2.4.x

Issue

Warning: Backup the database first, if you’re doing this in a live Production site, before performing these steps.

This article provides a solution for the issue when your deployment fails and one of the errors in the log looks like this:

[ YEAR-DAYTIME]  ERROR: [ 127]  The command "php ./bin/magento cache:flush --ansi --no-interaction" failed.
        There are no commands defined in the "cache" namespace.
...
      W:     There are no commands defined in the "cache" namespace.

Steps to reproduce:

Attempt to deploy.

Expected results:

You deploy successfully.

Actual results:

You don’t deploy successfully. In the logs you see a deployment error with a message similar to:  There are no commands in the cache namespace.

Cause

The core_config_data table contains configurations for a store ID or website ID that no longer exists in the database. This occurs when you’ve imported a database backup from another instance/environment, and the configurations for those scopes remain in the database, even though the associated store(s)/website(s) have been deleted.

Resolution resolution

If you have only have one website, then the second test for the websites doesn’t apply, and you only need to test for stores.

To solve this issue, identify the invalid rows left from those configurations.

  1. SSH to the server and run this command:

    code language-none 
    bin/magento

  2. The error message may indicate what rows and tables remain in the database from deleted sites. For example, the following is an error indicating that the requested store wasn’t found:

    code language-none 
    ...
    In StoreRepository.php line 112:

    The store that was requested wasn't found. Verify the store and try again.

  3. Run this MySQL query to verify that the store cannot be found, which is indicated by the error message in step 2.

    code language-none 
    select distinct scope_id from core_config_data where scope='stores' and scope_id not in (select store_id from store);

  4. Run the following MySQL statement to delete the invalid rows:

    code language-none 
    delete from core_config_data where scope='stores' and scope_id not in (select store_id from store);

  5. Run this command again:

    code language-none 
    bin/magento

    If you get an error like the one below which indicates that the website with id X that was requested wasn’t found, you have configurations remaining in the database from website(s), as well as store(s), that have been deleted.

    code language-none 
    In WebsiteRepository.php line 110:

    The website with id X that was requested wasn't found. Verify the website and try again.

    Run this MySQL query and verify that the website can’t be found:

    code language-none 
    select distinct scope_id from core_config_data where scope='websites' and scope_id not in (select website_id from store_website);

  6. Run this MySQL statement to delete the invalid rows from the website configuration:

    code language-none 
    delete from core_config_data where scope='websites' and scope_id not in (select website_id from store_website);
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f