Maybe it can help at the reconfigure time i got

== 0 AggregatedMigrations: migrating ==========================================
-- create_table("attachments", {:force=>true})
   -> 0.0347s
-- add_index("attachments", ["author_id"], {:name=>"index_attachments_on_author_id"})
   -> 0.0141s
-- add_index("attachments", ["container_id", "container_type"], {:name=>"index_attachments_on_container_id_and_container_type"})
   -> 0.0237s
-- add_index("attachments", ["created_on"], {:name=>"index_attachments_on_created_on"})
   -> 0.0248s
-- create_table("auth_sources", {:force=>true})
   -> 0.0509s
-- add_index("auth_sources", ["id", "type"], {:name=>"index_auth_sources_on_id_and_type"})
   -> 0.0160s
-- create_table("boards", {:force=>true})
   -> 0.0524s
-- add_index("boards", ["last_message_id"], {:name=>"index_boards_on_last_message_id"})
   -> 0.0163s
-- add_index("boards", ["project_id"], {:name=>"boards_project_id"})
   -> 0.0260s
-- create_table("changes", {:force=>true})
   -> 0.0483s
-- add_index("changes", ["changeset_id"], {:name=>"changesets_changeset_id"})
   -> 0.0151s
-- create_table("changesets", {:force=>true})
   -> 0.0483s
-- add_index("changesets", ["committed_on"], {:name=>"index_changesets_on_committed_on"})
   -> 0.0148s
-- add_index("changesets", ["repository_id", "revision"], {:name=>"changesets_repos_rev", :unique=>true})
rake aborted!
StandardError: An error has occurred, all later migrations canceled:

*Mysql2::Error: Specified key was too long; max key length is 767 bytes: CREATE UNIQUE INDEX `changesets_repos_rev`  ON `changesets` (`repository_id`, `revision`)
/opt/openproject/vendor/bundle/ruby/2.4.0/gems/mysql2-0.4.9/lib/mysql2/client.rb:120:in `_query'*

Later same MySQL error

/opt/openproject/bin/bundle:3:in `load'
/opt/openproject/bin/bundle:3:in `<main>'
ActiveRecord::StatementInvalid: Mysql2::Error: Specified key was too long; max key length is 767 bytes: CREATE UNIQUE INDEX `changesets_repos_rev`  ON `changesets` (`repository_id`, `revision`)
/opt/openproject/vendor/bundle/ruby/2.4.0/gems/mysql2-0.4.9/lib/mysql2/client.rb:120:in `_query'

and later again

What mysql database version and collation for the database are you using? The error is quite clear, in your encoding, the prefix length exceeds the capability of MySQL. This might be because you’re using the now suggested utf8mb4 encoding to make MySQL accept all UTF-8 characeters and not just a subset.

For more information, see https://stackoverflow.com/a/1814594/420614. Fore example, upgrading to MySQL 5.7. should resolve that issue.

Best,
Oliver

Hi,

Thanks for your answer.

Here is my version, apt update/upgrade done today. (debian 9)

mysql Ver 15.1 Distrib 10.1.26-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

-If it’s an innodb problem, maybe we can try https://stackoverflow.com/a/38675910/6427809
points 1 to 5 ?-

EDIT : not working.

Thanks,