Cause

The issue is caused by parallel interfering processes on the Redis connection.

Here, a process in App/Config/Type/System.php was expecting a response for system_defaultweb, but received a response for system_cache_exists that was made by a different process. See the detailed explanation in Jason Woods’ post.

Solution

Disable parallelism and run setup:static-content:deploy in a single-thread mode by setting the following environment variable:

STATIC_CONTENT_THREADS =1

Also you may run the setup:static-content:deploy command followed by the -j 1 (or --jobs=1) argument.

NOTE
In the single-thread mode, the static content deployment process may take four times longer.

More information

In our developer documentation:

Previous pageRedirect back to the Commerce Admin login form with "Your current session has been expired" error
Next pageSite in maintenance mode but available to customers

Commerce


Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more