Help - upgrading Redmine 0.8 to trunk version.

Added by Nanda P almost 11 years ago

I am trying upgrade Redmine 0.8 to trunk

Here are the steps

  • I pull the trunk from svn.
  • updated Rails to 2.2.2 ("gem install rails -v=2.2.2")
  • Replaced database.yml with my old one.
  • Replaced environment.rb and updated the following line
    > # Specifies gem version of Rails to use when vendor/rails is not present
    > RAILS_GEM_VERSION = '2.2.2' unless defined? RAILS_GEM_VERSION
     
  • Ran the following commands.
     rake config/initializers/session_store.rb 
     
  • When update the mysql gem (C:\Program Files\RedMine\current>gem install mysql) I got the following message
    Successfully installed mysql-2.7.3-x86-mswin32
    1 gem installed
    Installing ri documentation for mysql-2.7.3-x86-mswin32...
    Installing RDoc documentation for mysql-2.7.3-x86-mswin32...
    ERROR:  While generating documentation for mysql-2.7.3-x86-mswin32
    ... MESSAGE:   Unhandled special: Special: type=17, text="<!-- $Id: README.html,
    v 1.20 2006-12-20 05:31:52 tommy Exp $ -->" 
    ... RDOC args: --op c:/ruby/lib/ruby/gems/1.8/doc/mysql-2.7.3-x86-mswin32/rdoc -
    -exclude ext --main README --quiet ext README docs/README.html
    (continuing with the rest of the installation)
    

so I ran "gem install --no-rdoc mysql" as per someone idea on the web.

  • When I tried to start WebRick, getting the following error.
C:\Program Files\RedMine\current>ruby script/server --port=80 --environment=production

c:/ruby/lib/ruby/gems/1.8/gems/activerecord-2.2.2/lib/active_record/connection_a
dapters/mysql_adapter.rb:548: [BUG] Segmentation fault
ruby 1.8.6 (2007-09-24) [i386-mswin32]

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

About My application's environment

Ruby version              1.8.6 (i386-mswin32)
RubyGems version          1.3.1
Rails version             2.2.2
Active Record version     2.2.2
Action Pack version       2.2.2
Active Resource version   2.2.2
Action Mailer version     2.2.2
Active Support version    2.2.2
Application root          C:/Program Files/RedMine/current
Environment               development
Database adapter          mysql
Database schema version   103

Anyone could tell me how to solve this issue?

Thanks in Advance.!

Nanda

Replies (7)

RE: Help - upgrading Redmine 0.8 to trunk version. - Added by Mischa The Evil almost 11 years ago

It seems you forgot to migrate your database with rake db:migrate RAILS_ENV="production" like explaned in step 2 of the guide at RedmineUpgrade.
In your instance the DB-schema version is 103 which is 0.8. Current trunk is at 20090214190337...

HTH...

RE: Help - upgrading Redmine 0.8 to trunk version. - Added by Nanda P almost 11 years ago

Output of db:migrate

C:\Program Files\RedMine\current>rake db:migrate RAILS_ENV="production"

(in C:/Program Files/RedMine/current)
==  AddProjectsLftAndRgt: migrating ===========================================
-- add_column(:projects, :lft, :integer)
rake aborted!
An error has occurred, all later migrations canceled:

Mysql::Error: Duplicate column name 'lft': ALTER TABLE `projects` ADD `lft` int(
11)

(See full trace by running task with --trace)
c:/ruby/bin/rake:16: [BUG] Segmentation fault
ruby 1.8.6 (2007-09-24) [i386-mswin32]

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

RE: Help - upgrading Redmine 0.8 to trunk version. - Added by Nanda P almost 11 years ago

Mischa, Thanks for your Speedy response. Really appreciate it.!

RE: Help - upgrading Redmine 0.8 to trunk version. - Added by Nanda P almost 11 years ago

I created a new DB & tried to migrate, I got the same "[BUG] Segmentation fault" error.

C:\Program Files\RedMine\current>rake db:migrate RAILS_ENV="production"

(in C:/Program Files/RedMine/current)
rake aborted!
undefined method `each' for #<Mysql:0x48f62dc>

(See full trace by running task with --trace)
c:/ruby/bin/rake:16: [BUG] Segmentation fault
ruby 1.8.6 (2007-09-24) [i386-mswin32]

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

RE: Help - upgrading Redmine 0.8 to trunk version. - Added by Nanda P almost 11 years ago

I Reinstalled Ruby & MySQL 5.1 now I am getting a message. " The filename, directory name, or volume label syntax is incorrect. "

C:\Program Files\redmine\current>ruby script\about
About your application's environment
Ruby version              1.8.6 (i386-mswin32)
RubyGems version          1.3.1
Rails version             2.2.2
Active Record version     2.2.2
Action Pack version       2.2.2
Active Resource version   2.2.2
Action Mailer version     2.2.2
Active Support version    2.2.2
Application root          C:/Program Files/redmine/current
Environment               development
Database adapter          mysql
Database schema version   0

C:\Program Files\redmine\current>rake db:migrate RAILS_ENV="development" --trace
The filename, directory name, or volume label syntax is incorrect.

C:\Program Files\redmine\current>

Any suggestions?

RE: Help - upgrading Redmine 0.8 to trunk version. - Added by Nanda P almost 11 years ago

I found the solution for the above issue,

under "C:\program files\Ruby\bin\" take out the extra double quote (") from the following batch files

  • rake.bat
@ECHO OFF
IF NOT "%~f0" == "~f0" GOTO :WinNT
@"ruby.exe" "C:/Program Files/Ruby/bin/rake" %1 %2 %3 %4 %5 %6 %7 %8 %9
GOTO :EOF
:WinNT
@"ruby.exe" "%~dpn0" %*
  • rails.bat
@ECHO OFF
IF NOT "%~f0" == "~f0" GOTO :WinNT
@"ruby.exe"" "C:/Program Files/Ruby/bin/rails" %1 %2 %3 %4 %5 %6 %7 %8 %9
GOTO :EOF
:WinNT
@"ruby.exe" "%~dpn0" %*

RE: Help - upgrading Redmine 0.8 to trunk version. - Added by Nanda P almost 11 years ago

Nanda Palaniswamy wrote:

I created a new DB & tried to migrate, I got the same "[BUG] Segmentation fault" error.

C:Program FilesRedMinecurrent>rake db:migrate RAILS_ENV="production"
[...]

The above issue was solved by replacing MySQL 5.1 to MySQL 5.0

(1-7/7)