From: George C. <ga...@sp...> - 2004-09-09 02:36:11
|
Hi, I just did a clean install onto a new system from CVS tag T_2_5_0_24. No local customization done at all. Install appeared to go okay, but I'm seeing a few issues with the system. Is 2_5_0_24 a reasonable tag to try, or should I go with an older 2_5 tag? First error: [Thu Sep 9 02:00:48 2004] [error] /admin.pl:Slash::DB::MySQL:/usr/lib/perl5/site_perl/5.8.4/i686-linux-thread-multi/Slash/DB/MySQL.pm:1354:DB='wapav' -- hostinfo='Loc alhost via UNIX socket' -- Unknown column 'content_type' in 'where clause' -- SELECT extras_textname, extras_keyword, type FROM topic_nexus_extras WHERE tid = '1' AND content_type = 'story' I got past this by running the following from the mysql/updates file: ALTER TABLE topic_nexus_extras add column content_type enum("story","comment") DEFAULT 'story' NOT NULL; So it appears as though some of the upgrades have not made it into the initial database setup. 2) When I tried to submit a story, I get a foreign key error. Here is the report from innodb. ------------------------ LATEST FOREIGN KEY ERROR ------------------------ 040909 2:14:35 Transaction: TRANSACTION 0 6125, ACTIVE 0 sec, process no 19024, OS thread id 6619148 inserting, thread declared inside InnoDB 499 mysql tables in use 1, locked 1 2 lock struct(s), heap size 320, undo log entries 1 MySQL thread id 395, query id 10354 localhost slashuser update INSERT INTO submissions (uid,story,ipid,tid,subj,email,signature,time,primaryskid,subnetid) VALUES( '2', 'Here is the scoop, for what tis worth.', '059a8c05fd9067b0ffd148426cc37059', '5', 'This is a test subject submission', 'mailto:te...@sp...', 'cef509a0b8f8166fae752a7ac2c2f Foreign key constraint fails for table `slashdb/submissions`: , CONSTRAINT `submissions_ibfk_1` FOREIGN KEY (`uid`) REFERENCES `users` (`uid`) Trying to add to index `uid` tuple: DATA TUPLE: 2 fields; 0: len 3; hex 000002; asc ;; 1: len 3; hex 000001; asc ;; But the parent table `slashdb/users` does not currently exist! And when I visit "New Story" page to create a story, the following errors are logged: [Thu Sep 9 02:22:43 2004] [error] /admin.pl:Slash::DB::MySQL:/usr/lib/perl5/site_perl/5.8.4/i686-linux-thread-multi/Slash/DB/MySQL.pm:8765:DB='wapav' -- hostinfo='Localhost via UNIX socket' -- 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 '' at line 1 -- SELECT *, 0 AS is_future FROM stories WHERE stoid= [Thu Sep 9 02:22:43 2004] [error] Which was called by:Apache::ROOTwww_2eworcesterapa_2eorg::admin_2epl:/usr/local/slash/site/www.worcesterapa.org/htdocs/admin.pl:1172:DB='wapav' -- hostinfo='Localhost via UNIX socket' -- 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 '' at line 1 -- SELECT *, 0 AS is_future FROM stories WHERE stoid= \n [Thu Sep 9 02:22:43 2004] [error] /admin.pl:Slash::DB::MySQL:/usr/lib/perl5/site_perl/5.8.4/i686-linux-thread-multi/Slash/DB/MySQL.pm:9836:cannot getSkin for empty skid [Thu Sep 9 02:22:43 2004] [error] Which was called by:Apache::ROOTwww_2eworcesterapa_2eorg::admin_2epl:/usr/local/slash/site/www.worcesterapa.org/htdocs/admin.pl:1549:cannot getSkin for empty skid\n [Thu Sep 9 02:22:43 2004] [error] [client 192.168.1.19] File does not exist: /usr/local/slash/site/www.worcesterapa.org/htdocs/admin-topic-popup.css [Thu Sep 9 02:22:43 2004] [error] [client 192.168.1.19] File does not exist: /usr/local/slash/site/www.worcesterapa.org/htdocs/admin-topic-popup.js |
From: Shane <sh...@lo...> - 2004-09-09 11:35:12
|
On Sep 8, 2004, at 10:27 PM, George Clark wrote: > [...snip...] > > But the parent table `slashdb/users` does not currently exist! I would think that's fairly unlikely. If this site you're working with's db is 'slashdb' I would think much wouldn't work at all if the table 'users' didn't exist. > > And when I visit "New Story" page to create a story, the following > errors are > logged: > -- hostinfo='Localhost via UNIX socket' -- 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 '' at line 1 -- SELECT *, 0 AS is_future FROM > stories > WHERE stoid= \n > [Thu Sep 9 02:22:43 2004] [error] Look through the sf bug reports, I thought this was reported, and fixed. > /admin.pl:Slash::DB::MySQL:/usr/lib/perl5/site_perl/5.8.4/i686-linux- > thread-multi/Slash/DB/MySQL.pm:9836:cannot > getSkin for empty skid > [Thu Sep 9 02:22:43 2004] [error] Which was called > by:Apache::ROOTwww_2eworcesterapa_2eorg::admin_2epl:/usr/local/slash/ > site/www.worcesterapa.org/htdocs/admin.pl:1549:cannot > getSkin for empty skid\n From one of the OSDN guru's on irc about the skin errors: [09:16] yeah, sorry, we're still working those out [09:17] they don't hurt anything, they're just a reminder to us > [Thu Sep 9 02:22:43 2004] [error] [client 192.168.1.19] File does not > exist: > /usr/local/slash/site/www.worcesterapa.org/htdocs/admin-topic-popup.css > [Thu Sep 9 02:22:43 2004] [error] [client 192.168.1.19] File does not > exist: > /usr/local/slash/site/www.worcesterapa.org/htdocs/admin-topic-popup.js run your symlink-tool :) Shane |
From: Jamie M. <ja...@mc...> - 2004-09-09 13:32:43
|
> [Thu Sep 9 02:00:48 2004] [error] > /admin.pl:Slash::DB::MySQL:/usr/lib/perl5/site_perl/5.8.4/i686- > /linux-thread-multi/Slash/DB/MySQL.pm:1354:DB=3D'wapav' > -- hostinfo=3D'Loc alhost via UNIX socket' -- Unknown column > 'content_type' in 'where clause' -- SELECT extras_textname, > extras_keyword, type FROM topic_nexus_extras WHERE tid =3D '1' > AND content_type =3D 'story' >=20 > I got past this by running the following from the mysql/updates > file: >=20 > ALTER TABLE topic_nexus_extras add column content_type > enum("story","comment") DEFAULT 'story' NOT NULL; >=20 > So it appears as though some of the upgrades have not made it > into the initial database setup. Yep! We goofed. I'll fix this in CVS shortly, sorry. > > But the parent table `slashdb/users` does not currently exist! >=20 > I would think that's fairly unlikely. If this site you're > working with's db is 'slashdb' I would think much wouldn't work > at all if the table 'users' didn't exist. Right. Without a 'users' table it's hopeless. During the install I'm assuming it bombed out, saying this: The CREATE TABLE command below failed. This almost certainly means the rest of the slashsite installation will fail, so we're aborting. If so, then things are badly screwed up. Do a SHOW TABLES command in your mysql client and my guess is that the alphabetical list will cut off somewhere before 'u'. Let us know where (and, when you retry the installation, let us know what error caused the abort). Without a complete install, you have no chance of getting anything to work. Follow the "UNINSTALLING" instructions at the end of the INSTALL file, then start over on "INSTALLATION" step 6, "Install your Slash site." > > [Thu Sep 9 02:22:43 2004] [error] [client 192.168.1.19] File does not = =20 > > exist: > > /usr/local/slash/site/www.worcesterapa.org/htdocs/admin-topic-popup.css > > [Thu Sep 9 02:22:43 2004] [error] [client 192.168.1.19] File does not = =20 > > exist: > > /usr/local/slash/site/www.worcesterapa.org/htdocs/admin-topic-popup.js >=20 > run your symlink-tool :) No, those are generated by the topic_popup_static.pl task, so you'll want to run slashd. Which will utterly fail since you are missing half your tables :) --=20 Jamie McCarthy http://mccarthy.vg/ ja...@mc... |
From: George C. <ga...@sp...> - 2004-09-10 01:55:54
|
** Reply to message from Jamie McCarthy <ja...@mc...> on Thu, 9 Sep 2004 09:32:30 -0400 Hi Jamie, > > > But the parent table `slashdb/users` does not currently exist! > During the install I'm assuming it bombed out, saying this: > > The CREATE TABLE command below failed. This almost certainly means > the rest of the slashsite installation will fail, so we're aborting. Install was flawless. No issues. Daemons all work. Login, etc. works. The Mysql message about the user table missing has to be bogus. Select * from users shows that it contains UID 1 & 2. So the UID can't be the foreign key error. Looks like my mysql installation is somehow broken. Strange that the rest of slash is working fine. I couldn't drop the foreign key. phpBB is working okay too. ??? mysql> ALTER TABLE submissions drop foreign key uid; ERROR 1025: Error on rename of './slashdb/submissions' to './slashdb/#sql2-2172-e' (errno: 152) Finally I dropped the submissions table and recreated it, and submit started working. So I then tried to add the foreign key back in. mysql> ALTER TABLE submissions ADD FOREIGN KEY (uid) REFERENCES users(uid); ERROR 1005: Can't create table './slashdb/#sql-2172_e.frm' (errno: 150) I found the following: > This means either: > > * No index has been defined on the column other_id > * The referenced table is not an InnoDB table > * The referenced column is not unique Okay... it looks as though for some reason the users table is no longer type InnoDB. I tried to convert it, and get the following error: mysql> ALTER TABLE users TYPE=InnoDB; ERROR 1214: The used table type doesn't support FULLTEXT indexes And I just checked the slashschema_create, and it creates it as MyIsam. Finally, found the following comments in the schema: # Stories is now InnoDB and these other tables are still MyISAM, # so no foreign keys between them. #ALTER TABLE stories ADD FOREIGN KEY (uid) REFERENCES users(uid); ....>>but a few lines later>... ALTER TABLE submissions ADD FOREIGN KEY (uid) REFERENCES users(uid); Sure looks like the submissions table should not have a foreign key created on the users table. Sure looks like a bug in the schema to me ;-) And that original error... user table missing... From an InnoDB perspective it is missing, it is a MyIsam table. Thanks, George |
From: Jamie M. <ja...@mc...> - 2004-09-10 16:55:20
|
> Install was flawless. No issues. Daemons all work. Login, > etc. works. The Mysql message about the user table missing has > to be bogus. Huh. OK. I wondered why its syntax didn't look familiar, wonder what's going on there. Re foreign keys -- MySQL does not support foreign keys that go across table types, or at least not from MyISAM tables into InnoDB tables or vice versa. That's part of why after the section-topics rewrite we had to nuke a lot of the foreign keys we used to have -- several of the tables got converted from MyISAM to InnoDB. The remaining MyISAM tables are only MyISAM because they need FULLTEXT indexes (well, and users_count). > Finally, found the following comments in the schema: >=20 > # Stories is now InnoDB and these other tables are still MyISAM, > # so no foreign keys between them. Yeah :) > Okay... it looks as though for some reason the users table is > no longer type InnoDB. I tried to convert it, and get the > following error: >=20 > mysql> ALTER TABLE users TYPE=3DInnoDB; > ERROR 1214: The used table type doesn't support FULLTEXT > indexes >=20 > And I just checked the slashschema_create, and it creates it as > MyIsam. Ah, yes. And plugins/Search adds its FULLTEXT index. Just FYI, what we do on our big sites is keep users InnoDB on the main DB, with no FULLTEXT index, and have a separate, slaved search DB where we keep it MyISAM with a FULLTEXT index. That doesn't really help you here, but might be useful to know. > Finally, found the following comments in the schema: >=20 > # Stories is now InnoDB and these other tables are still MyISAM, > # so no foreign keys between them. > #ALTER TABLE stories ADD FOREIGN KEY (uid) REFERENCES users(uid); > .....>>but a few lines later>... > ALTER TABLE submissions ADD FOREIGN KEY (uid) REFERENCES > users(uid); >=20 > Sure looks like the submissions table should not have a foreign > key created on the users table. Sure looks like a bug in the > schema to me ;-) Yep! You're right. Commented-out and I'll commit that fix into CVS shortly. Thanks! --=20 Jamie McCarthy http://mccarthy.vg/ ja...@mc... |