[NC 21]: Error upgrading with foreign tables in NC database #25748
Comments
0xFFFFFFFFFFFFFFFFFF
added
0. Needs triage
|
I am on mariadb 10.5.8 and the update for NC 21 was successful. |
Thank you for the suggestion, but unfortunately that didn't work out. |
|
Cannot upgrade on MariaDB 10.5.9 either |
tflidd
changed the title
|
I'm also having the same error while upgrading to NC21 (although I'm using Mysql8 and Docker). |
|
That must be an app that gets broken.
Here is my app list. I'm successful on nextcloud 21 with mariadb 10.5.8 |
I checked which apps are disabled on your instance but enabled on mine. These are the apps I found: I tried to disable all of them (except for encryption; I am not sure whether this would corrupt my data). Unfortunately, the updater returns me the same error message. I was able to enable all of these again except for |
|
I've got the same error, using docker image fpm-alpine |
|
You may disable the migration / repair step as workaround: Insert a new line before the above line with |
|
I was able to workaround the issue by temporarily adding the mapping |
|
I can confirm this issue for MariaDB 10.3.27 on Debian 10.8. |
|
I can confirm this issue on PostgreSQL 12 when using |
I can confirm this workaround works. Thanks! I suppose something similar can be done for PostgresPlatform. |
This table belongs to phpmyadmin 🤔 |
I just tried this hoping that it might fix my issue #25761 , had no effect whatsoever (I didn't think it would but worth a try) |
Indeed. For some reason phpMyAdmin created some tables into my nextcloud database, although there is a separate one for phpMyAdmin. |
|
As mentioned, i experienced the same issue. I'm also using phpmyadmin. Edit: After reading this i deleted all pma tables inside my nextcloud database. Nevertheless Neziak's hotfix works. |
After upgrading successfully, can i undo the change? |
In my case if I was undoing the change the error started to appear again. So I left the change. I didn't remove the pma-tables, but I'm going to try it later. |
I undid the change after the upgrade and didn't encounter any issues. Anyway, I have now removed those 'pma__*' tables since I no longer use phpMyAdmin. Those tables shouldn't have been created in the Nextcloud schema in the first place. |
|
After i removed the pma tables, applied the hotfix and upgraded successfully, now, if i undo the hotfix, i get this logging error: Doctrine\DBAL\Exception: Unknown database type enum requested, Doctrine\DBAL\Platforms\MariaDb1027Platform may not support it. Additionally the Overview says under Security & setup warnings: |
|
I ran into this while updating Nextcloud from 20 to 21. I was able to solve this by just dropping all the
However, I would argue that it should not matter to Nextcloud if there are other tables in the DB. |
Lucky you, sadly dropping the pma tables did not fix the problem for me. |
|
@AlexCloudDev, you may want to check the trace in your log file to find out which table is causing the error. This was how I managed to find that it was the "pma__*" tables that were causing the issue in my case. {
"file":"/var/www/html/3rdparty/doctrine/dbal/src/Schema/AbstractSchemaManager.php",
"line":172,
"function":"_getPortableTableColumnList",
"class":"Doctrine\\DBAL\\Schema\\AbstractSchemaManager",
"type":"->",
"args":[
"pma__usergroups",
"nextcloud",
[
{
"Field":"usergroup",
"Type":"varchar(64)",
"Null":"NO",
"Key":"PRI",
"Default":null,
"Extra":"",
"Comment":"",
"CharacterSet":"utf8",
"Collation":"utf8_bin"
},
{
"Field":"tab",
"Type":"varchar(64)",
"Null":"NO",
"Key":"PRI",
"Default":null,
"Extra":"",
"Comment":"",
"CharacterSet":"utf8",
"Collation":"utf8_bin"
},
{
"Field":"allowed",
"Type":"enum('Y','N')",
"Null":"NO",
"Key":"PRI",
"Default":"'N'",
"Extra":"",
"Comment":"",
"CharacterSet":"utf8",
"Collation":"utf8_bin"
}
]
]
} |
|
Hey, So a solution to this problem could be to make sure no enum datatype field is present inside the nextcloud database. Thx for your help |
|
Fix #25882. Turn's out the filter for the database tables did not work anymore. After this patch it's fine to have other tables in the same database. |
0xFFFFFFFFFFFFFFFFFF
changed the title
worked for me on mysql Ver 15.1 Distrib 10.3.25-MariaDB, for debian-linux-gnueabihf (armv7l) using readline 5.2 |
|
Dropping all the PMA tables fixed the problem for me |
How to use GitHub
Steps to reproduce
Expected behaviour
the nextcloud instance should be updated successfully
Actual behaviour
update fails
Server configuration
Operating system: Arch Linux x86_64 Kernel: 5.10.17-hardened1-1-hardened
Web server: nginx 1.19.7
Database: Ver 15.1 Distrib 10.5.8-MariaDB, for Linux (x86_64) using readline 5.1
PHP version: PHP 8.0.2 (cli) (built: Feb 2 2021 18:26:02) ( NTS )
Nextcloud version: 21.0.0.18
Updated from an older Nextcloud: 20.0.7.1
Where did you install Nextcloud from: official Arch Linux repositories
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage: no
Are you using encryption: yes
Are you using an external user-backend: no
Client configuration
Browser: Mozilla Firefox 85.0.2 (64-Bit)
Operating system: Arch Linux x86_64
Logs
Web server error log
there is no recent nginx error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: