Redmine

You have to check your server logs for more information, specifically the logs of your application server (e.g. phusion) which are likely co-located with your webserver logs, as well as the log of Redmine in log/production.log within your the Redmine directory on the server.

In any case, please note that Remdine used its own rails version which is installed via bundler. To update a Remdine installed from source, please see RedmineUpgrade.

Only if you installed Redmine using the `redmine` apt package from Ubuntu, it will use Ubuntu's rails. If you use Ubuntu's redmine package, you should open an issue on Ubuntu's bug tracker (or the one form Debian since the redmine package is actually maintained by Debian people). As the packaged redmine version in Ubuntu is changed from what we ship here at redmine.org, we may not have all insight into how to best configure or update it.

Hi Holger,

thanks for your reply.

The production log doesn't show any information

The apache error.log file I think is the one to check and among a lot of msg I found this one:

Error: The application encountered the following error: Your Ruby version is 3.2.3, but your Gemfile specified >= 2.5.0, < 3.2.0 (Bundler::RubyVersionMismatch)

If I check list of ruby packages available this is part the result

# apt list | grep ruby
.
.
ruby3.0-dev/now 3.0.2-7ubuntu2.7 amd64 [installed,local]
ruby3.0-doc/now 3.0.2-7ubuntu2.7 all [installed,local]
ruby3.0/now 3.0.2-7ubuntu2.7 amd64 [installed,local]
ruby3.2-dev/noble-updates,noble-security,now 3.2.3-1ubuntu0.24.04.3 amd64 [installed,automatic]
ruby3.2-dev/noble-updates,noble-security 3.2.3-1ubuntu0.24.04.3 i386
ruby3.2-doc/noble-updates,noble-updates,noble-security,noble-security,now 3.2.3-1ubuntu0.24.04.3 all [installed,automatic]
ruby3.2/noble-updates,noble-security,now 3.2.3-1ubuntu0.24.04.3 amd64 [installed,automatic]
ruby3.2/noble-updates,noble-security 3.2.3-1ubuntu0.24.04.3 i386
ruby/noble,now 1:3.2~ubuntu1 amd64 [installed]
ruby/noble 1:3.2~ubuntu1 i386
rubygems-integration/noble,noble,now 1.18 all [installed]
.
.

If I read the package list correctly there is the Ruby 3.0.2-7 version installed along with ruby-3.2.3.

How can I force redmine to use the 3.0.2 version vs the latest installed?
I'm not sure this will solve the issue but it sounds the closest I came along so far

I hope this thread will help also others who ended up to the same situation

regards

Redmine 5.1.x should support Ruby 3.2 just fine. Only older versions, including Redmine 5.0.x do not yet support Ruby 3.2. See RedmineInstall for a list of requirements.

In any case, when using Passenger, you can configure the Ruby interpreter to use with the PassengerRuby configuration option.

Short edit

searching further the net, I came across the possibility to use rbenv

https://stackoverflow.com/questions/71371079/fix-your-ruby-version-is-2-6-8-but-your-gemfile-specified-2-5-5

but I don't know how and didn't use it before when the server was working fine so I'm not sure I should install and try something I don't know potentially messing up everything even more.

Suggestions?

Holger Just wrote in RE: redmine doesn't work after migrating to latest ubuntu...:

Redmine 5.1.x should support Ruby 3.2 just fine. Only older versions, including Redmine 5.0.x do not yet support Ruby 3.2. See RedmineInstall for a list of requirements.

In any case, when using Passenger, you can configure the Ruby interpreter to use with the PassengerRuby configuration option.

Thanks again Holger.

I update redmine using svn method following the upgrading procedure so I don't know what to say about Redmine 5.1.

mauro santini wrote in RE: redmine doesn't work after migrating to latest ubuntu...:

Holger Just wrote in RE: redmine doesn't work after migrating to latest ubuntu...:

Redmine 5.1.x should support Ruby 3.2 just fine. Only older versions, including Redmine 5.0.x do not yet support Ruby 3.2. See RedmineInstall for a list of requirements.

In any case, when using Passenger, you can configure the Ruby interpreter to use with the PassengerRuby configuration option.

Thanks again Holger.

I update redmine using svn method following the upgrading procedure so I don't know what to say about Redmine 5.1.

Sorry, sent by mistake.

how can I check the actual version of redmine after svn upgrade?

regarding the passengerRuby configuration, am I correct that domething like PassengerFriendlyErrorPages on/off goes into the virtual host .conf file? this was one of the question of my first post.

I'm only using ruby and passenger to run redmine and it is quite hard to get all this aspects. I'm not an IT guy so ruby is a parallel world for me

thanks again

Partially fixed.

Following this thread:

https://stackoverflow.com/questions/71371079/fix-your-ruby-version-is-2-6-8-but-your-gemfile-specified-2-5-5

I installed rbenv, set a local ruby version, run bundle upgradeas for new update procedure, update .bash_profile and redmine start to work again.

Now,despite I run the svn upgrade, it is still redmine 5.0.10. To get the latest redmine 5.1 do I have to download it in a new directory and move on from there?

Regarding phusion and the PassengerFriendlyErrorPages, it has been a great surprise to read in the landing page the detailed error log once I understond that this option needs to be in the virtual host conf file.

waiting news about upgrade redmine to latest releas I thank you all for your support

Depending on which source (branch or tag) you used exactly, you may need to switch to the new branch. If e.g. you previously used the branches/5.0-stable branch, to update to Redmine 5.1, you would need to switch to the branches/5.1-stable branch with a command like

svn switch https://svn.redmine.org/redmine/branches/5.1-stable

Holger Just wrote in RE: redmine doesn't work after migrating to latest ubuntu...:

Depending on which source (branch or tag) you used exactly, you may need to switch to the new branch. If e.g. you previously used the branches/5.0-stable branch, to update to Redmine 5.1, you would need to switch to the branches/5.1-stable branch with a command like

[...]

Thanks Holger.

I think this is an important piece of information which should be integrated with the upgrade procedure. I'm sure it will be appreciated by many

I'll give it a go and hopefully I'll manage to get it running with no hicups after the switch

regards