Hi,
I had the same problem on our instance, fortunately I managed to fix it using the instructions here and also since I have two instances running I tried again with the second - the problem seems to be mostly/entirely on not clearing the cache before upgrading.
On the install instructions:
Step 4: Clear Zammad cache
$ zammad run railsr "Cache.clear"
produces
sh: 1: exec: railsr: not found
(extra r after rails) and the presumably correct zammad run rails "Cache.clear"
or zammad run rails Cache.clear
both product the following:
rails aborted!
Don’t know how to build task ‘Cache.clear’ (See the list of available tasks withrails --tasks
)
Did you mean? tmp:cache:clear
/opt/zammad/vendor/bundle/ruby/2.6.0/gems/railties-5.2.4.6/lib/rails/commands/rake/rake_command.rb:23:inblock in perform' /opt/zammad/vendor/bundle/ruby/2.6.0/gems/railties-5.2.4.6/lib/rails/commands/rake/rake_command.rb:20:in
perform’
/opt/zammad/vendor/bundle/ruby/2.6.0/gems/railties-5.2.4.6/lib/rails/command.rb:48:ininvoke' /opt/zammad/vendor/bundle/ruby/2.6.0/gems/railties-5.2.4.6/lib/rails/commands.rb:18:in
’
/opt/zammad/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:inrequire' /opt/zammad/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in
block in require_with_bootsnap_lfi’
/opt/zammad/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/loaded_features_index.rb:65:inregister' /opt/zammad/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in
require_with_bootsnap_lfi’
/opt/zammad/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:inrequire' /opt/zammad/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:291:in
block in require’
/opt/zammad/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:257:inload_dependency' /opt/zammad/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:291:in
require’
/opt/zammad/bin/rails:9:in `’
(See full trace by running task with --trace)
However, running zammad rails run c
followed by Cache.clear
seemed to produce no errors (though a lot of output - tmp files it’s presumably clearing out).
After this, running the package update (apt in my case) ran correctly, with DB migrations and resulted in a working install. The problem with the process seems to be the instruction to clear the cache not working - the instructions have a typo in them, but even without that there is an error on both my systems at least.