#C31 Drupal-CMS 警告の解消

私の環境がMacのローカル環境でDDEVを使い、プレリリースからのアップデートという環境で起きた事例なので、他の方での再現はないかもしれません。また、特殊な対応でDrupalがデフォルトで持つ依存関係を壊してしまう対応を行っていますので、同じ対応を行うと環境によっては修復出来ない可能性がありますので、記事を参考に作業を行なう場合、ご自身で状況を良く把握し調べた上で全て自己責任において行ってください。

automatic_updatesモジュールのインストール時ターミナルに出た警告

[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

管理画面のログに出たpackage_managerの警告

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

以下の警告が管理画面に常時表示されます。
//
利用中の1つ以上のモジュールやテーマの最新版が入手可能です。 サイトを適切に機能させ続けるために、できるだけ早く更新するべきです。このメッセージが管理画面に常時表示されてしまう不具合。コアプログラム、モジュールやテーマが全て最新で更新がなくても表示されてしまいます。
// 

1. automatic_updates モジュールの不具合を修正するため、package_manager と automatic_updates を削除するがautomatic_updatesがdrupal_cms_starterと依存関係で紐づいているので削除出来ず。
2. automatic_updatesを削除するためにdrupal_cms_starterも削除しautomatic_updatesを削除
3. 依存関係 (drupal_cms_starter) に紐付いているテーマ (gin, easy_email_theme, drupal_cms_olivero) やモジュールが同時に削除されます。
4. 管理画面のテーマginも削除してしまったので管理画面もエラーでログイン出来ず。
5. エラー表示されたeasy_breadcrumbが存在しないというエラーを再インストールにて修復
6. テーマやモジュールを削除した影響で core.extension との不整合が発生し、収集がつかなくなる。
7. PHP (PathLocator クラス) の不具合を修正。
8. 必要なテーマ・モジュール (gin, package_manager など) を再インストール。
9. モジュールは再インストールが完了するが、テーマのインストールで不具合が発生
10. 管理画面のエラーを修復するためにGinの修復を行なう
11. Ginのツールバーとの不整合を修復しGinの再インストールを行い管理画面は復旧するがエラーが表示されパッケージマネージャーと残りのテーマのインストールに問題が残る
12. パッケージマネージャーとテーマの再インストール。この時点では依存関係のエラーが残る。
13. YML (services.yml)の不具合を修正
14. composer install で依存関係を修復し、drush updb でデータベースを更新。
15. drush cr でキャッシュをクリアし、最終的にエラーが解消。
16. KeyValueStore\DatabaseStorageに起因するエラーが表示される。DBに古いデータが残っていることに起因しているので削除することで対応。

以上の対応を行い警告メッセージ[ 利用中の1つ以上のモジュールやテーマの最新版が入手可能です。 サイトを適切に機能させ続けるために、できるだけ早く更新するべきです。 ]が常時表示される不具合の修正を行っています。

私の環境で出た固有の問題である可能性と、対応も正しい対応とは言えず参考にはならない記事ですが、私自身の備忘録として記事にしています。もし私の環境で出た固有の問題でなく、他の環境でも再現するDrupalコアやモジュールに起因するバグであった場合は、バグフィックスで対応すると考えられます。警告自体はDrupal-CMSの運用に直接の影響がありませんので、バグフィックスを待つ方が賢明でもありますので記事を見て私と同様の対応をする事はおすすめ出来ません。

今回の記事は、私自身が稚拙な知識で対応を行い、状態を悪化させてしまい、結果的には修復を完了していますが適切なエラー対処とは言い難い対応となっています。本来、別の適切な対処があると考えられますので、もし同様の不具合が出て対応をされる場合専門知識を持つ方に相談する事をおすすめします。

エラーログの警告を解消し、正しく package_manager が動作するように設定を変更します。

エラーログの警告を解消

// エラーログの警告を解消し、正しく package_manager が動作するように設定を変更します。
$ drush config:set package_manager.settings include_unknown_files_in_project_root TRUE -y
$ drush cr

// automatic_updatesのアップデート
$ 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

結果

• composer require drupal/automatic_updates を実行したが、Nothing to install, update or remove と表示されたため、すでにインストール済み。
• composer audit を実行するよう推奨されている（セキュリティ脆弱性の可能性）
• automatic_updates のバージョン ^3.1 が使用されている。

composer auditの実行

//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                                                              |
+-------------------+----------------------------------------------------------------------------------+

結果

composer audit によって、drupal/ai モジュールに 2つのセキュリティ脆弱性（SA-CONTRIB-2025-021 および SA-CONTRIB-2025-022）が検出された。

• 影響を受けるバージョンは 1.0.5 より前のバージョン。
• 問題のモジュール (drupal/ai) は automatic_updates のエラーに直接関係ない可能性が高い が、安全のため修正が必要。

セキュリティ脆弱性の対応

// drupal/ai モジュールを最新バージョンにアップデート
$ composer update drupal/ai --with-dependencies
$ drush cr

drupal/aiモジュールの更新が完了しました。

$ 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.

結果

1. composer remove drupal/automatic_updates を実行したが、依存関係のため削除できなかった。
2. automatic_updates モジュールは、他のモジュールやパッケージに依存されている可能性がある。

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)

結果

1. drupal/drupal_cms_starter 1.0.2 が drupal/automatic_updates (^3.1.7) を必要としている。
2. drupal/project_browser 2.0.0-alpha9 は drupal/automatic_updates のバージョン 3.0 未満と競合している（ただし、現在の automatic_updates は ^3.1 なので問題はなさそう）。

つまり、drupal/drupal_cms_starter が automatic_updates を依存しているため、単純に削除できない状況です。

$ composer remove drupal/drupal_cms_starter drupal/automatic_updates

削除後以下のエラーが出てしまい。管理画面にログイン出来なくなってしまいます。
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).

結果

「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. というエラーメッセージが 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.

結果

[warning] Drush command terminated abnormally. というエラーが発生しているため、drush コマンドが異常終了したことがわかります。

DBアップデートのエラー

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
)

結果

エラーログから Drupal のモジュールとテーマの整合性に問題がある ことが分かります。

主なエラー
    1.    Package Manager のテストモードが有効になっていない
    •    'testing_package_manager' の設定が settings.php で TRUE になっていない。
    2.    一部のモジュールが core.extension に登録されているが、実際には見つからない
    •    login_emailusername
    •    mailsystem
    •    project_browser
    •    redirect
    •    redirect_404
    •    sam
    •    symfony_mailer_lite
    3.    一部のテーマが core.extension に登録されているが、実際には見つからない
    •    gin
    •    easy_email_theme
    •    drupal_cms_olivero

web/sites/default/settings.phpに以下のコードを追加します。

$ settings['testing_package_manager'] = TRUE;

viを使ってsettings.phpを開き上記のコードを入力モード[i]で書き込み、[esc]で入力モードを抜け保存して終了[wq]をします。

不足しているモジュールを再インストール

$ 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.

結果

モジュールのインストールは正常に行われます。

$ 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.

結果

エラーが出てしまいインストールが出来ません。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.

結果

core.extension に登録されているテーマ gin, easy_email_theme, drupal_cms_olivero が実際には見つからない。

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

結果

gin, easy_email_theme, drupal_cms_oliveroがインストールされていません。

$ 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

結果

composer validate の結果、composer.json は有効 だが いくつかの警告があります。ただこの警告は直接のエラーではない ため、現在の gin などのテーマがインストールできない原因とは別の問題です。

$ 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 encountered an unexpected error. Try again later.」 で落ちている。
2. Drupal\package_manager\PathLocator クラスが見つからない というエラーが発生。
3. エラー発生箇所: core/lib/Drupal/Component/DependencyInjection/Container.php の createService() メソッド。

$ 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".

依存関係の修復

  $ 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".

結果

1. Drupal の package_manager に関連するサービスの依存関係が壊れている。
2. LockFileValidator のコンストラクタが KeyValueFactoryInterface を要求しているが、このサービスが見つからない というエラー。
3. keyvalue サービス (keyvalue.database, keyvalue.expirable) には存在するが、適切なエイリアス (alias) がない可能性がある。