Internal error while trying to login in Redmine 2.3.1-1

Bug #1239686 reported by Anton Statutov on 2013-10-14
This bug affects 7 people
Affects Status Importance Assigned to Milestone
redmine (Ubuntu)

Bug Description

1) OS: Ubuntu 13.10
2) Package: redmine 2.3.1-1
3) What's expected: I'm authorized.
4) What's happened: Internal error and 'NoMethodError' error (see attachment)

Anton Statutov (astatutov) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in redmine (Ubuntu):
status: New → Confirmed
Chris Monahan (cobra-v) wrote :

We experienced this on our server as well. Thankfully we use VMware and can revert to raring. Please fix this.

Chris Monahan (cobra-v) wrote :

I just want to add that I fixed this issue, credit goes to this page

As root, run gem install rack -v 1.4.5
Go to /usr/share/redmine
Edit Gemfile
Third line down (after source) add: gem "rack", "1.4.5"
Then run bundle update (from /usr/share/redmine
Restart apache, and it should work

Of course, don't forget to change the adapter in /etc/redmine/default/database.yml to:
  adapter: mysql2

(credit for that one goes to bug # 1240705)

Pascal A. (pascalav) wrote :

No "gem install" for me. I trust the OS packages tree to get those gems, and don't wish to get a sub packages tree (a ruby one I mean). In a nutshell, I prefer "sudo aptitude install ruby-charlock-holmes" rather than " sudo gem install charlock_holmes --version '0.6.9'" ;)

Pascal A. (pascalav) wrote :

Confirmation that "Chris Monahan (cobra-v)" solution (#4) is working. I'll wait for a package update anyway.

Concerning this error at install time:
rake aborted!
Please install the mysql adapter: `gem install activerecord-mysql-adapter`
Manually installing the 'ruby-mysql2' package allowed the install process to success until the end. Note, that's important, that this package doesn't seem to be in the 'redmine' nor 'redmine-mysql' dependencies, but it should.

After such a successfull reinstall, the problem remains the same : HTTP error 500 on login, and 'NoMethodError' .. 'options' in logs.

Regarding purge and uninstall, my OS sent much crash reports, and I got many broken situations, due to conflicts between 'redmine' and 'dbconfig-common'. It seems any of those 2 packages isn't purging right, and lets an orphan non-empty 'redmine' directory in the dbconfig-common configuration. I also realized that dbconfig-common drops the redmine database when asked, but not its redmine user. Maybe this is normal.

When reinstalling, I went on various situations:
 - 'redmine'@'localhost' identified by '' could not access database
 - The '<path_to_dbconfig_commons_redmine-specific_settings>' doesn't exists but was manually deleted: not recreating' (maybe the 'adapter: mysql' value, is brought directly from the dbconfig-common redmine-specific settings, with no indirection mysql/mysql2 relying on ruby 1.8.1/>=1.9)

I hope not having to reinstall the 'redmine' package as well ^^ Thanks VirtualBox and snapshots

Pascal A. (pascalav) wrote :

About this :
The '<path_to_dbconfig_commons_redmine-specific_settings>' doesn't exists but was manually deleted: not recreating'

The base problem is that dpkg complains (warning) upon 'redmine' purge, cause 'dbconfig-common' can't remove '<path_to_dbconfig_commons_base-dir_settings>', cause it's non empty. But if you help and get it empty with an 'rm', it won't be recreated upon next install.

I must be weak in packages management as well, and must be doing something wrong about that.

da6930p (da6930p) wrote :

Any solutions for this?

da6930p (da6930p) wrote :

I've tried to do the change with editing Gemfile with

Third line down (after source) add: gem "rack", "1.4.5"

but nothing happened. Again i get "Redmine 500 error" while trying to login.

Anton Statutov (astatutov) wrote :

da6930p, did you restart application?

da6930p (da6930p) wrote :

Yes nothing changed.

Anton Statutov (astatutov) wrote :

Of course, you didn't forget "gem install rack -v 1.4.5"?

And also in my Gemfile there is 'gem "rake"' line, I don't know if it's critical or not:
gem "rack", "1.4.5"
gem "rake"

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments