Project

General

Profile

Migrating Redmine 1.0.2. to 2.0.1 issues

Added by Andrius Kriučkovas almost 12 years ago

Hello,

I am newbie here and I am migrating Redmine 1.0.2 to 2.0.1.

Source server is Ubuntu JeOS 8.04 LTS
Redmine is 1.0.2 (stable)
MySQL database
Apache as a web server
+ez_summary plugin

Destination server is Ubuntu JeOS 12.04 LTS
with vanilla, stable and working empty:

Environment:
Redmine version 2.0.1.stable
Ruby version 1.8.7 (x86_64-linux)
Rails version 3.2.3
Environment production
Database adapter MySQL
Redmine plugins:
no plugin installed


I am using instructions as per: http://www.redmine.org/projects/redmine/wiki/RedmineUpgrade
I have a backup of old Redmine in 2 files" redmine.sql and redmine.tar.gz (entire folder tree)

---- UPGRADE TRY1 ------

1. I upload redmine.sql "mysql -uroot -p<password> -Dredmine < redmine.sql" there is no error.
2. untar redmine.tar.gz, copy /files directory.

I am uanble to copy 3a. step config/configuration.yml into the new config directory, because there is no "config/configuration.yml" file in the tar backup file. This is confusing - where should I get the file?

I do not know, how to exclude 3b. instructions step for "Make sure that you copy only plugins that are were not initially bundled with your previous Redmine setup.", therefore I copy the only plug-in "redmine_ezsummary Redmine ezSummary plugin Send Summary Emails http://ezwork.techcon.thtf.com.cn Peng Zuo 0.0.1" others are:

acts_as_activity_provider
acts_as_attachable
acts_as_customizable
acts_as_event
acts_as_list
acts_as_searchable
acts_as_tree
acts_as_versioned
acts_as_watchable
awesome_nested_set
classic_pagination
coderay-0.9.2
engines
gravatar
open_id_authentication
prepend_engine_views
rfpdf
ruby-net-ldap-0.0.4

as per 6th step I run "rake generate_session_store", but get "Note: The rake task generate_session_store has been deprecated, please use the replacement version generate_secret_token".

Runing "rake generate_secret_token" it finishes OK.

After this I go to Step 4 Update the database and "rake db:migrate RAILS_ENV=production". Here it goes:

(in /var/www/redmine)
rake aborted!
no such file to load -- dispatcher

Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)

I attach file trace1.txt.

what happened? how to fix it?

---- UPGRADE TRY2 ------

I continue, where the TRY1 scenario left.

I delete the only plugin in the /var/www/redmine/plugins/redmine_ezsummary, as a possible idea for narrowing the issue, and rerun "rake db:migrate RAILS_ENV=production", i get error

"Mysql::Error: Table 'changeset_parents' already exists: CREATE TABLE `changeset_parents` (`changeset_id` int(11) NOT NULL, `parent_id` int(11) NOT NULL) ENGINE=InnoDB
"

trace2.txt is attached for debug. Notice, that this time there is no issue as per "TRY1"

---- UPGRADE TRY3 ------

I continue, where the TRY2 scenario left.

With HeidiSQL I drop Table 'changeset_parents' from redmine DB. I do this, because the table is empty and rerun "rake db:migrate RAILS_ENV=production"

This time I get:

ChangeRepositoriesToFullSti: migrating ==================================
ChangeRepositoriesToFullSti: migrated (0.0006s) =========================

What I understand to be OK.

This time I get fully-functioning Redmine 2.0.1 with all records, projects, etc.

The one-million dollar question is - did I upgrade successfully? Or are there any hidden issues, because of work-arounds I made (deleted plugins, dropped "changeset_parents" table? I assume, that I did not migrate plugins - can there be any issues?

---- UPGRADE TRY4 ------

I try to upgrade plugins (in my case - empty?)

root@redmine2:/var/www/redmine# rake db:plugins:migrate RAILS_ENV=production
rake aborted!
Don't know how to build task 'db:plugins:migrate'

there is trace3.txt

(See full trace by running task with --trace)

if I put back plugin /redmine_ezsummary, and run "rake db:plugins:migrate RAILS_ENV=production", I get again:

(in /var/www/redmine)
rake aborted!
no such file to load -- dispatcher

Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)