This page provides information about common errors encountered during Remote Administration (RA) environment (glossary term, activate to view definition) security updates, along with possible solutions.
If you encounter an error during the first step of the RA security update process, you must first review the provided error, suggested steps, and documentation for guidance. If solutions are provided, attempt to deploy the suggested fix to your production environment. After deploying the fix, wait for the next automated update attempt to see if the issue has been resolved. Ensuring all documentation steps are carefully followed typically resolves the encountered errors.
If the problem persists, or if the security update is time-sensitive and you lack the necessary developer resources, consider enlisting a partner developer or engaging Acquia Professional Services to effectively address the issue. Timely resolutions are critical for maintaining site security.
Configure the default multisite with a working settings.php file with a correct database include statement. See .
Troubleshooting for failed updates on Composer-based websites
If you encounter an error during the RA automated update process, particularly with security updates for the current Drupal version, you might need to validate that that your site's Composer configuration is correct. For validation, you must ensure that:
A composer.json file with your required modules is in place above the docroot,
A composer.lock file is in place above the docroot,
The /vendor directory is in place above the docroot, and
The docroot/autoload.php file references the location of the vendor directory.
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.
Composer had issues with the require section versioning.
shouldbe
Security update process common errors
This page provides information about common errors encountered during Remote Administration (RA) environment (glossary term, activate to view definition) security updates, along with possible solutions.
If you encounter an error during the first step of the RA security update process, you must first review the provided error, suggested steps, and documentation for guidance. If solutions are provided, attempt to deploy the suggested fix to your production environment. After deploying the fix, wait for the next automated update attempt to see if the issue has been resolved. Ensuring all documentation steps are carefully followed typically resolves the encountered errors.
If the problem persists, or if the security update is time-sensitive and you lack the necessary developer resources, consider enlisting a partner developer or engaging Acquia Professional Services to effectively address the issue. Timely resolutions are critical for maintaining site security.
Configure the default multisite with a working settings.php file with a correct database include statement. See .
Troubleshooting for failed updates on Composer-based websites
If you encounter an error during the RA automated update process, particularly with security updates for the current Drupal version, you might need to validate that that your site's Composer configuration is correct. For validation, you must ensure that:
A composer.json file with your required modules is in place above the docroot,
A composer.lock file is in place above the docroot,
The /vendor directory is in place above the docroot, and
The docroot/autoload.php file references the location of the vendor directory.
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.
Give the RA team (glossary term, activate to view definition) with a list of 5 to 10 domains for websites which should be staged in the RA environments.
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.
Failedtoexecutegitclone
Unabletocheckoutgitbranch
A private Git repository specified in the composer.json file prevented Composer updates from getting completed.
.gitdirectoryismissing
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 yes to the prompt, and exited.
Remove the particular package from the vendor directory as mentioned in the composer_error log file attached with the ticket.
Be careful while removing the package directory as some packages such as simplesamlphp/simplesamlphp may write to the vendor directory, and your changes may be lost. For more information, refer to the package documentation.
Run composer install on root to regenerate this package directory.
Cannotapplypatch
Composer attempted to apply patches as specified in the composer.json file but failed.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Configuring your application to use environment databases
Point requests for default at a working multisite in the sites.php file, using sites.php to specify an alternate settings.php file.
Drush symlink is missing from vendor/bin - Ensure vendor/bin/drush is committed to a branch and deployed.
An alternate .drushrc file was detected. - Remove it from the codebase and add it to your .gitignore file.
Give the RA team (glossary term, activate to view definition) with a list of 5 to 10 domains for websites which should be staged in the RA environments.
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.
Failedtoexecutegitclone
Unabletocheckoutgitbranch
A private Git repository specified in the composer.json file prevented Composer updates from getting completed.
.gitdirectoryismissing
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 yes to the prompt, and exited.
Remove the particular package from the vendor directory as mentioned in the composer_error log file attached with the ticket.
Be careful while removing the package directory as some packages such as simplesamlphp/simplesamlphp may write to the vendor directory, and your changes may be lost. For more information, refer to the package documentation.
Run composer install on root to regenerate this package directory.
Cannotapplypatch
Composer attempted to apply patches as specified in the composer.json file but failed.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Cloud Platform