Zammad restored from backup - 502 Bad Gateway

Zammad 3.1.0 Centos 7 installed from package (stable).

  1. run backup script
  2. upgrade Zamad 3.1.0->3.2.0 from package (develop)
  3. Check Zammad (no visual problems, no visible changes)
  4. restore Zammad from last backup (files and db) #1
  5. after restore completed ok - got empty browser screen with error 502 Bad Gateway.
  6. Centos host reboot - error 502
    nginx, postgresql, zammad services - all running.
    /var/log/nginx/zammad.error.log:

2019/10/16 16:42:13 [error] 1426#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 10.10.3.10, server: helpdesk.XXXX.XY, request: “GET / HTTP/2.0”, upstream: “http://127.0.0.1:3000/”, host: “helpdesk.XXXX.XY”

/var/log/messages has repeating block of events now:

Oct 16 16:45:44 helpdesk systemd: Started zammad-worker-1.service.
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: bundler: failed to load command: script/websocket-server.rb (script/websocket-server.rb)
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: NameError: uninitialized constant OmniAuth::Strategies::SAML
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/co$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/co$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/co$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/co$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/lib/saml_database.rb:1:in <main>' Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/co$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/co$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/lo$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/co$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/co$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/config/initializers/vendor_lib.rb:4:inblock in ’
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/config/initializers/vendor_lib.rb:2:in each' Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/config/initializers/vendor_lib.rb:2:in
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/co$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/co$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/engine.rb:657:in blo$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.3/lib/active_support/notific$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/engine.rb:656:inloa$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/engine.rb:614:in blo$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/engine.rb:613:ineac$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/engine.rb:613:in blo$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:i$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:32:i$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:61:i$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:228:inblock in tsort_each’
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:350:in block (2 levels) in each_s$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:422:inblock (2 levels) in each_s$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:431:in each_strongly_connected_co$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:421:inblock in each_strongly_con$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:i$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:50:i$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:415:in call' Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:415:ineach_strongly_connected_co$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:349:in block in each_strongly_con$ Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:347:ineach’
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:347:in call' Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:347:ineach_strongly_connected_co$
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:226:in tsort_each' Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/tsort.rb:205:intsort_each’
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/initializable.rb:60:in run_initializers' Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/application.rb:361:ininitialize!’
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: /opt/zammad/config/environment.rb:5:in <top (required)>' Oct 16 16:45:45 helpdesk zammad-websocket-1.service: script/websocket-server.rb:14:inrequire’
Oct 16 16:45:45 helpdesk zammad-websocket-1.service: script/websocket-server.rb:14:in `<top (required)>’
Oct 16 16:45:45 helpdesk systemd: zammad-websocket-1.service: main process exited, code=exited, status=1/FAILURE
Oct 16 16:45:45 helpdesk systemd: Unit zammad-websocket-1.service entered failed state.
Oct 16 16:45:45 helpdesk systemd: zammad-websocket-1.service failed.
Oct 16 16:45:45 helpdesk systemd: zammad-websocket-1.service holdoff time over, scheduling restart.
Oct 16 16:45:45 helpdesk systemd: Stopped zammad-websocket-1.service.

what to do?

my fix:
yum uninstall zammad
rm -rf /opt/zammad
yum install zammad (from stable)
restore from backup.
Problem fixed.
P.S. Is it normal or v3.2.0 just not compatible with 3.1.0 ?

1 Like

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.