OpenStack Error – Index column size too large. The maximum column size is 767 bytes [Solved]
2016-10-24 19:53
951 查看
文章原地址 https://techglimpse.com/openstack-db-sync-error-mysql-character-set-solution/
执行
时出现错误:CRITICAL keystone [-] DBError: (pymysql.err.InternalError) (1071, u'Specified key was too long; max key length is 767 bytes') [SQL: u'\nCREATE TABLE migrate_version (\n\trepository_id VARCHAR(250) NOT NULL, \n\trepository_path TEXT, \n\tversion INTEGER,
\n\tPRIMARY KEY (repository_id)\n)\n\n']
Overall, you need to perform below steps:
Replace utf8mb4 to utf8 in all configuration files
Reload mysqld daemon
Drop database keystone or glance or nova or neutron (for whichever service
you were getting error and don’t worry, you haven’t populated the database yet and it’s safe to remove)
Create database keystone or glance or nova or neutron
Try db_sync or populate the database using OpenStack commands. It should probably work, else try Fix 2.
解决方案:
1.将/etc/mysql/mariadb.conf.d目录下的所有.cnf文件中出现uft8mb4的地方都修改成uft8
2.重启数据库 service mysql restart
3.进入数据库把建立的keystone数据库删除
4.重新建立keystone数据库
5.输入su -s /bin/sh -c "keystone-manage db_sync" keystone 应该就可以运行了,不行的话实时Fix2.
同时推荐文章http://blog.csdn.net/zhujie_hades/article/details/52104116
执行
# su -s /bin/sh -c "keystone-manage db_sync" keystone
时出现错误:CRITICAL keystone [-] DBError: (pymysql.err.InternalError) (1071, u'Specified key was too long; max key length is 767 bytes') [SQL: u'\nCREATE TABLE migrate_version (\n\trepository_id VARCHAR(250) NOT NULL, \n\trepository_path TEXT, \n\tversion INTEGER,
\n\tPRIMARY KEY (repository_id)\n)\n\n']
Overall, you need to perform below steps:
Replace utf8mb4 to utf8 in all configuration files
Reload mysqld daemon
Drop database keystone or glance or nova or neutron (for whichever service
you were getting error and don’t worry, you haven’t populated the database yet and it’s safe to remove)
Create database keystone or glance or nova or neutron
Try db_sync or populate the database using OpenStack commands. It should probably work, else try Fix 2.
解决方案:
1.将/etc/mysql/mariadb.conf.d目录下的所有.cnf文件中出现uft8mb4的地方都修改成uft8
2.重启数据库 service mysql restart
3.进入数据库把建立的keystone数据库删除
4.重新建立keystone数据库
5.输入su -s /bin/sh -c "keystone-manage db_sync" keystone 应该就可以运行了,不行的话实时Fix2.
同时推荐文章http://blog.csdn.net/zhujie_hades/article/details/52104116
相关文章推荐
- Index column size too large. The maximum column size is 767 bytes.
- Index column size too large. The maximum column size is 767 bytes
- Index column size too large. The maximum column size is 767 bytes
- Data for Source Column 3(’Col3’) is too large for the specified buffer size.
- Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You
- Mysql [Err] 1118 - Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535.
- [Cassandra] Mutation of <x> bytes is too large for the maxiumum size of <y>
- mysql 报错:Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65
- Row size too large. The maximum row size for the used table type 解决
- SoapUI启动报错:The JVM could not be started. The maximum heap size (-Xmx) might be too large
- [MySQL 错误]ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not
- [SoapUI]The maximum heap size (-Xmx) might be too large
- SoapUI启动报错:The JVM could not be started. The maximum heap size (-Xmx) might be too large
- ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not counting B
- SoapUI:the maximum head size (-Xmx)might be too large ……
- [MySQL 错误]ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not
- SoapUI启动报错:The JVM could not be started. The maximum heap size (-Xmx) might be too large
- SoapUI启动报错:The JVM could not be started. The maximum heap size (-Xmx) might be too large
- ERROR 1118 : Row size too large. The maximum row size for the used table type
- ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not counting B