Infos:
- Used Zammad version: 3.1.X
- Used Zammad installation source: Package
- Operating system: Ubuntu 18.04.03 LTS
Expected behavior:
- Logfile without Error Message
Actual behavior:
- Logfile shows Error:
I, [2019-09-16T07:36:30.190337 #580-47053315991240] INFO -- : Send notification to: recipient@domain.com (from:Notification Master <support@domain.com>/subject:Neues Ticket (EIL
T - Zg-Auftrag 844125) [Ticket#20190916310004])
E, **[2019-09-16T07:36:30.987451 #580-47053315991240] ERROR -- : undefined method `first' for nil:NilClass (NoMethodError)**
/opt/zammad/lib/signature_detection.rb:42:in `block in find_signature'
/opt/zammad/lib/signature_detection.rb:29:in `each'
/opt/zammad/lib/signature_detection.rb:29:in `find_signature'
/opt/zammad/lib/signature_detection.rb:137:in `by_user_id'
/opt/zammad/lib/signature_detection.rb:172:in `rebuild_user'
/opt/zammad/app/models/transaction/signature_detection.rb:48:in `perform'
/opt/zammad/app/models/observer/transaction.rb:62:in `execute_singel_backend'
/opt/zammad/app/models/transaction/background_job.rb:30:in `block in perform'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.3/lib/active_record/relation/delegation.rb:71:in `each'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.3/lib/active_record/relation/delegation.rb:71:in `each'
/opt/zammad/app/models/transaction/background_job.rb:26:in `perform'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/backend/base.rb:81:in `block in invoke_job'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/lifecycle.rb:61:in `block in initialize'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/lifecycle.rb:66:in `execute'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/backend/base.rb:78:in `invoke_job'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/worker.rb:230:in `block (2 levels) in run'
/opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/timeout.rb:93:in `block in timeout'
/opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/timeout.rb:103:in `timeout'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/worker.rb:230:in `block in run'
/opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/worker.rb:229:in `run'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/worker.rb:312:in `block in reserve_and_run_one_job'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/lifecycle.rb:61:in `block in initialize'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/lifecycle.rb:66:in `execute'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/worker.rb:312:in `reserve_and_run_one_job'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/worker.rb:213:in `block in work_off'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/worker.rb:212:in `times'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.7/lib/delayed/worker.rb:212:in `work_off'
/opt/zammad/app/models/scheduler.rb:367:in `block (3 levels) in worker'
/opt/zammad/vendor/ruby-2.5.5/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'
/opt/zammad/app/models/scheduler.rb:365:in `block (2 levels) in worker'
/opt/zammad/app/models/scheduler.rb:361:in `loop'
/opt/zammad/app/models/scheduler.rb:361:in `block in worker'
/opt/zammad/vendor/bundle/ruby/2.5.0/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:474:in `block in create_with_logging_context'
I, [2019-09-16T07:36:31.252233 #580-47053315991240] INFO -- : 2019-09-16T07:36:31+0200: [Worker(host:support pid:580)] Job Transaction::BackgroundJob (id=2616244) COMPLETED after 1.3408
Steps to reproduce the behavior:
- Have no actual workflow to reproduce it
I didn’t hear anything from my users regarding a problem cause of that, but as zammad is showing me this error, I’d like to know where it comes from and how I could get rid of this.
