You are not logged in.

#1 2021-07-21 10:15:12

Registered: 2017-08-21
Posts: 34

[SOLVED] Issues on nextcloud 22.0.0 and mariadb 10.6

after upgrade of nextcloud to 22.0.0-2 and mariadb to 10.6.3-1 i got an internal server error.
In nextcloud.log i found:

General error: 4047 InnoDB refuses to write tables with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.

Background and solution here


#2 2021-07-21 10:30:39

From: Hannover
Registered: 2016-05-06
Posts: 1,203

Re: [SOLVED] Issues on nextcloud 22.0.0 and mariadb 10.6

Since links rot, the workaround is to add


to the section [mariadb] in /etc/my.cnf.d/server.cnf.


#3 Yesterday 12:28:25

From: Bulgaria
Registered: 2013-02-23
Posts: 272

Re: [SOLVED] Issues on nextcloud 22.0.0 and mariadb 10.6

I have no luck with this workarond.
I've tried adding it to the [mariadb], [mariadb-10.6] and [mysqld] sections of /etc/my.cnf.d/server.cnf
After restarting the mariadb service, I still get an internal server error.
However, running:

SET GLOBAL innodb_read_only_compressed=OFF;

in the mariadb SQL client, it seems to make this problem go away until the next service restart.
I tried using "0", "off", "OFF" for values in the config. For some reason they all get accepted just fine, but they don't seem to do anything.
What I haven't tried yet is to add it as a command-line argument for starting the service: "--innodb_read_only_compressed=OFF".
The reason is because I haven't found a way to do it without modifying the package systemd service file, which will be overwritten upon the next update.

Last edited by smirky (Yesterday 12:29:21)

Personal spot  ::  ::  Try not to get lost!


Board footer

Powered by FluxBB