Database Update Crashes after 11.1.7->11.2.2

Created on 8 July 2025, 4 days ago

Problem/Motivation

Error when updating database after updating 11.1.7->11.2.2 via composer

Steps to reproduce

update all modules
put site in maintenance mode
clear cache
run
composer require drupal/core-recommended:11.2.2 drupal/core-composer-scaffold:11.2.2 drupal/core-project-message:11.2.2 --update-with-all-dependencies

Go to update.php and run updates. Pending updates show as:

system module
• 11200 - Add a [time] column to the {simpletest} table, if existing.
• 11201 - Add the [alias] field to the {router} table.
• Updates entity_form_mode descriptions from empty string to null.
• Remove path key in system.file.

block module
• Updates the `depth` setting to NULL if it is 0 in any menu blocks.

file module
• Adds a value for the 'playsinline' setting of the 'file_video' formatter.

update module
• Removes the legacy 'Update Manager' disk cache.

views module
• Defaults `items_per_page` to NULL in Views blocks.
• Adds a default table CSS class.
• Clean-up empty remember_roles display settings for views filters.

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

Site is in invalid state and no page comes up. Fortunately, I backed up virtual server before updating and was able to restore.

Is there a log in the file system I can look at as the /admin/reports/dblog is not useable.
Also,
Is there a way to see what scripts are going to run and perhaps run them manually one by one to see which one broke.

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Active

Version

11.2 🔥

Component

database system

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Abontu
  • I updated 11.1.7->11.1.8 successfully.
    I tried 11.1.8->11.2.0 and had the same behavior/error as described above. Same 10 database updates were wanting to run and crashed.

  • Drush can show the logs. Also the 500 was probably logged by the web server.

  • Thanks for the quick reply cilefen .

    Can you please elaborate on "Drush can show the logs." I am not Drush savy. How do I use Drush to sow the logs? Also is there a way to get debug information.

    I realize the 500 was a web server error which happens when the underlying ajax call does not catch the error/exception. Something is happening during the update script perhaps a sql exception that is not handled and reported. It would be good if this was done in a transaction that could be rolled back if not completed. Whatever is happening the site goes completely down.

    Thanks!
    Chris

  • I did find a tutorial on drush but not sure it is up to date.

    https://www.codebales.com/comprehensive-guide-debugging-and-monitoring-d...

    I tried the suggested
    drush watchdog:show --type=database

    I suppose I can just use without a type. Just wondering if you know a better tutorial.

    Thanks again.

Production build 0.71.5 2024