Nextcloud 18 update of this weekend (19-20/02) has nextcloud failing to start

snap
1

Hello,

sometime this weekend, snap in track 18 updated 18/edge (27832) to 18/stable(?) 25109.

However there is something that makes the mysql of 25109 choke on the DB, giving errors like

2022-02-20T04:07:20.017638Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000! 2022-02-20 05:07:20 0x7fdf91b12740 InnoDB: Assertion failure in thread 140598198740800 in file ut0ut.cc line 918 InnoDB: We intentionally generate a memory trap.

It could be something related to the innodb settings, but I do not know if I can touch the /snap/nextcloud/my.cnf file.

I reverted the snap and I will try to migrate again in another VM.

Did anyone else have the same issue and managed to fix it in a proper and clean way?

Regards

2

You probably know this, but Nextcloud 18 is long out of support and no longer receiving updates. Edge was supposed to be closed long ago. You might consider upgrading to a supported version.