-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An exception occurred while executing 'INSERT INTO migrations
(app
,version
)
#7528
Comments
I was able to resolve this by updating the length of the
I ran
Then the upgrade script ran as expected. |
Weird - we set this to 255: server/lib/private/DB/MigrationService.php Line 108 in 0eebff1
Have you done some other changes before that? |
I just tested this and it works fine (on multiple instances):
Could it be that you migrated before from ownCloud? |
Yeah bet that's it. I originally installed ownCloud 10.0.3.3 then migrated to Nextcloud 12.0.4 RC before upgrading to the final 12.0.4 release. I manually installed the files then ran the migration script from the server. Then today testing Nextcloud 13 Beta. So perhaps this is a bug more in the migration script of ownCloud > Nextcloud and less of Nextcloud 12 > 13 that I'm just now running into. Here's the version line in ownCloud showing a length of 14: I'm not familiar enough with how the Nextcloud migration script works to check if this is indeed a problem with the |
@BandonRandon Thanks for the clarification: yes this is indeed the problem. There is the 177 characters limit. |
@MorrisJobke Glad we were able to get to the bottom of that. It's perhaps a super power of mine to find these edge cases in OSS ;) Just for clarity here, it seems to be the |
I never looked into migrations (yet). |
I shall have a look at this. |
I will mostlikely cover this by #5901 (that is currently the only point it mentions) |
I ran utf8mb4_bin;':SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes" What can I do? |
Steps to reproduce
Expected behaviour
For the database to finish upgrading
Actual behaviour
Got this error in both web interface and from ssh into the server.
Server configuration
Operating system: CentOS 6.9 (final)
Web server: Nginx 1.12.2
Database: mysql Ver 15.1 Distrib 10.2.11-MariaDB, for Linux (x86_64) using readline 5.1
PHP version: PHP 7.1.12 (cli) (built: Nov 27 2017 11:00:37) ( NTS )
Nextcloud version: (see Nextcloud admin page) 13 beta 3
Updated from an older Nextcloud/ownCloud or fresh install: existing 12.04
Where did you install Nextcloud from:
List of activated apps:
sudo -u nginx php occ app:list
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Nextcloud configuration:
sudo -u nginx php occ config:list
Are you using external storage, if yes which one: Have 2 AWS SE storage
Are you using encryption: no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Client configuration
Browser: Firefox 57.0.1
Operating system: MacOS 10.13.2
Nextcloud log (data/nextcloud.log)
The text was updated successfully, but these errors were encountered: