migrate_from_trac aborting.
Added by Michael Bogucki over 11 years ago
Hello Everyone,
I'm attempting to migrate from trac (version 0.11.7) and onto redmine (version 2.3.0) using the migrate_from_trac script.
When I invoke said script, I see the following output:
root@ip-*******:/usr/local/share/redmine# rake --trace redmine:migrate_from_trac RAILS_ENV="production"- Invoke redmine:migrate_from_trac (first_time)
- Invoke environment (first_time)
- Execute environment
- Execute redmine:migrate_from_trac
WARNING: a new project will be added to Redmine during this process.
Are you sure you want to continue ? [y/N] y
Trac directory []: /tmp/trac/ZoroTools
Trac database adapter (sqlite3, mysql2, postgresql) [sqlite3]: mysql
Trac database host [localhost]:
Trac database port [3306]:
Trac database name []: trac
Trac database schema [public]:
Trac database username []: trac
Trac database password []: blah
Trac database encoding [UTF-8]:
Target project identifier []: tracmigration
Migrating components........
Migrating milestones..........................
Migrating custom fields
Migrating tickets..............................................................................................................................................................................................rake aborted!
"\205\r\n\r\nCan you ple"...
/usr/local/share/redmine-2.3.0/lib/tasks/migrate_from_trac.rake:716:in `iconv'
/usr/local/share/redmine-2.3.0/lib/tasks/migrate_from_trac.rake:716:in `encode'
/usr/local/share/redmine-2.3.0/lib/tasks/migrate_from_trac.rake:470:in `migrate'
/var/lib/gems/1.8/gems/activerecord-3.2.13/lib/active_record/relation/batches.rb:21:in `find_each'
/var/lib/gems/1.8/gems/activerecord-3.2.13/lib/active_record/relation/batches.rb:21:in `each'
/var/lib/gems/1.8/gems/activerecord-3.2.13/lib/active_record/relation/batches.rb:21:in `find_each'
/var/lib/gems/1.8/gems/activerecord-3.2.13/lib/active_record/relation/batches.rb:72:in `find_in_batches'
/var/lib/gems/1.8/gems/activerecord-3.2.13/lib/active_record/relation/batches.rb:20:in `find_each'
/var/lib/gems/1.8/gems/activerecord-3.2.13/lib/active_record/querying.rb:8:in `__send__'
/var/lib/gems/1.8/gems/activerecord-3.2.13/lib/active_record/querying.rb:8:in `find_each'
/usr/local/share/redmine-2.3.0/lib/tasks/migrate_from_trac.rake:465:in `migrate'
/usr/local/share/redmine-2.3.0/lib/tasks/migrate_from_trac.rake:768
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:246:in `call'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:246:in `execute'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:241:in `each'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:241:in `execute'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:184:in `invoke_with_call_chain'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:177:in `invoke_with_call_chain'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:170:in `invoke'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:143:in `invoke_task'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:101:in `top_level'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:101:in `each'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:101:in `top_level'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:110:in `run_with_threads'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:95:in `top_level'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:73:in `run'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:160:in `standard_exception_handling'
/var/lib/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:70:in `run'
/var/lib/gems/1.8/gems/rake-10.0.4/bin/rake:33
/usr/local/bin/rake:19:in `load'
/usr/local/bin/rake:19
Tasks: TOP => redmine:migrate_from_trac
I've been querying the trac database and removing the "offending" tickets. (Since this is a test environment, I have that luxury for now)
However I'm curious if there's any way to get more details as to which ticket is causing the problem or even which character is causing rake/ruby to throw a fit.
Please bare with me, I'm and N00b at this and more familar with python (over ruby).
Any suggestions would be greatly appreciated.
Thank you and take care.
--Mike
Replies (3)
RE: migrate_from_trac aborting.
-
Added by Paresh Patel over 11 years ago
hi,
http://www.redmine.org/projects/redmine/wiki/RedmineMigrate
http://www.howtoforge.com/how-to-migrate-from-trac-to-redmine
above this 2 links follow your problem is solving 100%
any other problem then reply me
Form: Paresh.Patel
RE: migrate_from_trac aborting.
-
Added by Michael Bogucki over 11 years ago
Hello Paresh,
Thank you for the following information, however these are the links that I'm using in order to do the migration.
I've got Redmine installed and running however I am unable to get the importer to work.
--Mike
RE: migrate_from_trac aborting.
-
Added by Michael Bogucki over 11 years ago
I forgot to mention that this migration does appear to work up to a point. (Meaning it does import a bunch of tickets, but for whatever reason, some character seems to cause the migrate process to crash.)