# Problems install RForum 0.2 **URL:** \ **Category:** Ruby-Forum\ **Created:** [January 4, 2006, 2:16am UTC](https://www.ruby-forum.com/t/problems-install-rforum-0-2/89192 "2006-01-04T02:16:31Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![zerohalo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/5fc32e/32.png) [@zerohalo](https://www.ruby-forum.com/u/zerohalo)\ **Post date:** [January 4, 2006, 2:16am UTC](https://www.ruby-forum.com/t/problems-install-rforum-0-2/89192/1 "2006-01-04T02:16:31Z")
When trying to do a clean install of RForum 0.2, rake migrate gives me the following error: rake aborted! Mysql::Error: You have an error in your SQL syntax near ‘ENGINE=InnoDB’ at line 1: CREATE TABLE attachments (`id` int(11) DEFAULT NULL auto\_increment PRIMARY KEY, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `filename` varchar(60) NOT NULL, `post_id` int(11), `position` int(11)) ENGINE=InnoDB - Something I should do, or is this a bug? database.yml is correctly filled out and I have created an ‘rforum’ database in mysql (which database.yml points to). Running Rails 1.0 on FreeBSD 5.3 with mysql 3.23. ---
**Author:** ![zerohalo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/5fc32e/32.png) [@zerohalo](https://www.ruby-forum.com/u/zerohalo)\ **Post date:** [January 4, 2006, 5:22am UTC](https://www.ruby-forum.com/t/problems-install-rforum-0-2/89192/2 "2006-01-04T05:22:26Z")
zero halo wrote: > When trying to do a clean install of RForum 0.2, rake migrate gives me > the following error: > > rake aborted! > Mysql::Error: You have an error in your SQL syntax near ‘ENGINE=InnoDB’ > at line 1: CREATE TABLE attachments (`id` int(11) DEFAULT NULL > auto\_increment PRIMARY KEY, `created_at` datetime NOT NULL, `updated_at` > datetime NOT NULL, `filename` varchar(60) NOT NULL, `post_id` int(11), > `position` int(11)) ENGINE=InnoDB I should have included the trace: /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active\_record/connection\_adapters/abstract\_adapter.rb:88:in `log' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active_record/connection_adapters/mysql_adapter.rb:180:in`execute’ /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active\_record/connection\_adapters/abstract/schema\_statements.rb:94:in `create_table' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active_record/connection_adapters/mysql_adapter.rb:283:in`create\_table’ /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active\_record/migration.rb:170:in `send' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active_record/migration.rb:170:in`method\_missing’ ./db/migrate//001\_initial.rb:6:in `up' ./db/migrate//001_initial.rb:4:in`instance\_eval’ /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active\_record/schema.rb:43:in `instance_eval' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active_record/schema.rb:43:in`define’ ./db/migrate//001\_initial.rb:4:in `up' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active_record/migration.rb:228:in`send’ /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active\_record/migration.rb:228:in `migrate' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active_record/migration.rb:223:in`each’ /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active\_record/migration.rb:223:in `migrate' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active_record/migration.rb:190:in`up’ /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active\_record/migration.rb:181:in `migrate' /usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/tasks/databases.rake:3 /usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/tasks/databases.rake:2:in`call’ /usr/local/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:202:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:202:in`each’ /usr/local/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:202:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:180:in`invoke’ /usr/local/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:1454:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:1454:in`each’ /usr/local/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:1454:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.6.2/bin/rake:7 /usr/local/bin/rake:18:in`load’ /usr/local/bin/rake:18 ---
**Author:** ![zerohalo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/5fc32e/32.png) [@zerohalo](https://www.ruby-forum.com/u/zerohalo)\ **Post date:** [January 4, 2006, 5:26am UTC](https://www.ruby-forum.com/t/problems-install-rforum-0-2/89192/3 "2006-01-04T05:26:45Z")
To answer my own question, it seems that Rails migrations choke in mysql 3.23. Details here: [http://rails.techno-weenie.net/question/2005/12/25/migrations\_with\_mysql\_3\_23](http://rails.techno-weenie.net/question/2005/12/25/migrations_with_mysql_3_23). ---
**Author:** ![zerohalo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/5fc32e/32.png) [@zerohalo](https://www.ruby-forum.com/u/zerohalo)\ **Post date:** [January 4, 2006, 11:34am UTC](https://www.ruby-forum.com/t/problems-install-rforum-0-2/89192/4 "2006-01-04T11:34:06Z")
zero halo wrote: > When I run ./script/server, I just get the following: > =\> Booting WEBrick… > > # > > However, WEBrick doesn’t actually boot. The odd thing is that I already > have 3 instances of WEBrick running (two instances of Instiki, plus my > own Rails app), so I know that WEBrick works on my system. I tried > killing one of 3 running WEBrick processes to see if it would boot then > (in case you can only run so many instances of WEBrick), but the same > results. Has anyone else encountered this? Not that I know of. MySQL 3.23 is really old, there might be problems related to that. Could you try it with SQLite, to rule out any problems with MySQL? ---
**Author:** ![zerohalo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/5fc32e/32.png) [@zerohalo](https://www.ruby-forum.com/u/zerohalo)\ **Post date:** [January 4, 2006, 5:41am UTC](https://www.ruby-forum.com/t/problems-install-rforum-0-2/89192/5 "2006-01-04T05:41:50Z")
Ok, now that I’ve gotten migrate to work (by editing the migrate files, adding :options =\> ‘TYPE=InnoDB’ to each create table line), I’m running into my next problem. When I run ./script/server, I just get the following: =\> Booting WEBrick… # However, WEBrick doesn’t actually boot. The odd thing is that I already have 3 instances of WEBrick running (two instances of Instiki, plus my own Rails app), so I know that WEBrick works on my system. I tried killing one of 3 running WEBrick processes to see if it would boot then (in case you can only run so many instances of WEBrick), but the same results. Has anyone else encountered this?