[solved, kinda] install step 5 database setup problem!

bzink5

Joined: 2005-11-10
Posts: 6
Posted: Thu, 2005-11-10 05:24

hi, i'm on a fresh install and i've been fiddiling with this problem for a few hours now and i've searched the forums and nothing that i've found (unless i'm overlooking something) has applied or helped.
I would really appreciate any advice or thoughts to point me in the right direction

I'm using fresh installs of the following on a windows xp machine:
apache 2.0.55
php 4.4.1
mysql 5.0.15
i also have mambo 4.5.2.3 and phpMyAdmin 2.6.4 installed
they all seem to be in working order

i'm receiving the following error:

***
The database privileges test did not complete successfully.
Failed to create a DB test sequence.Check the returned error message and README.html for missing privileges and clean up the database.
***

and at the bottom:

--------------------------------------------------------------------------------
(mysql): SHOW TABLES
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
(mysql): -- This file was automatically generated from an XSL template, which is -- why it looks so ugly. Editing it by hand would be a bad idea. -- CREATE TABLE g2dbtest0_Schema ( g_name varchar( 128 ) NOT NULL , g_major int(11) NOT NULL , g_minor int(11) NOT NULL , PRIMARY KEY (g_name) ) TYPE=MyISAM
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
(mysql): INSERT INTO g2dbtest0_Schema ( g_name, g_major, g_minor ) VALUES ( 'Schema', 1, 0 )
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
(mysql): ALTER TABLE g2dbtest0_Schema ADD COLUMN g_testCol varchar( 128 ) , ADD INDEX g2dbtest0_Schema_18169 (g_testCol)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
(mysql): UPDATE g2dbtest0_Schema SET g_major=1, g_minor=1 WHERE g_name='Schema' AND g_major=1 AND g_minor=0
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
(mysql): ALTER TABLE g2dbtest0_Schema DROP INDEX g2dbtest0_Schema_18169
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
(mysql): UPDATE g2dbtest0_Schema SET g_major=1, g_minor=2 WHERE g_name='Schema' AND g_major=1 AND g_minor=1
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
(mysql): DELETE FROM g2dbtest0_Schema WHERE g_name = 'Schema'
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
(mysql): DROP TABLE g2dbtest0_Schema
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
(mysql): create table g2dbtest0_g2privtestseq (id int not null)
--------------------------------------------------------------------------------
1289: The 'InnoDB' feature is disabled; you need MySQL built with 'InnoDB' to have it working

adodb_mysql._execute(create table g2dbtest0_g2privtestseq (id int not null), false) % line 855, file: adodb.inc.php
adodb_mysql.execute(create table g2dbtest0_g2privtestseq (id int not null)) % line 193, file: adodb-mysql.inc.php
adodb_mysql.createsequence(g2dbtest0_g2privtestseq) % line 399, file: DatabaseSetupStep.class
databasesetupstep._testprivileges(mysql, Array[0]) % line 136, file: DatabaseSetupStep.class
databasesetupstep.loadtemplatedata(Array[1]) % line 167, file: index.php
--------------------------------------------------------------------------------

To the best of my knowledge I have already corrected the password length problem,
and i have created the database as described in the readme file
MySQL is setup for Multifunctional Database,
and pretty much everything is setup in the most basic default manner (localhost, root, etc)

any help is appreciated, thanx!

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Thu, 2005-11-10 12:58

please try the non-transactional mysql driver (in step 5, you can select from 2 different mysql drivers, choose the other one).

 
benc

Joined: 2005-11-09
Posts: 18
Posted: Thu, 2005-11-10 14:03

I'm having same problem excatly
There is obviously a bug or compatibility issue in gallery
There are now 3 of us with identical problems

 
benc

Joined: 2005-11-09
Posts: 18
Posted: Thu, 2005-11-10 14:08

Valiant

Your suggestion doesnt work
As I old you I already selected transactional SQL engine
There's either a bug in gallery or a compatibility issue
between Gallery2 and the latest versions of MySQL/PHP/IIS

Ben

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Thu, 2005-11-10 14:51

benc

- this topic is probably about mysql 5 / linux, not sure if it's windows
- i was talking to someone else, maybe the user selected the transactional driver and i recommended the non-transactional one

benc:
could you please try the following in a mysql shell (or phpmyadmon)?
create table g2dbtest0_g2privtestseq (id int not null);
do you get the following error?
1289: The 'InnoDB' feature is disabled; you need MySQL built with 'InnoDB' to have it working

or do you get an error when executing the following sql?
CREATE TABLE g2dbtest0_Schema ( g_name varchar( 128 ) NOT NULL , g_major int(11) NOT NULL , g_minor int(11) NOT NULL , PRIMARY KEY (g_name) ) TYPE=MyISAM;

 
benc

Joined: 2005-11-09
Posts: 18
Posted: Thu, 2005-11-10 16:55

Hey Valiant

I get the error from the first create command,
but not with the second one (with the MyISAM option)
This is surprising, because InnoDB engine is running according to my config

Let me know if I can help u fix this
Cheers
Ben

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Thu, 2005-11-10 17:03

well, i guess this means that (your) windows Mysql installation uses InnoDB as default engine / table type when none is specified in the create table command.
this certainly looks like a Mysql 5.x (windows) issue and G2 can't do much about it. We have to assume that when we use a CREATE table statetement using the defaults of your DBMS, then it must work.

can you report this issue on mysql.org?

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Thu, 2005-11-10 17:12

from #mysql:

Quote:
valiant
are there any mysql 5.x related known InnoDB issues, maybe just for windows? in short: 3 independent users of our software report that create table tblname (id int not null); gives them the following error with mysql 5. at least 2 of them use windows. error:
1289: The 'InnoDB' feature is disabled; you need MySQL built with 'InnoDB' to have it working
shabbs
valiant: edit the my.ini and comment out skip-innodb
inviso
valiant: install a version from mysql.com
inviso
valiant: or what shabbs said if it isn't some random installer from papajoe.com
valiant
shabbs, invisio: it seems it select InnoDB as default engine, but why would it do that if inndodb is skipped in my.ini ?
shabbs
valiant: because it's swedish
valiant
shabbs: lol, on a less sarcastic note, what might be the reason?
shabbs
valiant: my guess is at some point (version 4.1.10 I think) innodb became the default table, but in some installs the skip-innodb persists or was selected during the config
valiant
shabbs: ok, might explain it. thanks a bunch!

so the proposed solutions are:

edit the my.ini and comment out skip-innodb
(or:
download and install mysql 5 from mysql.com and not from anywhere else...)

 
benc

Joined: 2005-11-09
Posts: 18
Posted: Thu, 2005-11-10 20:21

Valiant

Unfortunately that's not the solution
My version is from MySQL.com
And skip-innodb is commented out
Problm still there
:-(

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Thu, 2005-11-10 20:23

did you restart mysql (including the mysql service) after changing my.ini ?

if that isn't the problem, please contact mysql.com / .org, report it as a bug.

 
benc

Joined: 2005-11-09
Posts: 18
Posted: Thu, 2005-11-10 20:35

I didnt need to restart mysql
(as skip-inndb was always commented out in my.ini)

I will try to report to mysql in a few days if i have time

I'll also check back here in a few days to see if you have found solution

Thanks anyway
Ben

 
tippex

Joined: 2005-11-09
Posts: 3
Posted: Thu, 2005-11-10 20:37

There is a few posts that say there could be an issue with the latest windows distro on mysql. Still trying to dig some more info out.

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Thu, 2005-11-10 20:39

tippex,

thanks for the information. keep us posted!

 
bzink5

Joined: 2005-11-10
Posts: 6
Posted: Thu, 2005-11-10 20:41

valiant, i am also receiving the same problem when using your code
skip-innodb was already commented out when i checked it too
i also received mysql from the official site
o, and i've tried the other mysql driver on step 5, i get the same exact error

i will seek help at the mysql forums, thank you for your help
and if you have any more information to provide it would also be much appreciated
because surely someone has encountered this problem and overcome it

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Thu, 2005-11-10 20:52

well, i can't provide more information.
reproducing the error is easy, just do:
create table test123 (id int not null);
and you'll get the error:
1289: The 'InnoDB' feature is disabled; you need MySQL built with 'InnoDB' to have it working

create table is very fundamental in databases, if it doesn't work, it's a bug in the database software.
g2 can't do anything about it.

please file a mysql bug and let us know when it is fixed.
(usually people who find the bug and can reproduce it should file the bug, thus i ask you all to file it)

 
bzink5

Joined: 2005-11-10
Posts: 6
Posted: Thu, 2005-11-10 21:30

i dunno if this tells you anything but when i type in "show innodb status;"
it gives me the error:
ERROR 1235 (42000): Cannot call SHOW INNODB STATUS because skip-innodb is defined

but i most certainly have it commented out! unless there's somewhere else that "skip-innodb" is called other than in the my.ini file?

or is there some other way to manually start the innodb feature?

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Thu, 2005-11-10 21:34

all questions that are better asked in the mysql forums / etc.
it's a new problem and if someone might help, then the mysql community.

 
bzink5

Joined: 2005-11-10
Posts: 6
Posted: Thu, 2005-11-10 21:56

ya i just did that
it's here, just for reference:
http://forums.mysql.com/read.php?22,53946,53946#msg-53946

o well, thanx for the help thou in narrowing down the possible problem!

 
bzink5

Joined: 2005-11-10
Posts: 6
Posted: Sat, 2005-11-12 03:43

i got it to work!
i just set the default storage engine in mysql administrator to "myisam" instead of innodb and step 5 completed error free!
innodb still doesn't work but at least i got gallery2 to work
hope this helps someone else!

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Sat, 2005-11-12 04:03

thanks for letting us know.
but that's not really a satisfactory solution... hope they find the bug and release a fixed mysql soon.

 
bzink5

Joined: 2005-11-10
Posts: 6
Posted: Sat, 2005-11-12 04:29

ya i know, but at least gallery2 is useable, and that's good enough for me at least

 
pietheyn

Joined: 2005-11-13
Posts: 1
Posted: Sun, 2005-11-13 21:35

Hello,

I also experienced this same problem. I fixed it with the suggested workarround from bzink5 (so thanks!).

But maybe someone can tell me what would be bad about using myisam instead of innodb as the default storage. Is it slower?

Thanks in advance.

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Sun, 2005-11-13 22:07

myisam is faster than innodb, but you won't get transactions, so if something goes wrong in g2, the probability that g2 will be left in a corrupted state is larger when using myisam.

 
tippex

Joined: 2005-11-09
Posts: 3
Posted: Fri, 2005-11-18 13:16

Guys,

A post from the mysql forums.

I also had this problem and fixed it by deleting BOTH my DATA and LOG files at the same time and restarting the server.

For example,

Step 1. Stop MySQL service

Step 2. Delete files:

C:\Program Files\MySQL\MySQL Server 5.0\data\ib_logfile*
C:\MySQL Datafiles\ibdata*

Step 3: Restart MySQL service

MySQL InnoDB needs to create both DATA and LOGS at the same time -- it says this in the log file output. So if you don't delete both data and log files at the same time when it starts up it will fail to create the InnoDB database files properly and InnoDB will show up as DISABLED rather than DEFAULT (when using "show engines").

I have tried this solution and it worked perfectly.

Tip

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Fri, 2005-11-18 14:43