From ubuntu 20.04 to 22.04

Infos:

  • Used Zammad version: 5.4.0-1678891710.3caa4004.jammy
  • Used Zammad installation type: package
  • Operating system: ubuntu 22.04.2
  • Browser + version: chrome

Expected behavior:

  • Backup a zammad on ubuntu 20.04 with latest package version : 5.4.0-1678873230.90fef43e.focal
    to restore to zammad with ubuntu 22.04.2 at latest version : 5.4.0-1678891710.3caa4004.jammy

Actual behavior:

  • when restoring :
    i have this error :
    # Clearing Cache ... /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require’: libssl.so.1.1: cannot open shared object file: No such file or directory - /opt/zammad/vendor/bundle/ruby/3.1.0/gems/openssl-3.1.0/lib/openssl.so (LoadError)
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/openssl-3.1.0/lib/openssl.rb:13:in ’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/activesupport-6.1.7.3/lib/active_support/key_generator.rb:4:in <main>' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/railties-6.1.7.3/lib/rails/application.rb:6:in ’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/railties-6.1.7.3/lib/rails.rb:13:in <main>' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/railties-6.1.7.3/lib/rails/all.rb:5:in ’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require’
    from /opt/zammad/config/application.rb:5:in <main>' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/railties-6.1.7.3/lib/rails/command/actions.rb:22:in require_application!’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/railties-6.1.7.3/lib/rails/command/actions.rb:14:in require_application_and_environment!' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/railties-6.1.7.3/lib/rails/commands/runner/runner_command.rb:33:in perform’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/thor-1.2.1/lib/thor/command.rb:27:in run' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in invoke_command’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/thor-1.2.1/lib/thor.rb:392:in dispatch' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/railties-6.1.7.3/lib/rails/command/base.rb:69:in perform’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/railties-6.1.7.3/lib/rails/command.rb:48:in invoke' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/railties-6.1.7.3/lib/rails/commands.rb:18:in ’
    from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require' from /opt/zammad/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in require’`

Steps to reproduce the behavior:

  • backup zammad with the provided script on ubuntu 20.04 with latest zammad package
  • restore this package on ubuntu 22.04.2 with latest zammad package

I have a working workaround
if you can : upgrade your ubuntu to 22.04.2 in place if possible
or reinstall a server with ubuntu 20.04 with zammad then install latest zammad package
the command is :

do-release-upgrade

this will take about 40min
then modify your repo file : /etc/apt/sources.list.d/zammad.list
change 20.04 to 22.04

then do a apt update and a apt upgrade, this will update zammad to the right ubuntu

you can do a backup and restore to the newest ubuntu or stay in the new ubuntu if you’ve from scratch.
and voilĂ !
hope there will be a fix for this issue

Just for your information… the steps you’ve taken are not needed. The documentation actually guides you through exactly this use case:
https://docs.zammad.org/en/latest/appendix/backup-and-restore/migrate-hosts.html

The issues you have clearly indicate that you backed up as FULL_FS_DUMP=yes (default) which overwrites OS and version dependend files on the host you restore to.

For the next time, the config settings and their description can be found here:
https://docs.zammad.org/en/latest/appendix/backup-and-restore/configuration.html

1 Like