Windows Upgrade 0.9.3 to 1.0 Problem

I have a problem upgrading Redmine from 0.9.3 to 1.0. I used the Sep14 “How to..” instructions. First problem – The two ruby.exe processes run until they consume up to 60Mbytes of memory, then disappear and restart from 0 again. This problem was fixed by following Carlos advice to me in March (when I upgraded from 0.9.2 to 0.9.3) which was to add a file: redmine/config/initializers/mongrel_cluster_with_rails_23_fix.rb.

However, now when I try to access Redmine, the browser comes back with “Internal Error” (The browser tab heading is Redmine 500 error).

The Bitnami stack is the one which included Redmine version 0.9.2. I have only upgraded the Redmine app itself (from 0.9.2 to 0.9.3 and now to 1.0.0).

Any help would be greatly appreciated.

Are the ruby processes running? Could you try to restart the Apache server? Could you post the latest lines of the Apache2/logs/error.log and apps/redmine/log/mongrel.3001.log files?

Yes, the ruby processes are running. I have attached the Apache log file that you requested but I cannot find a mongrel.3001.log file. Searching the whole of Bitnami Redmine Stack, there is no such file in any of the versions of redmine that I have on the disk. Are the settings which need changing to create such a log?

Note that on Thursday afternoon, I reverted to the previous version and re-installed version 1.0 this morning.

Many Thanks.

Attached Files

I have been taking a look at the other logs, and the production.log in the redmine directory has the following error in it:
ActionView::TemplateError (undefined method `cache_formatted_text?’ for #) on line #24 of app/views/welcome/index.rhtml:

Is this any help? I have attached the complete log.

Attached Files

Have you installed any plugin in the previous Redmine version? Could you try to uninstall it and upgrade the application?

No. Just the basic redmine out of the box.

Not sure what could be the problem. Did you clean the cache browser?

I ran rake tmp:cache:clear and rake tmp:sessions:clear. Perhaps I should just download the full Bitnami 1.0 installer and do a full install then restore the database.

I decided to download the Bitnami 1.0 Redmine stack and restore my database from backup. Success (and less traumatic than I had expected)! However, it is worth noting that the September 14th 2009 How to upgrade tutorial has been updated on 18th May 2010. The new version includes simple instructions for upgrading either just the Redmine code or the complete stack which are very helpful. It is not clear from the forum entry that these instructions have been updated (unless you actually look in the post).

I’m glad to hear this. Thanks for your feedback.

Hi, So I just did these same steps (upgrade to 1.0 from 0.9.3). I installed the 1.0 Redmine stack, backed up/restored database:

mysql -u root -p bitnami_redmine < redmine_backup.sql
rake db:migrate RAILS_ENV=production
rake db:migrate:upgrade_plugin_migrations RAILS_ENV=production
rake db:migrate_plugins RAILS_ENV=production
rake tmp:cache:clear
rake tmp:sessions:clear

stopped and restarted everything and I get the error you see below. Any ideas?

And I get:

NoMethodError in Welcome#index
Showing app/views/welcome/index.rhtml where line #4 raised:

undefined method `cache_formatted_text?’ for #

Extracted source (around line #4):

RAILS_ROOT: C:/Program Files/BitNami Redmine Stack/apps/redmine

Application Trace | Framework Trace | Full Trace
C:/Program Files/BitNami Redmine Stack/apps/redmine/vendor/rails/activerecord/lib/active_record/base.rb:1959:in `method_missing’
C:/Program Files/BitNami Redmine Stack/apps/redmine/lib/redmine/wiki_formatting.rb:47:in `to_html’
C:/Program Files/BitNami Redmine Stack/apps/redmine/app/helpers/application_helper.rb:421:in `textilizable’
C:/Program Files/BitNami Redmine Stack/apps/redmine/app/views/welcome/index.rhtml:4:in `_run_rhtml_app47views47welcome47index46rhtml’

Try the following: http://www.redmine.org/boards/2/topics/12952

Thanks! That was exactly the problem. I had copied over my old settings.yml, didn’t even occur to me that that was the problem…