-
Notifications
You must be signed in to change notification settings - Fork 60
Upgrade 2021.02.2 failed at setup.php #7299
Comments
Hi cvantum, having the same issue, here. Probably you are updating an old database (not very old, though). Can you tell the output of the following SQL query: SELECT NAME, ROW_FORMAT
FROM information_schema.INNODB_SYS_TABLES
WHERE ROW_FORMAT IN('Redundant', 'Compact')
AND NAME NOT IN('SYS_DATAFILES', 'SYS_FOREIGN', 'SYS_FOREIGN_COLS', 'SYS_TABLESPACES', 'SYS_VIRTUAL', 'SYS_ZIP_DICT', 'SYS_ZIP_DICT_COLS')
HAVING NAME LIKE 'TINE_DB_NAME%' Please replace Old tables often have 'Compact', which would be 'DYNAMIC' in newer versions of MariaDB. |
For me changing ROW_FORMAT to DYNAMIC solved the issue of You can try this but have a backup in place, in case something goes wrong.
SELECT CONCAT('ALTER TABLE `', table_name, '` ROW_FORMAT=DYNAMIC;') AS sqlText FROM information_schema.tables WHERE table_schema = 'TINE_DB_NAME' The result is text with prepared commands for your database.
ALTER TABLE `tine20_accounts` ROW_FORMAT=DYNAMIC; and so forth.
Unfortunately, I do not know a way to permanently ensure that new tables are of the new ROW_FORMAT. However, it may be default for MariaDB versions after 10.2. Best |
Hello, thanks for your response. I can confim, that the value of The really bad side of this issue is, that we also have a BE-Version which could also run into this issue in the future. With way more affected tables:
Maybe devs can find a solution for this problem. At least for the BE-Version there is some time to find a sql-fix for upcoming releases. |
Right that's not my expertise, I do not have any experience on BE versions. |
hi, sorry for the late response. here is the upgrade howto for mariaDB (when you run into "Row size too large" errors):
|
Hello, thanks for your help. And i am sorry to open up this issue again. We ran those two tasks on our server. But firing up the migration-script we encountered a new issue:
If you need any further informations we can post them here too. Thank you in advance. |
Have you tried to run the update twice in a row (CLI: |
Hello, yes. First i updated the config at MariaDB. Restarted the service and looked at I tried to do an Upgrade with Unfortunately i had to rollback the server becuase with this state i wasn't table to work with it :) If you need any further informations, i will create a duplicate and can redo the steps on a non-productive system. |
Hello,
we are running Tine20 on a Debian 10 Server. Today morning we updated to the new version '2021.02.2' via
apt
. The apt-process ran without any issues. The upgrade via
setup.php
afterwards was leading to an error:php /usr/share/tine20/setup.php --config /etc/tine20/config.inc.php --update
The UI is still accessable and also the setup-UI via browser. While trying to update the applications on the browser the same error occur.
The text was updated successfully, but these errors were encountered: