Project

General

Profile

Actions

Defect #11563

closed

Can't Install any plugin for Redmine

Added by john zhel almost 12 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
No feedback
Affected version:

Description

My machine info: Build Operating System: Linux 2.6.18-194.11.1.el5 x86_64 Red Hat, Inc.

Downloaded BitNami redmine 1.4 stack from here http://bitnami.org/stack/redmine/

After installation, I can successfully see Redmine and login as a user.

Next, I just need some plugins.

I followed the instruction here: http://answers.bitnami.org/questions/1785/install-the-bitnami-redmine-plugins

Copy the plugin files to the "plugins" directory and run the following in Terminal

$ cd installdir
$ ./use_redmine
$ cd apps/redmine/htdocs
$ rake db:migrate_plugins RAILS_ENV=production

After rake, I see the following error in Terminal:

(in /home/abcdefg/public_html/pm/apps/redmine/htdocs) rake aborted! uninitialized constant YAML::ENGINE /home/abcdefg/public_html/pm/apps/redmine/htdocs/Rakefile:4:in `require' (See full trace by running task with --trace)

Why is that? How to fix it?

I also tried a plugin that does not need migration. Just copy the files over to plugins directory, and type ./ctlscript.sh restart Redmine in terminal and it seems running ok and I checked status, it shows:

subversion already running
apache already running
mysql already running

But, when I go the the browser and browse to http://localhost:8082/redmine/ , it returns 500 internal server error message; the error goes away if I deleted the plugins files I copied in.

In summary, I have 2 problems, both related to installing redmine plugins.

  1. can not run rake db:migrate_plugins RAILS_ENV=production
  2. for plugins that do not need migration, new plugins cause 500 internal server error

What should I do to debug these problems? Thank you so much for your help :)

Actions #1

Updated by Etienne Massip over 11 years ago

  1. Run rake with --trace as suggested
  2. Look into your production.log file to get error stack trace
Actions #2

Updated by john zhel over 11 years ago

Etienne Massip wrote:

  1. Run rake with --trace as suggested
  2. Look into your production.log file to get error stack trace

Hello Etienne,

Thank you for replying to my questions.

How do I "Run rake with --trace "? (I'm 100% NB here, LOL) Please advise :)

Actions #3

Updated by Etienne Massip over 11 years ago

rake db:migrate_plugins RAILS_ENV=production --trace =)

Actions #4

Updated by Jan Niggemann (redmine.org team member) over 11 years ago

  • Status changed from New to Needs feedback
Actions #5

Updated by Jan Niggemann (redmine.org team member) over 10 years ago

  • Status changed from Needs feedback to Closed
  • Resolution set to No feedback
Actions

Also available in: Atom PDF