The following list includes errors commonly seen during RA environment security updates, with possible solutions.
Drush, All pending updates failed on RA for prod:siteName
settings.php
file
with a correct database include statement. See Configuring your application to use environment databases.sites.php
file. See Using sites.php to specify an alternate settings.php file.Unable to run drush #.#.# pm-updatestatus/pm:security on any
Production multisite for prod:siteName, exiting.
settings.php
file with
a correct database include statement. See Configuring your application to use environment databases.sites.php
file, using sites.php
to specify an alternate settings.php
file.vendor/bin
- Ensure vendor/bin/drush
is committed to a branch and deployed..drushrc
file was detected.
- Remove it from the codebase and add it to your .gitignore
file.Error performing task 16811 : StageDeploy with error message
Staging failed because at least one site failed to stage during the process.
Unable to run drush As this is a Drupal multi-site build, and
you haven't specified a [status] pm-updatestatus/pm:security on any
Production multisite for prod:siteName, exiting.
Unable to run drush [warning] "continue" targeting switch is
equivalent to "break". Did you mean to use "continue"? file.module:898
pm-updatestatus/pm:security on any Production multisite for prod:siteName,
exiting.
View the Composer log file attached to the ticket, search for the first occurrence of Error Output to find details of what caused the automated update process to fail.
Acquia recommends that your development team fixes the root cause of the error and closes the associated ticket. This ensures that the automated process for security updates can attempt to update the website in the next weekly run.
The following table documents the probable root causes for different error messages that you may encounter in the Composer log file, and serves as a starting point for fixing the errors.
Error messages in log file | Probable root cause of the error |
---|---|
|
Composer had issues with the require section versioning. |
|
A dependency pinned to a specific version in the composer.json
file prevented updates from getting completed. |
|
A Composer-dependency conflict prevented updates from getting completed. |
|
The system encountered a PHP error while attempting to perform updates. |
|
The system attempted Composer updates with Composer 1.x, and PHP ran out of memory. |
|
The update process attempted to remove a deprecated package but failed. |
plugin was skipped because it requires a Plugin API version |
Composer updates could not be applied because of a dependency in the site that required Composer 2.x. Other dependencies were only compatible with Composer 1.x. |
|
A private Git repository specified in the composer.json file
prevented Composer updates from getting completed. |
.git directory is missing |
During the Composer update process, the system prompted the user to
reinstall a copy of a dependency due to a missing .git directory.
The automated update process could not respond
|
Cannot apply patch |
Composer attempted to apply patches as specified in the composer.json
file but failed. |