#C31 Drupal-CMS Warning Resolved

This is a case that occurred in my environment, where I was using DDEV on a local Mac environment and updating from a pre-release version, so it may not be reproducible in other people's environments. Also, because I am taking a special approach that breaks the dependencies that Drupal has by default, there is a possibility that the environment may not be able to be repaired if the same approach is taken, so if you are going to perform the work using the article as a reference, please make sure you fully understand the situation and investigate it yourself before doing so at your own risk.

Warning message displayed in the terminal when installing the automatic_updates module

[warning] foreach() argument must be of type array|object, null given Mapping.php:31
[warning] foreach() argument must be of type array|object, null given Mapping.php:230

Warning from package_manager in the admin screen log

The following paths in /var/www/html aren't recognized as part of your Drupal site, so to be safe, Package Manager is excluding them from all stage operations. If these files are not needed for Composer to work properly in your site, no action is needed. Otherwise, you can disable this behavior by setting the package_manager.settings:include_unknown_files_in_project_root config setting to TRUE. .ddev README.md launch-drupal-cms.sh recipes

The following warning will always be displayed in the admin screen.
//
The latest version of one or more of the modules or themes you are using is available. You should update it as soon as possible to keep your site functioning properly. This message is displayed in the admin area all the time. It is displayed even if the core program, modules and themes are all up to date and there is no need to update them.
// 

1. In order to fix a bug in the automatic_updates module, I deleted the package_manager and automatic_updates, but I couldn't delete automatic_updates because it was linked to drupal_cms_starter as a dependency.
2. To delete automatic_updates, also delete drupal_cms_starter and delete automatic_updates
3. The themes (gin, easy_email_theme, drupal_cms_olivero) and modules that are linked to the dependency (drupal_cms_starter) will be deleted at the same time.
4. I also deleted the theme gin from the admin screen, so I couldn't log in due to an error.
5. The error displayed was that the easy_breadcrumb did not exist. This was fixed by reinstalling.
6. The deletion of themes and modules causes a conflict with core.extension, and it becomes impossible to recover.
7. Fixed a bug in PHP (PathLocator class).
8. Reinstall the required themes and modules (gin, package_manager, etc.).
9. The module is reinstalled successfully, but there is a problem with the theme installation
10. Repairing Gin to fix errors in the admin screen
11. The management screen is restored by repairing the incompatibility with Gin's toolbar and reinstalling Gin, but an error is displayed and there are still problems with the package manager and the installation of the remaining themes.
12. Reinstall the package manager and theme. At this point, dependency errors will still remain.
13. Fixed a bug in YML (services.yml)
14. Repair dependencies with composer install, and update the database with drush updb.
15. The cache was cleared using drush cr, and the error was finally resolved.
16. An error caused by KeyValueStore/DatabaseStorage is displayed. This is caused by old data remaining in the DB, so it can be dealt with by deleting it.

We are working on a fix for the problem where the warning message [ An updated version of one or more of the modules or themes you are using is available. You should update it as soon as possible to keep your site functioning properly. ] is displayed at all times.

This is an article that I have written as a reminder for myself, as it is a unique problem that occurred in my environment and the response is not a correct response and cannot be used as a reference. If it is not a unique problem that occurred in my environment, but a bug that occurs in Drupal core or modules that can be reproduced in other environments, it is thought that it will be handled with a bug fix. As the warning itself does not have a direct impact on the operation of Drupal-CMS, it is also wise to wait for a bug fix, so I cannot recommend that you take the same action as me after reading the article.

In this article, I dealt with the problem using my own poor knowledge, which made the situation worse, and although I was eventually able to fix it, it was hardly an appropriate way to deal with the error. There are probably other, more appropriate ways to deal with the problem, so if you encounter a similar problem, I recommend that you consult someone with specialist knowledge.

We will change the settings so that the error log warnings are resolved and the package_manager works correctly.

Resolve the error log warning

// We will change the settings so that the error log warnings are resolved and the package_manager works correctly.
$ drush config:set package_manager.settings include_unknown_files_in_project_root TRUE -y
$ drush cr

// automatic_updates update
$ composer require drupal/automatic_updates

./composer.json has been updated
Running composer update drupal/automatic_updates
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Writing lock file
Installing dependencies from lock file (including require-dev)
Nothing to install, update or remove
Generating optimized autoload files
59 packages you are using are looking for funding.
Use the composer fund command to find out more!
Found 2 security vulnerability advisories affecting 1 package.
Run "composer audit" for a full list of advisories.
Using version ^3.1 for drupal/automatic_updates

Result

• I ran composer require drupal/automatic_updates, but it displayed ‘Nothing to install, update or remove’, so it's already installed.
• It is recommended that you run composer audit (possible security vulnerability)
• The version ^3.1 of automatic_updates is used.

Running composer audit

//Running composer audit
$ composer audit

Found 2 security vulnerability advisories affecting 1 package:
+-------------------+----------------------------------------------------------------------------------+
| Package           | drupal/ai                                                                        |
| Severity          |                                                                                  |
| CVE               | NO CVE                                                                           |
| Title             | AI (Artificial Intelligence) - Critical - Remote Code Execution -                |
|                   | SA-CONTRIB-2025-021                                                              |
| URL               | https://www.drupal.org/sa-contrib-2025-021                                       |
| Affected versions | <1.0.5                                                                           |
| Reported at       | 2025-03-05T17:18:25+00:00                                                        |
| Advisory ID       | SA-CONTRIB-2025-021                                                              |
+-------------------+----------------------------------------------------------------------------------+
+-------------------+----------------------------------------------------------------------------------+
| Package           | drupal/ai                                                                        |
| Severity          |                                                                                  |
| CVE               | NO CVE                                                                           |
| Title             | AI (Artificial Intelligence) - Moderately critical - Gadget Chain -              |
|                   | SA-CONTRIB-2025-022                                                              |
| URL               | https://www.drupal.org/sa-contrib-2025-022                                       |
| Affected versions | <1.0.5                                                                           |
| Reported at       | 2025-03-05T17:27:19+00:00                                                        |
| Advisory ID       | SA-CONTRIB-2025-022                                                              |
+-------------------+----------------------------------------------------------------------------------+

Result

The composer audit detected two security vulnerabilities (SA-CONTRIB-2025-021 and SA-CONTRIB-2025-022) in the drupal/ai module.

• The affected versions are those prior to 1.0.5.
• The module in question (drupal/ai) is highly unlikely to be directly related to the automatic_updates error, but it needs to be fixed for safety's sake.

Handling security vulnerabilities

// Update the drupal/ai module to the latest version.
$ composer update drupal/ai --with-dependencies
$ drush cr

The update of the drupal/ai module has been completed.

$ drush pmu automatic_updates -y
$ composer remove drupal/automatic_updates
Removal failed, drupal/automatic_updates is still present, it may be required by another package. See composer why drupal/automatic_updates.

Result

1. I ran composer remove drupal/automatic_updates, but it couldn't be deleted due to dependencies.
2. The automatic_updates module may be dependent on other modules or packages.

Check the effect of the dependency using composer why.

$ composer why drupal/automatic_updates
drupal/drupal_cms_starter 1.0.2        requires  drupal/automatic_updates (^3.1.7)
drupal/project_browser    2.0.0-alpha9 conflicts drupal/automatic_updates (<3.0)

Result

1. drupal/drupal_cms_starter 1.0.2 requires drupal/automatic_updates (^3.1.7).
2. drupal/project_browser 2.0.0-alpha9 conflicts with versions of drupal/automatic_updates less than 3.0 (however, the current automatic_updates is ^3.1, so it seems to be fine).

In other words, drupal/drupal_cms_starter depends on automatic_updates, so it cannot be simply deleted.

$ composer remove drupal/drupal_cms_starter drupal/automatic_updates
// After deleting, the following error appears and you can no longer log in to the admin screen.

The website encountered an unexpected error. Try again later.
AssertionError: The file specified by the given app root, relative path and file name (/var/www/html/web/modules/contrib/easy_breadcrumb/easy_breadcrumb.info.yml) do not exist. in assert() (line 73 of core/lib/Drupal/Core/Extension/Extension.php).

Result

1. 「The website encountered an unexpected error. Try again later.」
2. AssertionError: The file specified by the given app root, relative path and file name (/var/www/html/web/modules/contrib/easy_breadcrumb/easy_breadcrumb.info.yml) do not exist. core/lib/Drupal/Core/Extension/Extension.php:73

$ composer require drupal/easy_breadcrumb
$ drush en easy_breadcrumb -y
$ drush updb -y
$ drush cr
[warning] Drush command terminated abnormally.

Result

The error [warning] Drush command terminated abnormally. indicates that the drush command terminated abnormally.

DB update error

$ drush updb -y

[error]  Package Manager is available for early testing. To install the module set the
value of 'testing_package_manager' to TRUE in your settings.php file.
[error]   (Currently using Missing or invalid modules The following modules are marked as installed in the core.extension
configuration, but they are missing:
* login_emailusername
* mailsystem
* project_browser
* redirect
* redirect_404
* sam
* symfony_mailer_lite
Review the  suggestions for resolving this incompatibility [1] to repair your
installation, and then re-run update.php.
[1] https://www.drupal.org/docs/updating-drupal/troubleshooting-database-updates
)
[error]   (Currently using Missing or invalid themes The following themes are marked as installed in the core.extension
configuration, but they are missing:
* gin
* easy_email_theme
* drupal_cms_olivero
Review the  suggestions for resolving this incompatibility [1] to repair your
installation, and then re-run update.php.
[1] https://www.drupal.org/docs/updating-drupal/troubleshooting-database-updates
)

Result

The error log shows that there is a problem with the consistency of Drupal modules and themes.

Main errors
    1.    Package Manager's test mode is not enabled.
    •     The ‘testing_package_manager’ setting is not set to TRUE in settings.php.
    2.    Some modules are registered in core.extension, but they are not actually found.
    •    login_emailusername
    •    mailsystem
    •    project_browser
    •    redirect
    •    redirect_404
    •    sam
    •    symfony_mailer_lite
    3.    Some themes are registered in core.extension, but they cannot actually be found.
    •    gin
    •    easy_email_theme
    •    drupal_cms_olivero

Add the following code to web/sites/default/settings.php.

$ settings['testing_package_manager'] = TRUE;

Open settings.php using vi, enter the above code in input mode [i], exit input mode with [esc], save and exit with [wq].

Reinstall the missing module

$ composer require drupal/login_emailusername drupal/mailsystem drupal/project_browser drupal/redirect drupal/redirect_404 drupal/sam drupal/symfony_mailer_lite

./composer.json has been updated
Running composer update drupal/login_emailusername drupal/mailsystem drupal/project_browser drupal/redirect drupal/redirect_404 drupal/sam drupal/symfony_mailer_lite
Loading composer repositories with package information
Updating dependencies
Lock file operations: 10 installs, 0 updates, 0 removals
- Locking drupal/login_emailusername (3.0.1)
- Locking drupal/mailsystem (4.5.0)
- Locking drupal/project_browser (2.0.0-alpha10)
- Locking drupal/redirect (1.11.0)
- Locking drupal/redirect_404 (1.11.0)
- Locking drupal/sam (1.3.2)
- Locking drupal/symfony_mailer_lite (2.0.2)
- Locking html2text/html2text (4.3.2)
- Locking symfony/css-selector (v7.2.0)
- Locking tijsverkoyen/css-to-inline-styles (v2.3.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 10 installs, 0 updates, 0 removals
- Downloading drupal/project_browser (2.0.0-alpha10)
- Installing drupal/login_emailusername (3.0.1): Extracting archive
- Installing drupal/project_browser (2.0.0-alpha10): Extracting archive
- Installing drupal/redirect (1.11.0): Extracting archive
- Installing drupal/redirect_404 (1.11.0)
- Installing drupal/sam (1.3.2): Extracting archive
- Installing symfony/css-selector (v7.2.0): Extracting archive
- Installing tijsverkoyen/css-to-inline-styles (v2.3.0): Extracting archive
- Installing html2text/html2text (4.3.2): Extracting archive
- Installing drupal/mailsystem (4.5.0): Extracting archive
- Installing drupal/symfony_mailer_lite (2.0.2): Extracting archive
Generating optimized autoload files
58 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
Using version ^3.0 for drupal/login_emailusername
Using version ^4.5 for drupal/mailsystem
Using version ^2.0@alpha for drupal/project_browser
Using version ^1.11 for drupal/redirect
Using version ^1.11 for drupal/redirect_404
Using version ^1.3 for drupal/sam
Using version ^2.0 for drupal/symfony_mailer_lite

$ drush cr
[success] Cache rebuild complete.

Result

The module is installed successfully.

$ composer require drupal/gin drupal/easy_email_theme drupal/drupal_cms_olivero

./composer.json has been updated
Running composer update drupal/gin drupal/easy_email_theme drupal/drupal_cms_olivero
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
 Problem 1
   - Root composer.json requires drupal/gin * -> satisfiable by drupal/gin[1.0.0-alpha1, ..., 1.0.0-alpha14, 2.0.0-alpha1, ..., 2.0.0-alpha13, 3.0.0-alpha1, ..., 3.0.0, 4.0.0, ..., 4.0.6].
   - drupal/project_browser is locked to version 2.0.0-alpha10 and an update of this package was not requested.
   - drupal/gin[1.0.0-alpha4, ..., 1.0.0-alpha14] require drupal/core <8.8 -> found drupal/core[8.0.0-beta6, ..., 8.7.14] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
   - drupal/gin[1.0.0-alpha1, ..., 1.0.0-alpha2] require drupal/core ~8.0 -> found drupal/core[8.0.0-beta6, ..., 8.9.20] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
   - drupal/gin 1.0.0-alpha3 requires drupal/core ^8 || ^9 -> found drupal/core[8.0.0-beta6, ..., 8.9.20, 9.0.0-alpha1, ..., 9.5.11] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
   - drupal/gin[2.0.0-alpha1, ..., 2.0.0-alpha3] require drupal/core ^8.8 -> found drupal/core[8.8.0-alpha1, ..., 8.9.20] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
   - drupal/gin[2.0.0-alpha4, ..., 2.0.0-alpha13, 3.0.0-alpha1, ..., 3.0.0-alpha36] require drupal/core ^8.8 || ^9 -> found drupal/core[8.8.0-alpha1, ..., 8.9.20, 9.0.0-alpha1, ..., 9.5.11] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
   - drupal/gin[3.0.0-beta1, ..., 3.0.0-rc1] require drupal/core ^8.9 || ^9 || ^10 -> found drupal/core[8.9.0-beta1, ..., 8.9.20, 9.0.0-alpha1, ..., 9.5.11, 10.0.0-alpha1, ..., 10.4.4] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
   - drupal/gin[3.0.0-rc2, ..., 3.0.0-rc10] require drupal/core ^9 || ^10 -> found drupal/core[9.0.0-alpha1, ..., 9.5.11, 10.0.0-alpha1, ..., 10.4.4] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
   - drupal/gin 3.0.0-alpha37 requires drupal/core ^8.8 || ^9 || ^10 -> found drupal/core[8.8.0-alpha1, ..., 8.9.20, 9.0.0-alpha1, ..., 9.5.11, 10.0.0-alpha1, ..., 10.4.4] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
   - drupal/gin[4.0.1, ..., 4.0.6] require drupal/gin_toolbar ^2.0 -> found drupal/gin_toolbar[2.0.0] but it conflicts with your root composer.json require (1.0.0).
   - drupal/project_browser 2.0.0-alpha10 conflicts with drupal/gin 4.0.0.
   - drupal/project_browser 2.0.0-alpha10 conflicts with drupal/gin 3.0.0.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require drupal/gin:*" to figure out if any version is installable, or "composer require drupal/gin:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.

$ drush cr
[success] Cache rebuild complete.

Result

I'm getting an error and can't install it. I'll try updating the DB.

$ drush updb -y

[error]   (Currently using Missing or invalid themes The following themes are marked as installed in the core.extension
configuration, but they are missing:
* gin
* easy_email_theme
* drupal_cms_olivero
Review the  suggestions for resolving this incompatibility [1] to repair your
installation, and then re-run update.php.
[1] https://www.drupal.org/docs/updating-drupal/troubleshooting-database-updates
)
// Requirements check reports errors. Do you wish to continue?: yes.
[success] No pending updates.

Result

The themes gin, easy_email_theme and drupal_cms_olivero registered in core.extension are not actually found.

$ ls -l /var/www/html/web/themes/contrib/
total 0
drwxr-xr-x 1 shinichirotakeda dialout 698 Aug  8  2024 bootstrap5

Result

gin, easy_email_theme and drupal_cms_olivero are not installed.

$ composer validate

./composer.json is valid, but with a few warnings
See https://getcomposer.org/doc/04-schema.md for details on the schema
# General warnings
- require.drupal/autosave_form : exact version constraints (1.10.0) should be avoided if the package follows semantic versioning
- require.drupal/better_exposed_filters : exact version constraints (7.0.5) should be avoided if the package follows semantic versioning
- require.drupal/bpmn_io : exact version constraints (2.0.7) should be avoided if the package follows semantic versioning
- require.drupal/coffee : exact version constraints (2.0.1) should be avoided if the package follows semantic versioning
- require.drupal/core-composer-scaffold : exact version constraints (11.1.4) should be avoided if the package follows semantic versioning
- require.drupal/core-project-message : exact version constraints (11.1.4) should be avoided if the package follows semantic versioning
- require.drupal/core-recommended : exact version constraints (11.1.4) should be avoided if the package follows semantic versioning
- require.drupal/dashboard : exact version constraints (2.0.0) should be avoided if the package follows semantic versioning
- require.drupal/easy_email : exact version constraints (3.0.4) should be avoided if the package follows semantic versioning
- require.drupal/gin_toolbar : exact version constraints (1.0.0) should be avoided if the package follows semantic versioning
- require.drupal/honeypot : exact version constraints (2.2.2) should be avoided if the package follows semantic versioning
- require.drupal/klaro : exact version constraints (3.0.0) should be avoided if the package follows semantic versioning

Result

As a result of composer validate, composer.json is valid, but there are some warnings. However, these warnings are not direct errors, so they are a separate issue from the reason why themes such as gin cannot be installed at present.

$ composer show drupal/gin --all | grep versions

versions : 4.0.x-dev, 4.0.6, 4.0.5, 4.0.4, 4.0.3, 4.0.2, 4.0.1, 4.0.0, 3.x-dev, 3.0.0, 3.0.0-rc16, 3.0.0-rc15, 3.0.0-rc14, 3.0.0-rc13, 3.0.0-rc12, 3.0.0-rc11, 3.0.0-rc10, 3.0.0-rc9, 3.0.0-rc8, 3.0.0-rc7, 3.0.0-rc6, 3.0.0-rc5, 3.0.0-rc4, 3.0.0-rc3, 3.0.0-rc2, 3.0.0-rc1, 3.0.0-beta5, 3.0.0-beta4, 3.0.0-beta3, 3.0.0-beta2, 3.0.0-beta1, 3.0.0-alpha37, 3.0.0-alpha36, 3.0.0-alpha35, 3.0.0-alpha34, 3.0.0-alpha33, 3.0.0-alpha32, 3.0.0-alpha31, 3.0.0-alpha30, 3.0.0-alpha29, 3.0.0-alpha28, 3.0.0-alpha27, 3.0.0-alpha26, 3.0.0-alpha25, 3.0.0-alpha24, 3.0.0-alpha23, 3.0.0-alpha22, 3.0.0-alpha21, 3.0.0-alpha20, 3.0.0-alpha19, 3.0.0-alpha18, 3.0.0-alpha17, 3.0.0-alpha16, 3.0.0-alpha15, 3.0.0-alpha14, 3.0.0-alpha13, 3.0.0-alpha12, 3.0.0-alpha11, 3.0.0-alpha10, 3.0.0-alpha9, 3.0.0-alpha8, 3.0.0-alpha7, 3.0.0-alpha6, 3.0.0-alpha5, 3.0.0-alpha4, 3.0.0-alpha3, 3.0.0-alpha2, 3.0.0-alpha1, 2.x-dev, 2.0.0-alpha13, 2.0.0-alpha12, 2.0.0-alpha11, 2.0.0-alpha10, 2.0.0-alpha9, 2.0.0-alpha8, 2.0.0-alpha7, 2.0.0-alpha6, 2.0.0-alpha5, 2.0.0-alpha4, 2.0.0-alpha3, 2.0.0-alpha2, 2.0.0-alpha1, 1.x-dev, 1.0.0-alpha14, 1.0.0-alpha13, 1.0.0-alpha12, 1.0.0-alpha11, 1.0.0-alpha10, 1.0.0-alpha9, 1.0.0-alpha8, 1.0.0-alpha7, 1.0.0-alpha6, 1.0.0-alpha5, 1.0.0-alpha4, 1.0.0-alpha3, 1.0.0-alpha2, 1.0.0-alpha1, dev-3.x, dev-4.0.x, dev-2.x, dev-1.x

$ composer require drupal/gin_toolbar:^2.0 --with-dependencies

./composer.json has been updated
Running composer update drupal/gin_toolbar --with-dependencies
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 1 update, 0 removals
- Upgrading drupal/gin_toolbar (1.0.0 => 2.0.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 1 update, 0 removals
- Downloading drupal/gin_toolbar (2.0.0)
- Upgrading drupal/gin_toolbar (1.0.0 => 2.0.0): Extracting archive
Generating optimized autoload files
58 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.

$ drush cr
[success] Cache rebuild complete.

$ composer require drupal/gin

./composer.json has been updated
Running composer update drupal/gin
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 0 updates, 0 removals
- Locking drupal/gin (4.0.6)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 0 updates, 0 removals
- Downloading drupal/gin (4.0.6)
- Installing drupal/gin (4.0.6): Extracting archive
Generating optimized autoload files
59 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
Using version ^4.0 for drupal/gin

$ drush cr
[success] Cache rebuild complete.

The website encountered an unexpected error. Try again later.
Error: Class "Drupal\package_manager\PathLocator" not found in Drupal\Component\DependencyInjection\Container->createService() (line 259 of core/lib/Drupal/Component/DependencyInjection/Container.php).
Drupal\Component\DependencyInjection\Container->get() (Line: 430)
Drupal\Component\DependencyInjection\Container->resolveServicesAndParameters() (Line: 237)
Drupal\Component\DependencyInjection\Container->createService() (Line: 177)
Drupal\Component\DependencyInjection\Container->get() (Line: 197)
Drupal::service() (Line: 38)
package_manager_requirements()
call_user_func_array() (Line: 355)
Drupal\Core\Extension\ModuleHandler->Drupal\Core\Extension\{closure}() (Line: 307)
Drupal\Core\Extension\ModuleHandler->invokeAllWith() (Line: 354)
Drupal\Core\Extension\ModuleHandler->invokeAll() (Line: 109)
Drupal\system\SystemManager->listRequirements() (Line: 53)
Drupal\system\Controller\SystemInfoController->status()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 593)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 183)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle() (Line: 116)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 90)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 709)
Drupal\Core\DrupalKernel->handle() (Line: 19)

1. The website is down with the message ‘The website encountered an unexpected error. Try again later.’.
2. An error occurred: The Drupal\package_manager\PathLocator class was not found.
3. Error location: createService() method in core/lib/Drupal/Component/DependencyInjection/Container.php.

$ composer require drupal/package_manager --with-all-dependencies

./composer.json has been updated
Running composer update drupal/package_manager --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Lock file operations: 2 installs, 0 updates, 0 removals
- Locking drupal/automatic_updates (3.1.7)
- Locking drupal/package_manager (3.1.7)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 2 installs, 0 updates, 0 removals
- Downloading drupal/automatic_updates (3.1.7)
- Installing drupal/automatic_updates (3.1.7): Extracting archive
- Installing drupal/package_manager (3.1.7)
Generating optimized autoload files
59 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
Using version ^3.1 for drupal/package_manager
However, you may be able to use a command like:

$ drush cr
In DefinitionErrorExceptionPass.php line 48:
 Cannot autowire service "Drupal\package_manager\Validator\LockFileValidator
 ": argument "$keyValueFactory" of method "__construct()" references interfa
 ce "Drupal\Core\KeyValueStore\KeyValueFactoryInterface" but no such service
  exists. You should maybe alias this interface to one of these existing ser
 vices: "keyvalue", "keyvalue.database", "keyvalue.expirable".

Repairing the dependency relationship

  $ composer install
  
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Nothing to install, update or remove
Generating optimized autoload files
59 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
* Homepage: https://www.drupal.org/project/drupal
* Support:
 * docs: https://drupal.org/docs/user_guide/en/index.html
 * chat: https://drupal.org/node/314178
 
$ composer update --lock
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Writing lock file
Installing dependencies from lock file (including require-dev)
Nothing to install, update or remove
Generating optimized autoload files
59 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
 $ drush cr
 
In DefinitionErrorExceptionPass.php line 48:
 Cannot autowire service "Drupal\package_manager\Validator\LockFileValidator
 ": argument "$keyValueFactory" of method "__construct()" references interfa
 ce "Drupal\Core\KeyValueStore\KeyValueFactoryInterface" but no such service
  exists. You should maybe alias this interface to one of these existing ser
 vices: "keyvalue", "keyvalue.database", "keyvalue.expirable".

Result

1. The dependency of the service related to Drupal's package_manager is broken.
2. An error that the LockFileValidator constructor requires KeyValueFactoryInterface, but this service cannot be found.
3. The keyvalue service (keyvalue.database, keyvalue.expirable) exists, but there may not be an appropriate alias (alias).