redmine upgrade from 2.2.3.stable to 2.5.1 does not work

Added by pee pee over 8 years ago

Hi,

I have a turnkeylinux (v13.0) redmine appliance (redmine v2.2.3).
I tried to upgrade v2.2.3 to v2.5.1 and followed the upgrade instructions.

I did not get any errors, but my version is still at v2.2.3!
what am I doing wrong?

RAILS_ENV=production script/about:

root@tkredmine www/redmine# RAILS_ENV=production  script/about
[deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message.
/var/lib/gems/1.9.1/gems/activesupport-3.2.12/lib/active_support/dependencies.rb:251:in `block in require': iconv will be deprecated in the future, use String#encode instead.

Environment:
  Redmine version                          2.2.3.stable
  Ruby version                             1.9.3 (x86_64-linux)
  Rails version                            3.2.12
  Environment                              production
  Database adapter                         Mysql2
Redmine plugins:
  no plugin installed

The steps I did to upgrade redmine (as in the docs)

root@tkredmine /# cd /var/www/redmine
root@tkredmine www/redmine# svn
Type 'svn help' for usage.
root@tkredmine www/redmine# svn update
Skipped '.'
root@tkredmine www/redmine# bundle update
Fetching gem metadata from http://rubygems.org/.........
Fetching gem metadata from http://rubygems.org/..
Resolving dependencies...
Using rake (10.3.1)
Using i18n (0.6.9)
Using multi_json (1.9.3)
Using activesupport (3.2.12)
Using builder (3.0.0)
Using activemodel (3.2.12)
Using erubis (2.7.0)
Using journey (1.0.4)
Using rack (1.4.5)
Using rack-cache (1.2)
Using rack-test (0.6.2)
Using hike (1.2.3)
Using tilt (1.4.1)
Using sprockets (2.2.2)
Using actionpack (3.2.12)
Using mime-types (1.25.1)
Using polyglot (0.3.4)
Using treetop (1.4.15)
Using mail (2.4.4)
Using actionmailer (3.2.12)
Using arel (3.0.3)
Using tzinfo (0.3.39)
Using activerecord (3.2.12)
Using activeresource (3.2.12)
Using bundler (1.3.5)
Using coderay (1.0.9)
Using rack-ssl (1.3.4)
Using json (1.8.1)
Using rdoc (3.12.2)
Using thor (0.19.1)
Using railties (3.2.12)
Using jquery-rails (2.0.3)
Using metaclass (0.0.4)
Using mocha (0.12.3)
Using mysql2 (0.3.15)
Using net-ldap (0.3.1)
Using pg (0.17.1)
Using ruby-openid (2.1.8)
Using rack-openid (1.4.2)
Using rails (3.2.12)
Using shoulda (2.11.3)
Using sqlite3 (1.3.9)
Using test-unit (2.5.5)
Using yard (0.8.7.4)
Your bundle is updated!
Gems in the groups rmagick and install were not installed.
root@tkredmine www/redmine# rake db:migrate RAILS_ENV=production
[deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message.
root@tkredmine www/redmine# rake redmine:plugins:migrate RAILS_ENV=production
[deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message.
root@tkredmine www/redmine# rake tmp:cache:clear
root@tkredmine www/redmine# rake tmp:sessions:clear

I tried to restart passenger as told in the docs, but I do not know how.
How do you do that?
I did restart apache2, and even rebooted, but that did not work either

Any suggestions please?

Thanks!!

Replies (5)

RE: redmine upgrade from 2.2.3.stable to 2.5.1 does not work - Added by Martin Denizet (redmine.org team member) over 8 years ago

Hello,

Did you check you Apache log?
You could also try to start your instance with Webrick to see.

Cheers,

RE: redmine upgrade from 2.2.3.stable to 2.5.1 does not work - Added by pee pee over 8 years ago

Yes, but it does not give me any clue.
How can I start redmine with webrick instead of apache?
thanks!

RE: redmine upgrade from 2.2.3.stable to 2.5.1 does not work - Added by Martin Denizet (redmine.org team member) over 8 years ago

From CLI:

ruby script/rails server webrick -e production

Will start the server on port 3000 by default.
More in Redmine's doc

RE: redmine upgrade from 2.2.3.stable to 2.5.1 does not work - Added by mike B about 8 years ago

I had alot of issues trying to follow just one walkthrough so I pieced together alot of them and found things that worked. I am in no way an expert on this nor am I even a novice.... I just have vshpere where I snapshot and then trial and error. Finally got it to work and I believe below is the only commands I used.

This is all done with a baseline turnkey redmine with 2.2.3. I had some plugins i wanted to try which required an upgrade... so here it is...

If you made any changes to the locales/en.yml then you will have to do it again. I wouldn't recommend copying that file over as the update might have some other language associations that werent with the older version.

**SNAPSHOT VM FIRST!!!****
edit: I recently had to do this again... and i couldnt remember how i did it and was spending about 2 hours scouring the internet then found this and it worked!! except for a couple of steps but then I realized I MADE THIS! haha. wow..... too dependant on Google. But hey, it works and I made some changes that it needed. I did this with an out of the box turnkey linux machine so I didnt need to migrade the files and plugins as you would find on the generic upgrade instructions.

cd /var/www/
mv redmine redmine-old
wget http://www.redmine.org/releases/redmine-2.5.2.zip
unzip redmine-2.5.2.zip -d /var/www/
mv redmine-2.5.2 redmine
cp redmine-old/config/database.yml redmine/config/database.yml
cp redmine-old/config/configuration.yml redmine/config/configuration.yml
cp -r redmine-old/files redmine/
cp -r redmine-old/plugins redmine/
cd redmine
bundle install --without development test rmagick
bundle exec rake generate_secret_token
bundle exec rake db:migrate RAILS_ENV=production
bundle exec rake redmine:plugins:migrate RAILS_ENV=production
chown -R root:www-data /var/www/redmine
mkdir /public/plugin_assets
chown -R www-data:www-data files/ log/ tmp/ public/plugin_assets
reboot

log into your webserver as admin=>administration=>information
and you should see that it was upgraded. Ensure that there is no error with the plugin write access. You may have to go in and change ownership of some stuff. This is where it got funky with mine and I forgot what I did so I think the above commands is what I did but not sure.

RE: redmine upgrade from 2.2.3.stable to 2.5.1 does not work - Added by d s 2 months ago

I have added the results of my own experiences in the post #41238 as I could solve that issue of a Redmine apparently not updated.

I hope this helps.

Pierre.

(1-5/5)