Plugin problems after moving to Redmine 5.0.1 from 4.2.3
Added by Ivan Cenov 3 months ago
Hi,
I moved from 4Redmine 4.2.3 to Redmine 5.0.1. It started and works, but only when removed several plugins (removed means physically removed from the plugins folder, not de-installed). Below is the log when redmine_code_review plugin is in plugins folder. Other plugins that prevents Redmine to start are redmine_issue_templates, additionals, additional_tags.
E:\data\redmine>puma -e production -p 3002 *** SIGUSR2 not implemented, signal based restart unavailable! *** SIGUSR1 not implemented, signal based restart unavailable! *** SIGHUP not implemented, signal based logs reopening unavailable! Puma starting in single mode... * Puma version: 5.5.2 (ruby 2.6.9-p207) ("Zawgyi") * Min threads: 0 * Max threads: 5 * Environment: production * PID: 12392 ! Unable to load application: LoadError: cannot load such file -- gravatar C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/zeitwerk-2.5.4/lib/zeitwerk/kernel.rb:35:in `require': cannot load such file -- gravatar (LoadError) from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/zeitwerk-2.5.4/lib/zeitwerk/kernel.rb:35:in `require' from E:/data/redmine/plugins/redmine_code_review/init.rb:22:in `<top (required)>' from E:/data/redmine/lib/redmine/plugin_loader.rb:31:in `load' from E:/data/redmine/lib/redmine/plugin_loader.rb:31:in `run_initializer' from E:/data/redmine/lib/redmine/plugin_loader.rb:108:in `each' from E:/data/redmine/lib/redmine/plugin_loader.rb:108:in `block in load' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/callbacks.rb:427:in `instance_exec' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/callbacks.rb:427:in `block in make_lambda' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/callbacks.rb:198:in `block (2 levels) in halting' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/callbacks.rb:604:in `block (2 levels) in default_terminator' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/callbacks.rb:603:in `catch' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/callbacks.rb:603:in `block in default_terminator' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/callbacks.rb:199:in `block in halting' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/callbacks.rb:512:in `block in invoke_before' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/callbacks.rb:512:in `each' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/callbacks.rb:512:in `invoke_before' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/callbacks.rb:105:in `run_callbacks' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/activesupport-6.1.6/lib/active_support/reloader.rb:88:in `prepare!' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/railties-6.1.6/lib/rails/application/finisher.rb:124:in `block in <module:Finisher>' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/railties-6.1.6/lib/rails/initializable.rb:32:in `instance_exec' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/railties-6.1.6/lib/rails/initializable.rb:32:in `run' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/railties-6.1.6/lib/rails/initializable.rb:61:in `block in run_initializers' from C:/Ruby26-x64/lib/ruby/2.6.0/tsort.rb:228:in `block in tsort_each' from C:/Ruby26-x64/lib/ruby/2.6.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component' from C:/Ruby26-x64/lib/ruby/2.6.0/tsort.rb:431:in `each_strongly_connected_component_from' from C:/Ruby26-x64/lib/ruby/2.6.0/tsort.rb:349:in `block in each_strongly_connected_component' from C:/Ruby26-x64/lib/ruby/2.6.0/tsort.rb:347:in `each' from C:/Ruby26-x64/lib/ruby/2.6.0/tsort.rb:347:in `call' from C:/Ruby26-x64/lib/ruby/2.6.0/tsort.rb:347:in `each_strongly_connected_component' from C:/Ruby26-x64/lib/ruby/2.6.0/tsort.rb:226:in `tsort_each' from C:/Ruby26-x64/lib/ruby/2.6.0/tsort.rb:205:in `tsort_each' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/railties-6.1.6/lib/rails/initializable.rb:60:in `run_initializers' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/railties-6.1.6/lib/rails/application.rb:391:in `initialize!' from E:/data/redmine/config/environment.rb:16:in `<top (required)>' from C:/Ruby26-x64/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' from C:/Ruby26-x64/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' from config.ru:3:in `block in <main>' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/builder.rb:116:in `eval' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/builder.rb:116:in `new_from_string' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/builder.rb:105:in `load_file' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rack-2.2.3/lib/rack/builder.rb:66:in `parse_file' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/puma-5.5.2/lib/puma/configuration.rb:345:in `load_rackup' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/puma-5.5.2/lib/puma/configuration.rb:267:in `app' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/puma-5.5.2/lib/puma/runner.rb:149:in `load_and_bind' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/puma-5.5.2/lib/puma/single.rb:44:in `run' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/puma-5.5.2/lib/puma/launcher.rb:181:in `run' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/puma-5.5.2/lib/puma/cli.rb:80:in `run' from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/puma-5.5.2/bin/puma:10:in `<top (required)>' from C:/Ruby26-x64/bin/puma:23:in `load' from C:/Ruby26-x64/bin/puma:23:in `<main>' E:\data\redmine>
Replies (1)
RE: Plugin problems after moving to Redmine 5.0.1 from 4.2.3
-
Added by Markus Boremski 2 months ago
This error comes from Plugin redmine_code_review
As far as I understood in redmine 5 we now use Rails 6.
This uses Zeitwerk what leads to some changes regadring loading files.
I am facing the same issue here: https://github.com/xmera-circle/redmine_workload/issues/5
Maybe you can solve the problem with the hint there?
Maybe adress this problem on the github-page of the plugin.
(1-1/1)