Cant Login after upgrade to 3.3

  • Used Zammad version: 2.8
  • Used Zammad installation source: deb
  • Operating system: ubuntu 18.04
  • Browser + version: any

Expected behavior:

can log in same credentials after update and upgrade

Actual behavior:

Cant login
image

Steps to reproduce the behavior:

  1. Working zammad 2.8
  2. sudo systemctl stop zammad
  3. apt update
  4. apt upgrade
    restart system/machine then still cant login after update from 2.8 version

ANY ADVICE HOW CAN I UPGRADE SMOOTHLY THANK YOU

also tried run db:migrate below are the error

rake aborted!
StandardError: An error has occurred, this and all later migrations canceled:

PG::UndefinedTable: ERROR: relation “active_job_locks” does not exist
LINE 8: WHERE a.attrelid = ‘“active_job_locks”’::regc…
^
: SELECT a.attname, format_type(a.atttypid, a.atttypmod),
pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod,
c.collname, col_description(a.attrelid, a.attnum) AS comment
FROM pg_attribute a
LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum
LEFT JOIN pg_type t ON a.atttypid = t.oid
LEFT JOIN pg_collation c ON a.attcollation = c.oid AND a.attcollation <> t.typcollation
WHERE a.attrelid = ‘“active_job_locks”’::regclass
AND a.attnum > 0 AND NOT a.attisdropped
ORDER BY a.attnum
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:63:in async_exec' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:63:in block (2 levels) in query’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.4.1/lib/active_support/dependencies/interlock.rb:48:in block in permit_concurrent_loads' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.4.1/lib/active_support/concurrency/share_lock.rb:187:in yield_shares’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.4.1/lib/active_support/dependencies/interlock.rb:47:in permit_concurrent_loads' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:62:in block in query’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/abstract_adapter.rb:581:in block (2 levels) in log' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/abstract_adapter.rb:580:in block in log’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.4.1/lib/active_support/notifications/instrumenter.rb:23:in instrument' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/abstract_adapter.rb:571:in log’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:61:in query' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/postgresql_adapter.rb:757:in column_definitions’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/abstract/schema_statements.rb:113:in columns' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/schema_cache.rb:69:in columns’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/schema_cache.rb:75:in columns_hash' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/model_schema.rb:466:in load_schema!’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/attributes.rb:234:in load_schema!' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/attribute_decorators.rb:51:in load_schema!’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/model_schema.rb:459:in block in load_schema' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/model_schema.rb:456:in load_schema’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/model_schema.rb:346:in attribute_types' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/model_schema.rb:370:in type_for_attribute’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/table_metadata.rb:33:in type' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/relation/predicate_builder.rb:51:in build’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/relation/predicate_builder.rb:112:in block in expand_from_hash' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/relation/predicate_builder.rb:71:in each’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/relation/predicate_builder.rb:71:in flat_map' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/relation/predicate_builder.rb:71:in expand_from_hash’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/relation/predicate_builder.rb:21:in build_from_hash' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/relation/where_clause_factory.rb:19:in build’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/relation/query_methods.rb:588:in where!' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/relation/query_methods.rb:581:in where’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/relation/finder_methods.rb:81:in find_by' /opt/zammad/app/jobs/concerns/has_active_job_lock.rb:117:in active_job_lock’
/opt/zammad/app/jobs/concerns/has_active_job_lock.rb:107:in active_job_lock_for_enqueue!' /opt/zammad/app/jobs/concerns/has_active_job_lock.rb:58:in block in ensure_active_job_lock_for_enqueue!’
/opt/zammad/app/jobs/concerns/has_active_job_lock.rb:90:in block in in_active_job_lock_transaction' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/abstract/database_statements.rb:267:in block in transaction’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/abstract/transaction.rb:239:in block in within_new_transaction' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/abstract/transaction.rb:236:in within_new_transaction’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/connection_adapters/abstract/database_statements.rb:267:in transaction' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.4.1/lib/active_record/transactions.rb:212:in transaction’
/opt/zammad/app/jobs/concerns/has_active_job_lock.rb:89:in in_active_job_lock_transaction' /opt/zammad/app/jobs/concerns/has_active_job_lock.rb:57:in ensure_active_job_lock_for_enqueue!’
/opt/zammad/app/jobs/concerns/has_active_job_lock.rb:6:in block (2 levels) in <module:HasActiveJobLock>' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.4.1/lib/active_support/callbacks.rb:426:in instance_exec’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.4.1/lib/active_support/callbacks.rb:426:in block in make_lambda' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.4.1/lib/active_support/callbacks.rb:198:in block (2 levels) in halting’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.4.1/lib/active_support/callbacks.rb:606:in block (2 levels) in default_terminator' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.4.1/lib/active_support/callbacks.rb:605:in catch’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.4.1/lib/active_support/callbacks.rb:605:in block in default_terminator' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.4.1/lib/active_support/callbacks.rb:199:in block in halting’
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/active

Thank you

fixed already

run zammad run rails db:migrate not zammad run rake db:migrate
then
zammad run rake searchindex:rebuild

Thanks for this solution. Had the exact same problem.

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