Project

General

Profile

Can't remove failed plugin and now Redmine won't start. Help [Resolved]

Added by Yohan Bienvenue over 7 years ago

I've been on this for 4 hours now, I really need some help. Redmine has been down this whole time for everybody in the office..

Windows Server 2003
Redmine 2.5.2
Ruby 1.9.3
MySQL 5.1.48

I just wanted to install the redmine_checklists plugin, but it failed to install because it needed version 2.13.3 of rmagick. Redmine wouldn't start after that.
So at first I just tried to uninstall the plugin, but it fails because it needs rmagick, so it won't remove it, what the heck...

Failing to remove the plugin, I tried for 2 hours to install this rmagick 2.13.3 gem, but I got error after error, nothing worked. bundle install is unable to install it because it says it's missing headers. I tried installing imagemagick and pointing to the headers there, but it still fails. I managed to install version 2.16.0, but not 2.13.3. I tried so many solutions..

So now I'm back at trying to just uninstall the plugin, I must restore the service. I just want to remove it and go back to where I was. Please help.
This is the command I'm trying:

E:\redmine-2.5.2>rake redmine:plugins:migrate NAME=redmine_checklists VERSION=0 RAILS_ENV=production
←[31mCould not find rmagick-2.13.3 in any of the sources←[0m
←[33mRun `bundle install` to install missing gems.←[0m

E:\redmine-2.5.2>

Another thought, is it possible to directly manipulate the database to remove it??

Thanks


Replies (1)

RE: Can't remove failed plugin and now Redmine won't start. Help - Added by Yohan Bienvenue over 7 years ago

I finally managed to make Redmine start again...

So in the end what I think happens is that even if the plugin fails to install, from that point redmine adds the plugins dependencies to it's list and then requires the plugins dependencies. In my case the rmagick 2.13.3 gem failed to install, but redmine now needed it to run anyway.

Manually removing the plugins table in the database does not help.

What worked is calling redmine's bundle install, but with the option --without rmagick:

E:\redmine-2.5.2>bundle install --without rmagick

Somehow this fixes redmine's dependencies list back to normal.

    (1-1/1)