When installing a clean Drupal 8 version with Dutch selected as language, a database error occurs. Steps I followed:

  • Clean Drupal installation (drupal 8.0.0-beta7)
  • Dutch language selected
  • Standard installation profile selected
  • Database config provided
  • Installing modules
  • Importing Drupal translations (error)

It stops at 98% and throws the following error:

Uncaught exception thrown in shutdown function.Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.: UPDATE {batch} SET batch=:db_update_placeholder_0
WHERE (bid = :db_condition_placeholder_0) ; Array (array with the Dutch translations).......in Drupal\Core\Batch\BatchStorage->update() (line 85 of C:\xampp\htdocs\xampp\www\drupal8\core\lib\Drupal\Core\Batch\BatchStorage.php).Drupal\Core\Batch\BatchStorage->update(Array)
_batch_shutdown()
call_user_func_array('_batch_shutdown', Array)
_drupal_shutdown_function()

Tried it several times to be sure. Test machine: Windows 7, Xampp (Apache 2.4.10 / PHP 5.5.15 / MySQL 5.0.11). When installing with English, no error occurs.

Comments

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous at XIO commented

I cannot reproduce this on the 8.0.x branch. Could this already be resolved on the dev branch? I recall a similar issue, but I can't seem to find it.

stefan.r’s picture

stefan.r CreditAttribution: stefan.r commented

This might be a MySQL bug:

http://stackoverflow.com/questions/22637733/mysql-error-code-1118-row-si...

http://stackoverflow.com/questions/15585602/change-limit-for-mysql-row-s...

http://dba.stackexchange.com/questions/90096/row-size-too-large-8126

stefan.r’s picture

stefan.r CreditAttribution: stefan.r commented 
Important

Due to Bug #69477, redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. To address this bug, a patch introduced in MySQL 5.6.20 limits the size of redo log BLOB writes to 10% of the redo log file size. As a result of this limit, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields).

In MySQL 5.6.22, the redo log BLOB write limit is relaxed to 10% of the total redo log size (innodb_log_file_size * innodb_log_files_in_group). (Bug #19498877)

If this is actually the issue, maybe we could check for this in the database tasks in the installer?

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous at XIO commented
Status: Active » Postponed (maintainer needs more info)

We'll need more information from @tmansveld.

amateescu’s picture

amateescu CreditAttribution: amateescu for Drupal Association commented

Note that the required MySQL version has been updated to 5.5.3 recently (#2473301: Raise MySQL requirement to 5.5.3) so you should update your local environment before trying to install beta10, which will be released in three days.

tmansveld’s picture

tmansveld CreditAttribution: tmansveld commented

Whatever it was, it now works okay. I updated Xampp to run on PHP 5.6.8 and MySQL 5.6.24. Made a clean Drupal installation with beta10, selected Dutch as language and no problems at all.

tmansveld’s picture

tmansveld CreditAttribution: tmansveld commented
Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.