From: David T. <da...@mm...> - 2003-07-20 23:18:23
|
Just trying to run install-slash, I receive the error: ERROR 1005 at line 135: Can't create table './testdb/backup_blocks.frm' (errno: 150) I have MySQL 4.0.13-Max installed, do I need anything else? |
From: Alex M. <alex@OWAL.co.uk> - 2003-07-21 10:38:09
|
At 00:15 21/07/03, David Tseng wrote: >Just trying to run install-slash, I receive the error: > >ERROR 1005 at line 135: Can't create table './testdb/backup_blocks.frm' >(errno: 150) > >I have MySQL 4.0.13-Max installed, do I need anything else? Hello David, Please excuse me if this is a bit terse but you haven't really told us much. Are any tables created at all? Do you have MySQL logs switched on? (might be worth doing so - we need to find out why the table isn't created). Goodluck Alex Available for java/perl/C++/web development in London, UK or nearby. Apache FOP, Cocoon, Turbine, Struts,XSL:FO, XML, Tomcat, JSP http://www.OWAL.co.uk/ |
From: shane <sh...@lo...> - 2003-07-21 11:49:44
|
On Monday 21 July 2003 06:50, Alex McLintock wrote: > At 00:15 21/07/03, David Tseng wrote: > >Just trying to run install-slash, I receive the error: > > > >ERROR 1005 at line 135: Can't create table './testdb/backup_blocks.frm' > >(errno: 150) > > > >I have MySQL 4.0.13-Max installed, do I need anything else? > > Hello David, > > > Please excuse me if this is a bit terse but you haven't really told us > much. > > Are any tables created at all? > Do you have MySQL logs switched on? (might be worth doing so - we need to > find out > why the table isn't created). > > Goodluck > > Alex > > Available for java/perl/C++/web development in London, UK or nearby. > Apache FOP, Cocoon, Turbine, Struts,XSL:FO, XML, Tomcat, JSP > http://www.OWAL.co.uk/ I get the *same* thing w/ mysql4. I cann't install new sites on any mysql4 box. I sent a message to the list titled "problem after converting to mysql4" on the 15th. Have a look at it. Shane PS - previous message text contained below: I'm running into a wall trying to use install-slashsite on a machine which had mysql3 running, and now has mysql4. Here's what happens when I run install-slashsite: Plugins selected: Admin Blob Email Hof Journal MenuEdit Messages Page PollBooth Print PubKey Search Sections Stats Submit Zoo bookiejoint calleria lastcomments DBD::mysql::db do failed: Can't create table './devbj/backup_blocks.frm' (errno: 150) at /usr/local/slash/bin/install-slashsite line 387. The CREATE TABLE command below failed. This almost certainly means the rest of the slashsite installation will fail, so we're aborting. This is probably because your SQL user associated with your DBIx::Password user 'devbj' lacks CREATE and/or DROP permissions. Fix this, or whatever the problem is, and rerun install-slashsite. Failed command: CREATE TABLE backup_blocks ( bid varchar(30) DEFAULT '' NOT NULL, block text, FOREIGN KEY (bid) REFERENCES blocks(bid), PRIMARY KEY (bid)) TYPE=InnoDB Now, the odd thing here is that if I use the mysql cli interface, and login to it as the user which I'm using in DBIx::Password's Password.pm, I can. And I have full permisisons - I can add tables, drop, you name it, etc: create table foo (id int auto_increment,unique key (id)); Query OK, 0 rows affected (0.00 sec) works when I enter mysql with mysql devbj -u devbj -h localhost (I specified the host to demonstrate that's not the problem). Now, I googled on error 150. It seems that Innodb's fairly picky about indexes and what not when a table is type InnoDB: <URL: http://www.mysql.com/doc/en/Cannot_create.html > So, I'm wondering if this isn't a slash bug in the schema with mysql4 when the install runs and imports the theme's schema file. Have any of you who are running mysql 4 done an install-slashsite lately? Some info: mysql Ver 12.20 Distrib 4.0.13, for pc-linux (i686) perl, v5.8.0 Apache/1.3.26 (Unix) |
From: Jamie M. <ja...@mc...> - 2003-07-21 15:41:28
|
I'm quite sure this is a FOREIGN KEY problem. Here's the CVS note for the change I just committed moments ago: Straightened out FOREIGN KEYs. The old schema as written had serious problems creating its foreign keys, which often stymied the very installation of a slashsite. Now all the FOREIGN KEYs are created with ALTER TABLEs *after* all tables are created. And MySQL has some problems in that FOREIGN KEYs have to be precisely the same as the columns they reference, which creates problems when pointing to a foreign primary key that's AUTO_INCREMENT -- so the keys that cause problems are commented out until I can figure out how best to handle this. This is a big complex change and I may have missed something -- in any case it shouldn't affect already established sites, this only affects install. I'm not suggesting that y'all upgrade to the very latest CVS code for a production site... but any feedback on this new change re installation would be appreciated. I'll work on this myself and try to squash any remaining installation quirks. |
From: David T. <da...@mm...> - 2003-07-21 15:21:20
|
Hi Alex, Sorry for not giving more details, I was basically just trying a fresh install with the most recent T tag, T 108 (the error also occurs with the latest CVS) and I received this error and thought others may have run into it also. I believe this is caused by latest change to the sql/mysql/slashschema_create.sql which changed many tables to InnoDB. Here is a more detailed error message upon running install-slashsite: DBD::mysql::db do failed: Can't create table './testdb/backup_blocks.frm' (errno: 150) at bin/install-slashsite line 387. The CREATE TABLE command below failed. This almost certainly means the rest of the slashsite installation will fail, so we're aborting. This is probably because your SQL user associated with your DBIx::Password user 'david' lacks CREATE and/or DROP permissions. Fix this, or whatever the problem is, and rerun install-slashsite. Failed command: CREATE TABLE backup_blocks ( bid varchar(30) DEFAULT '' NOT NULL, block text, FOREIGN KEY (bid) REFERENCES blocks(bid), PRIMARY KEY (bid)) TYPE=InnoDB It does look like several tables are created before the error. I don't receive the error with the latest R tag. Thanks! David On Monday 21 July 2003 03:50 am, Alex McLintock wrote: > At 00:15 21/07/03, David Tseng wrote: > >Just trying to run install-slash, I receive the error: > > > >ERROR 1005 at line 135: Can't create table './testdb/backup_blocks.frm' > >(errno: 150) > > > >I have MySQL 4.0.13-Max installed, do I need anything else? > > Hello David, > > > Please excuse me if this is a bit terse but you haven't really told us > much. > > Are any tables created at all? > Do you have MySQL logs switched on? (might be worth doing so - we need to > find out > why the table isn't created). > > Goodluck > > Alex > > Available for java/perl/C++/web development in London, UK or nearby. > Apache FOP, Cocoon, Turbine, Struts,XSL:FO, XML, Tomcat, JSP > http://www.OWAL.co.uk/ |
From: Jamie M. <ja...@mc...> - 2003-07-21 16:10:11
|
By the way, "perror" is your friend for finding out what those cryptic MySQL error codes mean: > DBD::mysql::db do failed: Can't create table > './testdb/backup_blocks.frm' (errno: 150) at > bin/install-slashsite line 387. $ perror 150 Error code 150: Unknown error 150 150 = Foreign key constraint is incorrectly formed Yes, "perror" is a stupid name for that utility, and the MySQL folks are looking into changing that, or better, putting the error text into the report instead of just the number. da...@mm... (David Tseng) writes: > It does look like several tables are created before the error. > I don't receive the error with the latest R tag. Heh, that's good, but I didn't think it was fixed with the latest R tag. Oh well... it should be fixed *better* in the very latest CVS (untagged yet :) |