OpenNetAdmin

Track. Automate. Configure.

Home About Features Community Develop
Download this project as a tar.gz file

Install ona-v11.02.10.tar.gz Error

themons

03-03-2011 01:12:09

Hi all

I try to install ONA 11.02.10

The database is created in the server. but I have this error in the logs.

ERROR => There was an error processing tables: 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=INNODB DEFAULT CHARSET=utf8 DEFAULT COLLATE=utf8_general_ci' at line 8


Prerequisite checks
PHP version > 5.0: Yes
PHP mysql support: Yes
Has GMP support: Yes
Has mbstring support: Yes
/img/mti/ONA/www/local/config dir writable by '': Yes


Is there a way to manual create database and configuration file.

Thanks for your help

Matt

07-03-2011 11:40:20

Themons,

Sorry I've not replied sooner. busy busy busy..

I'm not too sure why it is you are getting this error in the first place. it might be worth digging into that a bit more.

As far as having a way to manually create the database and initial data load. This is something that I've overlooked thus far when I switched to the .xml based files. My plan is to start including updated .sql files so that people can manually load the tables and initial data if they need to. This is not something that is currently set up at this time.

However, you could try to do the following:

in /opt/ona/install you can load ona-tables.sql then load ona-data.sql.

once that is loaded to your database, try and run the installer to see if it picks up and does a proper upgrade. its a 50/50 shot but something to try at least.

I will be working on getting updated .sql files that will work better.

Matt

07-09-2011 11:01:31

So It would seem that there is an issue with mysql 5.5 that they changed how the define the database type. Key word is no longer "TYPE=innodb" it is now "ENGINE=innodb".

So until I get this fixed up permanently, you can either downgrade your mysql or edit the /opt/ona/install/ona-table_schema.xml file and change from TYPE to ENGINE.

I hope to have this fixed soon.