Not a bug, I just fucked something up and need help with database collation specifications #13987
Labels
Comments
WNYmathGuy
added
0. Needs triage
|
This got worse. One oddity I was suffering from today before it got way worse was the Files section of NC showed nothing. The tables for files are intact and the files and folders still exist on my server but the interface can't display them. NC wanted to do some updates and they errored out while trying to happen. They were throwing the error I mentioned in the initial post. Then after it failed NC got stuck in a non-working position and would only serve the "You got updates to do screen". When trying to run that update it' throws these errors: and the Detailed logs say: A wierd screen I got was this one: It could be because I was tinkering with the table character limits between update attempts. It seems that if MariaDB isn't ready for the max size character unique indexes, then Nextcloud can't be used in it because updates aren't limiting their char fields. Is their any good info on how to link to another MySQL server inside my network? |
|
Okay, so as of now I got this going. Changed the The first page that loaded was like the first image I added in the last note, but it had a list of all the app updates that went wrong since this shit-filled rabbit-hole trip started. So as of right now every app works except for the Files browser app... I don't understand the messages in the logs, but I'm pretty sure now that their all related to the file browser problem I'm having. Here are the latest entries. I can see the section where I tested the Gallery app (I think). |
|
BTW: Last night after the movement of the database from one MariaDB server to a different MySQL server I failed the code integrity check and will be using the previous solution I was given for that problem, but for the sake of this thread having the info, here is the failure list: SolutionSame as Closed Issue #12524, Running |
|
I must really be off the mark lately. I was wrong about that last post because the Rescan... takes me from the Also, I did the upgrade from 15.0.2 to 15.0.4 and the Files app started working normally again. I'm still getting a stream of error messages in the logs that resemble the ones attached above. So where were at right now is, don't move from MySQL 5.7 or higher to MariaDB 10.1 or lower. Also the infinitely fast propagating error messages have nothing to do with how well your Nextcloud Server is working. |
|
https://docs.nextcloud.com/server/16/admin_manual/configuration_database/mysql_4byte_support.html should give you a hint about the right database configuration. Check the discussion in #15058 as well. |
I think you missed the point but, okay. I showed I was The problem was I speculate that if a person initially deploys a Nextcloud server on a MariaDB type datastore, the freshly built tables with |
Afaik everything you need to change for mysql or mariadb is in the docs (some innodb settings). If you enabled utf8mb4 on mysql you need the same configuration for mariadb.
No ;) |
|
@kesselb I did have the MariaDB set-up with the appropriate defaults. Export dump to import dump did not work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What I hope to get out of this Issue Report
The template that created the database for nextcloud so that I can restore my collations to their optimal state.
Steps to reproduce
#1071 - Specified key was too long; max key length is 767 bytesutf8mb4withutf8in the dump file will solve all your problems. Reimport the dump file with no errors.ALTER TABLE oc_tablename CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;queries on all the tables, but have a small set of tables that won't allow the conversion.CHARfields withPRIMARYorUNIQUEindexes from 255 to 191, then run the step 5 queries on them.*_bincollation instead of the*_general_ci. Change over all the tables to the*_bincollation. (SHUT DOWN ALL GARBAGE SMASHERS ON THE DETENTION LEVEL!!!)Expected behavior
Data fields should have had the
CHARfield limits set more carefully on indexed fields for backward compatibility, like having 191 the max instead of the default 255.Actual behavior
A lot of strange things happened.
Server configuration
Operating system: Ubuntu Linux 18.04.1
Web server: Apache 2.4.29
Database: MariaDB 10.1.34
PHP version: 7.2.10
Nextcloud version: 15.0.2
Updated from an older Nextcloud/ownCloud or fresh install: Updated from 14, updated from 13, maybe updated from 12.
Where did you install Nextcloud from: The Nextcloud site directly.
Signing status:
Signing status
List of activated (and deactivated) apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: no
Are you using encryption: not the end-to-end one yet, but it's a LetsEncrypt SSL type server.
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: Firefox and Chrome
Operating system: Ubuntu 18.04.1 LTS Workstation
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
nextcloud.log
The text was updated successfully, but these errors were encountered: