Table init fails for too big index

[rautamiekka]

Tested with 5.2-SNAPSHOT-b957 and 5.2-SNAPSHOT-b893, both fail to init the table[s] for this same error:

[22:21:03 WARN]: [AuthMe] Fatal error occurred during database connection! Authme initialization aborted! [SQLException]: Index column size too large. The maximum column size is 767 bytes.

I use InnoDB/XtraDB as the default engine. utf8mb4_unicode_ci is the default collation.

No AuthMe tables show up in the database.

EDIT: Clarification just in case: I'm on Linux with Percona Server 5.6.29-76.2 (equivalent MySQL version 5.6.29).

[sgdc3]

Sounds very strange, could you post your config please?

[rautamiekka]

There are no reasons to use MyISAM or -based engine anymore.

Config:

DataSource:
    # What type of database do you want to use?
    # Valid values: sqlite, mysql
    backend: 'MYSQL'
    # Enable database caching, should improve database performance
    caching: false
    # Database host address
    mySQLHost: 'localhost'
    # Database port
    mySQLPort: '3306'
    # Username about Database Connection Infos
    mySQLUsername: 'XXXXXX'
    # Password about Database Connection Infos
    mySQLPassword: 'XXXXXX'
    # Database Name, use with converters or as SQLITE database name
    mySQLDatabase: 'XXXXXX'
    # Table of the database
    mySQLTablename: 'authme'
    # Column of IDs to sort data
    mySQLColumnId: 'id'
    # Column for storing or checking players nickname
    mySQLColumnName: 'username'
    # Column for storing or checking players RealName
    mySQLRealName: 'realname'
    # Column for storing players passwords
    mySQLColumnPassword: 'password'
    # Column for storing players emails
    mySQLColumnEmail: 'email'
    # Column for storing if a player is logged in or not
    mySQLColumnLogged: 'isLogged'
    # Column for storing players ips
    mySQLColumnIp: 'ip'
    # Column for storing players lastlogins
    mySQLColumnLastLogin: 'lastlogin'
    # Column for storing player LastLocation - X
    mySQLlastlocX: 'x'
    # Column for storing player LastLocation - Y
    mySQLlastlocY: 'y'
    # Column for storing player LastLocation - Z
    mySQLlastlocZ: 'z'
    # Column for storing player LastLocation - World Name
    mySQLlastlocWorld: 'world'
    # Enable this when you allow registration through a website
    mySQLWebsite: false

ExternalBoardOptions:
    # Column for storing players passwords salts
    mySQLColumnSalt: ''
    # Column for storing players groups
    mySQLColumnGroup: ''
    # -1 means disabled. If you want that only activated players
    # can log into your server, you can set here the group number
    # of unactivated users, needed for some forum/CMS support
    nonActivedUserGroup: -1
    # Other MySQL columns where we need to put the username (case-sensitive)
    mySQLOtherUsernameColumns: []
    # How much log2 rounds needed in BCrypt (do not change if you do not know what it does)
    bCryptLog2Round: 10
    # phpBB table prefix defined during the phpBB installation process
    phpbbTablePrefix: 'phpbb_'
    # phpBB activated group ID; 2 is the default registered group defined by phpBB
    phpbbActivatedGroupId: 2
    # Wordpress prefix defined during WordPress installation
    wordpressTablePrefix: 'wp_'

Converter:
    Rakamak:
        # Rakamak file name
        fileName: 'users.rak'
        # Rakamak use IP?
        useIP: false
        # Rakamak IP file name
        ipFileName: 'UsersIp.rak'
    CrazyLogin:
        # CrazyLogin database file name
        fileName: 'accounts.db'

settings:
    # The name shown in the help messages
    helpHeader: 'Login'
    sessions:
        # Do you want to enable the session feature?
        # If enabled, when a player authenticates successfully,
        # his IP and his nickname is saved.
        # The next time the player joins the server, if his IP
        # is the same as last time and the timeout hasn't
        # expired, he will not need to authenticate.
        enabled: false
        # After how many minutes should a session expire?
        # 0 for unlimited time (Very dangerous, use it at your own risk!)
        # Remember that sessions will end only after the timeout, and
        # if the player's IP has changed but the timeout hasn't expired,
        # the player will be kicked from the server due to invalid session
        timeout: 10
        # Should the session expire if the player tries to log in with
        # another IP address?
        sessionExpireOnIpChange: true
    # Message language, available: en, de, br, cz, pl, fr, ru, hu, sk, es, zhtw, fi, zhcn, lt, it, ko, pt
    messagesLanguage: 'en'
    restrictions:
        # Keeps collisions disabled for logged players
        # Works only with MC 1.9
        keepCollisionsDisabled: false
        # Can not authenticated players chat?
        # Keep in mind that this feature also blocks all commands not
        # listed in the list below.
        allowChat: false
        # Hide the chat log from players who are not authenticated?
        hideChat: false
        # Allow unlogged users to use all the commands if registration is not forced!
        # WARNING: use this only if you need it!
        allowAllCommandsIfRegistrationIsOptional: false
        # Allowed commands for unauthenticated players
        allowCommands:
        - '/login'
        - '/register'
        - '/l'
        - '/reg'
        - '/email'
        - '/captcha'
        # Max number of allowed registrations per IP
        # The value 0 means an unlimited number of registrations!
        maxRegPerIp: 3
        # Minimum allowed username length
        minNicknameLength: 3
        # Maximum allowed username length
        maxNicknameLength: 16
        # When this setting is enabled, online players can't be kicked out
        # due to "Logged in from another Location"
        # This setting will prevent potential security exploits.
        ForceSingleSession: true
        # If enabled, every player will be teleported to the world spawnpoint
        # after successful authentication.
        # The quit location of the player will be overwritten.
        # This is different from "teleportUnAuthedToSpawn" that teleport player
        # back to his quit location after the authentication.
        ForceSpawnLocOnJoinEnabled: true
        # This option will save the quit location of the players.
        SaveQuitLocation: false
        # To activate the restricted user feature you need
        # to enable this option and configure the AllowedRestrictedUser field.
        AllowRestrictedUser: false
        # The restricted user feature will kick players listed below
        # if they don't match the defined IP address.
        # Example:
        #     AllowedRestrictedUser:
        #     - playername;127.0.0.1
        AllowedRestrictedUser:
        - 'playername;127.0.0.1'
        # Should unregistered players be kicked immediately?
        kickNonRegistered: false
        # Should players be kicked on wrong password?
        kickOnWrongPassword: true
        # Should not logged in players be teleported to the spawn?
        # After the authentication they will be teleported back to
        # their normal position.
        teleportUnAuthedToSpawn: false
        # Can unregistered players walk around?
        allowMovement: false
        # Should not authenticated players have speed = 0?
        # This will reset the fly/walk speed to default value after the login.
        removeSpeed: true
        # After how many seconds should players who fail to login or register
        # be kicked? Set to 0 to disable.
        timeout: 30
        # Regex syntax of allowed characters in the player name.
        allowedNicknameCharacters: '[a-zA-Z0-9_ .]*'
        # How far can unregistered players walk?
        # Set to 0 for unlimited radius
        allowedMovementRadius: 100
        # Enable double check of password when you register
        # when it's true, registration requires that kind of command:
        # /register <password> <confirmPassword>
        enablePasswordConfirmation: true
        # Should we protect the player inventory before logging in? Requires ProtocolLib.
        ProtectInventoryBeforeLogIn: true
        # Should we deny the tabcomplete feature before logging in? Requires ProtocolLib.
        DenyTabCompleteBeforeLogin: true
        # Should we hide the tablist before logging in? Requires ProtocolLib.
        HideTablistBeforeLogin: true
        # Should we display all other accounts from a player when he joins?
        # permission: /authme.admin.accounts
        displayOtherAccounts: true
        # WorldNames where we need to force the spawn location for ForceSpawnLocOnJoinEnabled
        # Case-sensitive!
        ForceSpawnOnTheseWorlds:
        - 'world'
        - 'world_nether'
        - 'world_the_end'
        # Ban ip when the ip is not the ip registered in database
        banUnsafedIP: false
        # Spawn priority; values: authme, essentials, multiverse, default
        spawnPriority: 'authme,essentials,multiverse,default'
        # Maximum Login authorized by IP
        maxLoginPerIp: 0
        # Maximum Join authorized by IP
        maxJoinPerIp: 0
        # AuthMe will NEVER teleport players if set to true!
        noTeleport: false
        # Regex syntax for allowed chars in passwords
        allowedPasswordCharacters: '[\x21-\x7E]*'
    GameMode:
        # Force survival gamemode when player joins?
        ForceSurvivalMode: false
    unrestrictions:
        # Below you can list all account names that
        # AuthMe will ignore for registration or login, configure it
        # at your own risk!! Remember that if you are going to add
        # nickname with [], you have to delimit name with ' '.
        # this option add compatibility with BuildCraft and some
        # other mods.
        # It is case-sensitive!
        UnrestrictedName: []
    security:
        # Minimum length of password
        minPasswordLength: 5
        # Maximum length of password
        passwordMaxLength: 30
        # This is a very important option: every time a player joins the server,
        # if they are registered, AuthMe will switch him to unLoggedInGroup.
        # This should prevent all major exploits.
        # You can set up your permission plugin with this special group to have no permissions,
        # or only permission to chat (or permission to send private messages etc.).
        # The better way is to set up this group with few permissions, so if a player
        # tries to exploit an account they can do only what you've defined for the group.
        # After, a logged in player will be moved to his correct permissions group!
        # Please note that the group name is case-sensitive, so 'admin' is different from 'Admin'
        # Otherwise your group will be wiped and the player will join in the default group []!
        # Example unLoggedinGroup: NotLogged
        unLoggedinGroup: 'unLoggedinGroup'
        # Possible values: MD5, SHA1, SHA256, WHIRLPOOL, XAUTH, MD5VB, PHPBB,
        # MYBB, IPB3, PHPFUSION, SMF, XENFORO, SALTED2MD5, JOOMLA, BCRYPT, WBB3, SHA512,
        # DOUBLEMD5, PBKDF2, PBKDF2DJANGO, WORDPRESS, ROYALAUTH, CUSTOM (for developers only)
        passwordHash: 'XAUTH'
        # Salt length for the SALTED2MD5 MD5(MD5(password)+salt)
        doubleMD5SaltLength: 8
        # If password checking return false, do we need to check with all
        # other password algorithm to check an old password?
        # AuthMe will update the password to the new password hash
        supportOldPasswordHash: false
        # Prevent unsafe passwords from being used; put them in lowercase!
        # unsafePasswords:
        # - '123456'
        # - 'password'
        unsafePasswords:
        - '123123'
        - '123321'
        - 'password'
        - 'salasana'
        - '1234567890'
        - '123456789'
        - '12345678'
        - '1234567'
        - '123456'
        - 'fuckyou'
        - 'youfuck'
        - 'hacker'
        - 'passw0rd'
        - 'pa55word'
        - 'pa55wrd'
        - 'passwrd'
        - 'pa55w0rd'
        - '12301230'
        - 'minecraft'
        - 'rautamiekka.org'
        - 'rautamiekka'
        - 'epriih'
        - 'eprimc'
        - 'eprimex'
        - 'qwertyuiop'
        - 'qwertyuio'
        - 'qwertyui'
        - 'qwertyu'
        - 'qwerty'
        - 'qwert'
        - 'lollol'
        - 'l0ll0l'
        - '131211'
        - '90000.0'
        - 'asdasdasd'
        - 'asdasd123123'
        - 'asdasdasd123123123'
    registration:
        # Enable registration on the server?
        enabled: true
        # Send every X seconds a message to a player to
        # remind him that he has to login/register
        messageInterval: 5
        # Only registered and logged in players can play.
        # See restrictions for exceptions
        force: true
        # Do we replace password registration by an email registration method?
        enableEmailRegistrationSystem: false
        # Enable double check of email when you register
        # when it's true, registration requires that kind of command:
        # /register <email> <confirmEmail>
        doubleEmailCheck: false
        # Do we force kick a player after a successful registration?
        # Do not use with login feature below
        forceKickAfterRegister: false
        # Does AuthMe need to enforce a /login after a successful registration?
        forceLoginAfterRegister: false
    # Force these commands after /login, without any '/', use %p to replace with player name
    forceCommands: []
    # Force these commands after /login as service console, without any '/'. Use %p to replace with player name
    forceCommandsAsConsole: []
    # Force these commands after /register, without any '/', use %p to replace with player name
    forceRegisterCommands: []
    # Force these commands after /register as a server console, without any '/'. Use %p to replace with player name
    forceRegisterCommandsAsConsole: []
    # Enable to display the welcome message (welcome.txt) after a registration or a login
    # You can use colors in this welcome.txt + some replaced strings:
    # {PLAYER}: player name, {ONLINE}: display number of online players, {MAXPLAYERS}: display server slots,
    # {IP}: player ip, {LOGINS}: number of players logged, {WORLD}: player current world, {SERVER}: server name
    # {VERSION}: get current bukkit version, {COUNTRY}: player country
    useWelcomeMessage: true
    # Do we need to broadcast the welcome message to all server or only to the player? set true for server or false for player
    broadcastWelcomeMessage: false
    # Should we delay the join message and display it once the player has logged in?
    delayJoinMessage: true
    # Should we remove join messages altogether?
    removeJoinMessage: true
    # Should we remove leave messages?
    removeLeaveMessage: true
    # Do we need to add potion effect Blinding before login/reigster?
    applyBlindEffect: false
    # Do we need to prevent people to login with another case?
    # If Xephi is registered, then Xephi can login, but not XEPHI/xephi/XePhI
    preventOtherCase: false

permission:
    # Take care with this option; if you don't want
    # to use Vault and group switching of AuthMe
    # for unloggedIn players, set this setting to true.
    # Default is false.
    EnablePermissionCheck: false

Email:
    # Email SMTP server host
    mailSMTP: 'smtp.gmail.com'
    # Email SMTP server port
    mailPort: 465
    # Email account which sends the mails
    mailAccount: 'XXXXXX'
    # Email account password
    mailPassword: 'XXXXXX'
    # Custom sender name, replacing the mailAccount name in the email
    mailSenderName: 'rautamiekka.org-support'
    # Recovery password length
    RecoveryPasswordLength: 8
    # Mail Subject
    mailSubject: 'EpriMC 1.9 Survival 0 new password'
    # Like maxRegPerIP but with email
    maxRegPerEmail: 1
    # Recall players to add an email?
    recallPlayers: false
    # Delay in minute for the recall scheduler
    delayRecall: 5
    # Blacklist these domains for emails
    emailBlacklisted:
    - '10minutemail.com'
    - 'that.com'
    - 'a.a'
    - 'asd.com'
    - 'ass.com'
    - 'fart.com'
    - 'hh.com'
    - 'nopederp.com'
    # Whitelist ONLY these domains for emails
    emailWhitelisted: []
    # Send the new password drawn in an image?
    generateImage: false
    # The OAuth2 token
    emailOauth2Token: ''

Hooks:
    # Do we need to hook with multiverse for spawn checking?
    multiverse: true
    # Do we need to hook with BungeeCord?
    bungeecord: false
    # Send player to this BungeeCord server after register/login
    sendPlayerTo: ''
    # Do we need to disable Essentials SocialSpy on join?
    disableSocialSpy: false
    # Do we need to force /motd Essentials command on join?
    useEssentialsMotd: false
    # Do we need to cache custom Attributes?
    customAttributes: false

Protection:
    # Enable some servers protection (country based login, antibot)
    enableProtection: false
    # Countries allowed to join the server and register, see http://dev.bukkit.org/bukkit-plugins/authme-reloaded/pages/countries-codes/ for countries' codes
    # PLEASE USE QUOTES!
    countries:
    - 'US'
    - 'GB'
    # Countries not allowed to join the server and register
    # PLEASE USE QUOTES!
    countriesBlacklist:
    - 'A1'
    # Do we need to enable automatic antibot system?
    enableAntiBot: true
    # Max number of players allowed to login in 5 secs before the AntiBot system is enabled automatically
    antiBotSensibility: 5
    # Duration in minutes of the antibot automatic system
    antiBotDuration: 10

Purge:
    # If enabled, AuthMe automatically purges old, unused accounts
    useAutoPurge: false
    # Number of Days an account become Unused
    daysBeforeRemovePlayer: 60
    # Do we need to remove the player.dat file during purge process?
    removePlayerDat: false
    # Do we need to remove the Essentials/users/player.yml file during purge process?
    removeEssentialsFile: false
    # World where are players.dat stores
    defaultWorld: 'world'
    # Do we need to remove LimitedCreative/inventories/player.yml, player_creative.yml files during purge process ?
    removeLimitedCreativesInventories: false
    # Do we need to remove the AntiXRayData/PlayerData/player file during purge process?
    removeAntiXRayFile: false
    # Do we need to remove permissions?
    removePermissions: false

Security:
    SQLProblem:
        # Stop the server if we can't contact the sql database
        # Take care with this, if you set this to false,
        # AuthMe will automatically disable and the server won't be protected!
        stopServer: true
    ReloadCommand:
        # /reload support
        useReloadCommandSupport: true
    console:
        # Remove spam from console?
        noConsoleSpam: false
        # Remove passwords from console?
        removePassword: true
        # Copy AuthMe log output in a separate file as well?
        logConsole: true
    captcha:
        # Player need to put a captcha when he fails too lot the password
        useCaptcha: false
        # Max allowed tries before request a captcha
        maxLoginTry: 5
        # Captcha length
        captchaLength: 5
    stop:
        # Kick players before stopping the server, that allow us to save position of players
        # and all needed information correctly without any corruption.
        kickPlayersBeforeStopping: true

BackupSystem:
    # Enable or disable automatic backup
    ActivateBackup: false
    # Set backup at every start of server
    OnServerStart: false
    # Set backup at every stop of server
    OnServerStop: true
    # Windows only mysql installation Path
    MysqlWindowsPath: 'C:\\Program Files\\MySQL\\MySQL Server 5.1\\'

[sgdc3]

@ljacqu what do you think about this issue?

[ljacqu]

We don't create an index on our table, do we? I wonder if the automatic one from the primary key is provoking this. But I'm not sure.

Not certain if I have the db engine OP mentioned but if so, I'll try to set it up

[rautamiekka]

XtraDB is the name of Percona's improved InnoDB (there's no distinction between the 2 apart from the name used for InnoDB which has received performance improvements), so a regular InnoDB from Oracle MySQL 5.6 will do all the same.

[EvilOlaf]

XtraDB is default in the MySQL fork MariaDB.

[ljacqu]

Authme.log should have the entire stacktrace of the error. If you could kindly post it, it would help us to pinpoint the cause.

[rautamiekka]

[04-24 22:13:22]: Connection arguments loaded, Hikari ConnectionPool ready!
[04-24 22:13:23]: ERROR: Can't initialize the MySQL database... Please check your database settings in the config.yml file! SHUTDOWN...
[04-24 22:13:23]: ERROR: If this error persists, please report it to the developer!
[04-24 22:13:23]: ERROR: Fatal error occurred during database connection! Authme initialization aborted! [SQLException]: Index column size too large. The maximum column size is 767 bytes.
[04-24 22:13:23]: java.sql.SQLException: Index column size too large. The maximum column size is 767 bytes.
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:959)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3870)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2546)
        at com.mysql.jdbc.StatementImpl.executeUpdateInternal(StatementImpl.java:1541)
        at com.mysql.jdbc.StatementImpl.executeLargeUpdate(StatementImpl.java:2605)
        at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1469)
        at fr.xephi.authme.libs.hikari.pool.ProxyStatement.executeUpdate(ProxyStatement.java:120)
        at fr.xephi.authme.libs.hikari.pool.HikariProxyStatement.executeUpdate(HikariProxyStatement.java)
        at fr.xephi.authme.datasource.MySQL.setupConnection(MySQL.java:167)
        at fr.xephi.authme.datasource.MySQL.<init>(MySQL.java:82)
        at fr.xephi.authme.AuthMe.setupDatabase(AuthMe.java:579)
        at fr.xephi.authme.AuthMe.onEnable(AuthMe.java:240)
        at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:292)
        at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:340)
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:405)
        at org.bukkit.craftbukkit.v1_9_R1.CraftServer.loadPlugin(CraftServer.java:361)
        at org.bukkit.craftbukkit.v1_9_R1.CraftServer.enablePlugins(CraftServer.java:321)
        at net.minecraft.server.v1_9_R1.MinecraftServer.t(MinecraftServer.java:411)
        at net.minecraft.server.v1_9_R1.MinecraftServer.l(MinecraftServer.java:376)
        at net.minecraft.server.v1_9_R1.MinecraftServer.a(MinecraftServer.java:331)
        at net.minecraft.server.v1_9_R1.DedicatedServer.init(DedicatedServer.java:269)
        at net.minecraft.server.v1_9_R1.MinecraftServer.run(MinecraftServer.java:527)
        at java.lang.Thread.run(Thread.java:745)

[04-24 22:13:23]: ERROR: THE SERVER IS GOING TO SHUT DOWN AS DEFINED IN THE CONFIGURATION!
[04-24 22:13:25]: AuthMe 5.2-SNAPSHOT-b893 disabled!
[04-24 22:13:25]: Waiting for 0 tasks to finish
[04-24 22:21:02]: Connection arguments loaded, Hikari ConnectionPool ready!
[04-24 22:21:03]: ERROR: Can't initialize the MySQL database... Please check your database settings in the config.yml file! SHUTDOWN...
[04-24 22:21:03]: ERROR: If this error persists, please report it to the developer!
[04-24 22:21:03]: ERROR: Fatal error occurred during database connection! Authme initialization aborted! [SQLException]: Index column size too large. The maximum column size is 767 bytes.
[04-24 22:21:03]: java.sql.SQLException: Index column size too large. The maximum column size is 767 bytes.
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:959)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3870)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2546)
        at com.mysql.jdbc.StatementImpl.executeUpdateInternal(StatementImpl.java:1541)
        at com.mysql.jdbc.StatementImpl.executeLargeUpdate(StatementImpl.java:2605)
        at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1469)
        at fr.xephi.authme.libs.hikari.pool.ProxyStatement.executeUpdate(ProxyStatement.java:120)
        at fr.xephi.authme.libs.hikari.pool.HikariProxyStatement.executeUpdate(HikariProxyStatement.java)
        at fr.xephi.authme.datasource.MySQL.setupConnection(MySQL.java:167)
        at fr.xephi.authme.datasource.MySQL.<init>(MySQL.java:82)
        at fr.xephi.authme.AuthMe.setupDatabase(AuthMe.java:583)
        at fr.xephi.authme.AuthMe.onEnable(AuthMe.java:245)
        at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:292)
        at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:340)
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:405)
        at org.bukkit.craftbukkit.v1_9_R1.CraftServer.loadPlugin(CraftServer.java:361)
        at org.bukkit.craftbukkit.v1_9_R1.CraftServer.enablePlugins(CraftServer.java:321)
        at net.minecraft.server.v1_9_R1.MinecraftServer.t(MinecraftServer.java:411)
        at net.minecraft.server.v1_9_R1.MinecraftServer.l(MinecraftServer.java:376)
        at net.minecraft.server.v1_9_R1.MinecraftServer.a(MinecraftServer.java:331)
        at net.minecraft.server.v1_9_R1.DedicatedServer.init(DedicatedServer.java:269)
        at net.minecraft.server.v1_9_R1.MinecraftServer.run(MinecraftServer.java:527)
        at java.lang.Thread.run(Thread.java:745)

[04-24 22:21:03]: ERROR: THE SERVER IS GOING TO SHUT DOWN AS DEFINED IN THE CONFIGURATION!
[04-24 22:21:03]: AuthMe 5.2-SNAPSHOT-b957 disabled!
[04-24 22:21:03]: Waiting for 0 tasks to finish```

[rautamiekka]

IMO the best way to fix this is to default to utf8_unicode_ci for the table since you won't be seeing something like Japanese letters anyway, while allowing for, for example, northern letters. utf8mb4_unicode_ci has support for many more characters, which can't be used in Minecraft. Or I don't think so.

The complaint is given for the username being an unique that exceeds the InnoDB index limits when using utf8mb4.

I've modified the table:

• password: ascii_bin
• ip: ascii_bin

Those give performance improvements since it won't help having them as _general_ci.

The improved table structure:

CREATE TABLE `authme` (
  `id` mediumint(8) UNSIGNED NOT NULL,
  `username` varchar(255) NOT NULL,
  `realname` varchar(255) NOT NULL,
  `password` varchar(255) CHARACTER SET ascii COLLATE ascii_bin NOT NULL,
  `ip` varchar(255) CHARACTER SET ascii COLLATE ascii_bin NOT NULL,
  `lastlogin` bigint(20) NOT NULL DEFAULT '0',
  `x` double NOT NULL DEFAULT '0',
  `y` double NOT NULL DEFAULT '0',
  `z` double NOT NULL DEFAULT '0',
  `world` varchar(255) NOT NULL,
  `email` varchar(255) NOT NULL DEFAULT 'your@email.com',
  `isLogged` tinyint(1) NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=COMPACT;

ALTER TABLE `authme`
  ADD PRIMARY KEY (`id`),
  ADD UNIQUE KEY `username` (`username`);

ALTER TABLE `authme`
  MODIFY `id` mediumint(8) UNSIGNED NOT NULL AUTO_INCREMENT;

[ljacqu]

Excellent analysis, @rautamiekka, thank you very much. My phpMyAdmin version only has InnoDB and with it I can't reproduce this bug with the 767 bytes. In hindsight it makes sense that the username is causing the issue, since username is set to 255 chars (at potentially 4 bytes each).

[rautamiekka]

Besides, Bukkit/Spigot defaults to something way shorter than 255 chars for usernames.

EDIT: http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/modification-development/1436534-minecraft-username-length says Minecraft Client is hardcoded to 16 while Server doesn't care.

[sgdc3]

16 for online mode clients. "unlimited" for SP clients ;)

[rautamiekka]

^ Offline mode too ?

[sgdc3]

Offline clients can use nicknames up to 24 char i think.

[coolty]

I am also experiencing this bug. Is there any update on this? This issue is causing great pains. I cannot use MyISAM engine. I have tried setting the innodb_large_prefix options but to no avail.

[ljacqu]

Thank you for bumping this. I will integrate rautamiekka's fix within the next 10 hours

[coolty]

Thanks! I look forward to it

[ljacqu]

@coolty It should be fixed from build nr. 1170 or above http://ci.xephi.fr/job/AuthMeReloaded/

Unfortunately, I don't have those database engines locally or on my webserver, so I could not test this with full certainty. I would be thankful for your feedback.

[coolty]

This works, thank you very much.

[ljacqu]

Thank for your reply—glad this is fixed :)