I have tried to update my Drupal site from 8.3.7 to 8.4.0, but the site crashes irrevocably when I try to carry out the database update.

I put the site into maintenance mode, and deleted composer.lock and the vendor directory. I changed the Drupal/core and symfony/css-selector versions in composer.json to ~8.4 and ~3.3 respectively. I used
composer update drupal/core --with-dependencies
This appeared to work successfully.
However, when I visited /update.php, got the database update page, and continued to the update, the process crashed after 5 updates (out of 15) with the message

An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /update.php/start?id=6&op=do_nojs&op=do
StatusText: Internal Server Error
ResponseText:

and the site was completely broken. All attempts to visit any page on the site now produced an error message
The website has encountered an error ...
(I forgot to note the exact wording) on an otherwise blank page.

I don't understand the error message. There was no ResponseText.

I reverted to the backup 8.3.7 and database and tried /update.php, in case there were earlier database updates outstanding, but I got a report "no pending updates".

Is this a bug, or is there something I can do to fix it?

Comments

anthonyjs created an issue. See original summary.

cilefen’s picture

cilefen commented
Category: Support request » Bug report
Issue tags: +8.4.0 update

What was logged by the server when the 500 occurred?

alan d.’s picture

alan d. commented

The most common appears to be #2915332: Constructing service "validation.constraint" from a parent definition is not supported at build time

I updated all of the sites that used Libraries, so I'm not sure if the patch in the issue mentioned works, if your lucky, no need to revert down to upgrade again :)

If that doesn't help, if you can, roll back to 8.3.x

These were the main steps I used, mostly pre-update. Renaming the vendors directory forces this to be regenerated with all of the right dependencies, and the global update for good measure, but composer update drupal/libraries at a minimum instead if you have that.

composer global update drush/drush
mv vendors _vendors
composer update drupal/core --with-dependencies
composer update

Edit composer.json to go up to ~8.4, then try to update core.

I had on average 3 fatal errors related to this update and noted misc other bugs. You definitely need to get the error reporting / traces enabled to show what is happening.

cilefen’s picture

cilefen commented
Status: Active » Postponed (maintainer needs more info)

Version: 8.3.6 » 8.3.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

pameeela’s picture

pameeela commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
Issue tags: +Bug Smash Initiative

Thanks for reporting this issue. We rely on issue reports like this one to resolve bugs and improve Drupal core.

As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)".

Since there were no specific steps to reproduce the issue provided since the issue was postponed, I'm marking the issue "Closed (cannot reproduce)". If anyone can provide complete steps to reproduce the issue (starting from "Install Drupal core"), document those steps in the issue summary and set the issue status back to "Active".

Thanks!