Skip to content
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

OwnCloud 10 Instalation Error MySql #28030

Closed
git-wessel opened this issue May 28, 2017 · 11 comments
Closed

OwnCloud 10 Instalation Error MySql #28030

git-wessel opened this issue May 28, 2017 · 11 comments
Assignees

Comments

@git-wessel
Copy link

git-wessel commented May 28, 2017

Expected behaviour

An fresh instalation of OwnCloud 10

Actual behaviour

The instalation is stuck on the install index page, with an error from MySql

Error while trying to create admin user: An exception occurred while executing 'CREATE TABLE oc_migrations (app VARCHAR(255) NOT NULL, version VARCHAR(255) NOT NULL, PRIMARY KEY(app, version)) DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci ENGINE = InnoDB':

SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes

Server configuration

Operating system:
Raspbian 8 (Debian 8)
Web server:
Apache2 - PHP5
Database:
MySql - On remote server (Zyxel Nas)
PHP version:
5
ownCloud version: (see ownCloud admin page)
10
Updated from an older ownCloud or fresh install:
no
Where did you install ownCloud from:
i downloaded the zip from owncloud.org

Can't acces because of the install error

The content of config/config.php:

https://gist.github.com/TheWesleyMan/c1639411bf7295ee5a60d716b3438b55

Are you using encryption: yes/no
nope

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
nope

Client configuration

Browser:
Chrome
Operating system:
Windows 10 (With Creators Update)

Already thanks for reading en possible help

@ghost
Copy link

ghost commented May 28, 2017

@TheWesleyMan Please edit your gist and remove the dbpassword. You might have exposed your DB password publicly so you should change all services using this to a new password.

MySql - On remote server (Zyxel Nas)

Try a local / default MySQL server on your local system first. Those NAS devices might show issues like missing/insufficient InnoDB support or similar which could cause this issue.

Edit

Might be also related to #23988

@git-wessel
Copy link
Author

git-wessel commented May 28, 2017

hi @kdslkdsaldsal the hashed password what is standing there isn't what my password is i have removed some bit of it but i'l remove it all.

i'm gonna try an local MySql.

Edit:
@kdslkdsaldsal i haven't found that on git. Thanks for sharing.

@PVince81
Copy link
Contributor

@DeepDiver1975 @tomneedham another key length issue (oc_migrations)

@arymkus
Copy link

arymkus commented Jun 2, 2017

Same for me (on FreeBSD 10.3)
upgrade log - https://gist.github.com/arymkus/3f186e75f1fb6017dfd9d00939f3c975
mysql is on the same host with owncloud installation.

@tomneedham
Copy link
Contributor

Why are app and version columns so crazy long?! Do we have any other restrictions on app name length? Version is a datetimestring so we can lock that down pretty easily. Won't be fun making another db table key fix migration -.-

@tomneedham tomneedham self-assigned this Jun 5, 2017
@tomneedham
Copy link
Contributor

So from research this is caused by strict mode being enabled on mysql, which highlights these issues. @DeepDiver1975 @PVince81 should we test using this in CI?

@git-wessel
Copy link
Author

git-wessel commented Jun 5, 2017

@tomneedham What is CI?

@tomneedham
Copy link
Contributor

@TheWesleyMan CI = Continuous Integration. We use it to automatically test our code changes against a suite of tests. If we ensure strict mode is enabled during the testing we would see these, and potentially other, error messages.

@PVince81
Copy link
Contributor

If we consider mysql / mariadb strict mode to be supported officially then it makes sense to add it to CI.

If everything that works in strict mode is also guaranteed to work in non-strict mode then maybe we can only run the tests in strict mode (and no tests in non-strict mode) to save CI time.

@DeepDiver1975 thoughts ?

@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

@lock
Copy link

lock bot commented Jul 31, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants