Content
No email notifications
Added by Radu Stefan about 1 year ago
Hi all.
I have installed openproject 12.5.8 CE with postgresql 13.11 on a Ubuntu Server 18.04.6LTS.
I've installed it via repositories and everything is working great except email notifications on package modifications and others.
I've went through 11 => 12 upgrade and in the logs I can see this error:
Date: Tue, 12 Sep 2023 16:25:02 +0300 (EEST)
rake aborted!
Bundler::RubyVersionMismatch: Your Ruby version is 2.5.1, but your Gemfile specified ~> 3.2.1
/opt/openproject/config/boot.rb:37:in `<top (required)>'
This happens every 1 minute because the use openproject has a crontab installed as follows:
*/1 * * * * cd /opt/openproject/; /opt/openproject/vendor/bundle/ruby/3.2.0/bin/rake jobs:workoff
Password reset and test email work correctly.
I've searched and re-searched and I'm loosing my minds!
What could be the culprit of this?
Indeed, the ruby version installed on the server is 2.5.1 but as far as I can tell from the cronjob, it uses the bundled ruby version which is version 3.2.0.
I've also installed ruby 3.2.1 with rvm and when manually running the command from crontab, it throws the following error:
https://github.com/opf/omniauth (at fe862f9@fe862f9) is not yet checked out. Run `bundle install` first.
Any ideas are greatly appreciated!
Cheers,
Radu
Replies (1)
L.E.: I've installed ruby 3.2.1, the one which was indicated in the log file errors and I've executed bundle install since openproject complained about gems not being installed.
Now, it complains only about the ruby version:
Date: Wed, 13 Sep 2023 13:15:02 +0300 (EEST)
rake aborted!
Bundler::RubyVersionMismatch: Your Ruby version is 2.5.1, but your Gemfile specified ~> 3.2.1
/opt/openproject/config/boot.rb:37:in `<top (required)>'
/opt/openproject/config/application.rb:29:in `require_relative'
/opt/openproject/config/application.rb:29:in `<top (required)>'
/opt/openproject/Rakefile:33:in `<top (required)>'
/usr/share/rubygems-integration/all/gems/rake-12.3.1/exe/rake:27:in `<top (required)>'
(See full trace by running task with --trace)
Still, this morning me and my colleagues received an email notiifcation regarding unread notifications so I guess this is a step forward!