You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2018/05/09 13:10:00 UTC

[jira] [Resolved] (OPENMEETINGS-1883) Mariadb - "Index column size too large" during install.

     [ https://issues.apache.org/jira/browse/OPENMEETINGS-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Solodovnik resolved OPENMEETINGS-1883.
--------------------------------------------
    Resolution: Information Provided

According to this [https://stackoverflow.com/questions/42043205/how-to-fix-mysql-index-column-size-too-large-laravel-migrate]

You need to set default charset and collation for your MariaDb and/or for OM DB

> Mariadb -  "Index column size too large" during install.
> --------------------------------------------------------
>
>                 Key: OPENMEETINGS-1883
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1883
>             Project: Openmeetings
>          Issue Type: Bug
>         Environment: Linux  4.14.36-1-MANJARO #1 SMP PREEMPT Tue Apr 24 19:16:26 UTC 2018 x86_64 GNU/Linux
> openmeetings  4.0.3-1
> $ mysql -V
> mysql  Ver 15.1 Distrib 10.1.32-MariaDB, for Linux (x86_64) using readline 5.1
> /etc/mysql/my.cnf 
> [mysqld]
> innodb_file_format = Barracuda
> innodb_file_per_table = 1
> innodb_large_prefix
> #collation_server=utf8_unicode_ci
> #collation_server=utf8_general_ci
> #character_set_server=utf8
>            Reporter: No Bicycle
>            Assignee: Maxim Solodovnik
>            Priority: Major
>
> $cd /opt/openmeetings
> $sudo ./red5-debug.sh
> [INFO] [Loader:/openmeetings] org.red5.server.Server - Add mapping global: default host: 127.0.0.1 context: openmeetings
> DEBUG 05-07 08:25:33.499 o.a.o.c.r.ScopeApplicationAdapter:343 [r:/openmeetings] - start: Scope [name=openmeetings, path=/default, type=APPLICATION, autoStart=true, creationTime=1525652732657, depth=1, enabled=true, running=false]
> DEBUG 05-07 08:25:33.529 o.a.o.c.r.ScopeApplicationAdapter:127 [r:/openmeetings] - webAppPath : /opt/openmeetings/webapps/openmeetings
> ERROR 05-07 08:25:34.472 o.a.o.c.r.ScopeApplicationAdapter:146 [r:/openmeetings] - [appStart]
> org.springframework.transaction.CannotCreateTransactionException: Could not open JPA EntityManager for transaction; nested exception is <openjpa-2.4.2-r422266:1777108 nonfatal general error> org.apache.openjpa.persistence.*PersistenceException: Index column size too large.* The maximum column size is 767 bytes. {stmnt 1441795057 *CREATE TABLE configuration* (id BIGINT NOT NULL AUTO_INCREMENT, deleted BIT NOT NULL, inserted DATETIME, updated DATETIME, comment TEXT, fromVersion VARCHAR(255), om_key VARCHAR(255), type SMALLINT, value VARCHAR(255), user_id BIGINT, PRIMARY KEY (id), UNIQUE U_CNFGRTN_OM_KEY (om_key)) ENGINE = innodb} [code=1709, state=HY000]
>  
> When the install failed I saw 4 tables in the openmeetings database: address, appointment, conference_log, chat. For each of them I ran  ALTER TABLE openmeetings.<table> ROW_FORMAT=DYNAMIC;
> This did fix errors for those tables; but the configuration table error can't be fixed that way because the error seems generated during  create table.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)