[GH-ISSUE #261] since 2.0.11 ,include 2.0.11 mysql 5.7.23 can not start #229

Closed
opened 2026-02-26 06:31:39 +03:00 by kerem · 1 comment
Owner

Originally created by @hangox on GitHub (Dec 17, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/261

Describe the bug
log is here

migration file "20190227065017_settings.js" failed
migration failed with error: alter table `setting` add primary key `setting_pkey`(`id`) - ER_TOO_LONG_KEY: Specified key was too long; max key length is 768 bytes
[12/17/2019] [2:14:16 AM] [Global   ] › ✖  error     alter table `setting` add primary key `setting_pkey`(`id`) - ER_TOO_LONG_KEY: Specified key was too long; max key length is 768 bytes
[12/17/2019] [2:14:17 AM] [Migrate  ] › ℹ  info      Current database version: 20190218060101
[12/17/2019] [2:14:17 AM] [Migrate  ] › ℹ  info      [settings] Migrating Up...
migration file "20190227065017_settings.js" failed
migration failed with error: create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists
[12/17/2019] [2:14:17 AM] [Global   ] › ✖  error     create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists
[12/17/2019] [2:14:18 AM] [Migrate  ] › ℹ  info      Current database version: 20190218060101
[12/17/2019] [2:14:18 AM] [Migrate  ] › ℹ  info      [settings] Migrating Up...
migration file "20190227065017_settings.js" failed
migration failed with error: create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists
[12/17/2019] [2:14:18 AM] [Global   ] › ✖  error     create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists
[12/17/2019] [2:14:19 AM] [Migrate  ] › ℹ  info      Current database version: 20190218060101
[12/17/2019] [2:14:19 AM] [Migrate  ] › ℹ  info      [settings] Migrating Up...
migration file "20190227065017_settings.js" failed
migration failed with error: create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists
[12/17/2019] [2:14:20 AM] [Global   ] › ✖  error     create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists
[12/17/2019] [2:14:21 AM] [Migrate  ] › ℹ  info      Current database version: 20190218060101
[12/17/2019] [2:14:21 AM] [Migrate  ] › ℹ  info      [settings] Migrating Up...
migration file "20190227065017_settings.js" failed
migration failed with error: create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists
[12/17/2019] [2:14:21 AM] [Global   ] › ✖  error     create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists

To Reproduce
just docker run

Expected behavior
start connect

Operating System
debain 10

Additional context
dockerversion: 18.03.1-ce
mysqlVersion : 5.7.23

Originally created by @hangox on GitHub (Dec 17, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/261 **Describe the bug** log is here ``` migration file "20190227065017_settings.js" failed migration failed with error: alter table `setting` add primary key `setting_pkey`(`id`) - ER_TOO_LONG_KEY: Specified key was too long; max key length is 768 bytes [12/17/2019] [2:14:16 AM] [Global ] › ✖ error alter table `setting` add primary key `setting_pkey`(`id`) - ER_TOO_LONG_KEY: Specified key was too long; max key length is 768 bytes [12/17/2019] [2:14:17 AM] [Migrate ] › ℹ info Current database version: 20190218060101 [12/17/2019] [2:14:17 AM] [Migrate ] › ℹ info [settings] Migrating Up... migration file "20190227065017_settings.js" failed migration failed with error: create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists [12/17/2019] [2:14:17 AM] [Global ] › ✖ error create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists [12/17/2019] [2:14:18 AM] [Migrate ] › ℹ info Current database version: 20190218060101 [12/17/2019] [2:14:18 AM] [Migrate ] › ℹ info [settings] Migrating Up... migration file "20190227065017_settings.js" failed migration failed with error: create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists [12/17/2019] [2:14:18 AM] [Global ] › ✖ error create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists [12/17/2019] [2:14:19 AM] [Migrate ] › ℹ info Current database version: 20190218060101 [12/17/2019] [2:14:19 AM] [Migrate ] › ℹ info [settings] Migrating Up... migration file "20190227065017_settings.js" failed migration failed with error: create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists [12/17/2019] [2:14:20 AM] [Global ] › ✖ error create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists [12/17/2019] [2:14:21 AM] [Migrate ] › ℹ info Current database version: 20190218060101 [12/17/2019] [2:14:21 AM] [Migrate ] › ℹ info [settings] Migrating Up... migration file "20190227065017_settings.js" failed migration failed with error: create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists [12/17/2019] [2:14:21 AM] [Global ] › ✖ error create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists ``` **To Reproduce** just docker run **Expected behavior** start connect **Operating System** debain 10 **Additional context** dockerversion: 18.03.1-ce mysqlVersion : 5.7.23
kerem 2026-02-26 06:31:39 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@chaptergy commented on GitHub (May 11, 2021):

This issue is fairly old, if you are still experiencing some problems, please open a new issue.

<!-- gh-comment-id:838981379 --> @chaptergy commented on GitHub (May 11, 2021): This issue is fairly old, if you are still experiencing some problems, please open a new issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#229
No description provided.