Copyright © 2012 Kaltura Inc.
All Rights Reserved. Designated trademarks and brands are the property of their respective owners.
Use of this web site constitutes acceptance of the Terms of Use and Privacy Policy.
EduVideo.org
Kaltura CE v3.0 installation error with MySQL
Mon, 05/16/2011 - 17:03
I run "php install.php" and enter all the necessary information and get an error during the MySQL db setup. These are the lines from the log file:
16.05.2011 12:29:37 USER Creating and initializing 'kaltura' database
16.05.2011 12:29:37 INFO Creating database kaltura
16.05.2011 12:29:37 INFO Executing mysql -h127.0.0.1 -uroot -p******** -P3306 kaltura < /kaltura/app/deployment/base/sql/01.schema.sql
16.05.2011 12:29:40 INFO Executing mysql -h127.0.0.1 -uroot -p******** -P3306 kaltura < /kaltura/app/deployment/base/sql/02.schema_updates.sql
16.05.2011 12:29:40 ERROR Executing command failed: ERROR 1064 (42000) at line 2: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'Type=MyISAM' at line 26
16.05.2011 12:29:40 INFO Sending install report
16.05.2011 12:29:40 USER Installation failed.
16.05.2011 12:29:40 USER Failed running database script /kaltura/app/deployment/base/sql/02.schema_updates.sql
I'm running a CentOS 5.6 server that has MySQL 5.5.12 installed. Any help would be appreciated.
Thanks,
Jack
I decided to install phpMyAdmin on the MySQL 5.5.12 server and manually test the database creation steps so that I could fix the files in the package/app/app/deployment/base/sql location so that the install script would run successfully.
I found that 02.schema_updates.sql and 10.cassiopea.sql contained CREATE statements that failed because of the Type=MyISAM at the end of each of them. I looked at the other SQL files and discovered that they used ENGINE=MyISAM. So I modified the SQL in the 02 and 10 files to use ENGINE-MyISAM instead.
This allowed "php install.php" to complete successfully.
FYI: I also tested these SQL modifications on a 5.1.48 MySQL server installation and they worked there as well for those running a different MySQL server but getting a similar error.