Ruby Errors in Production Log

Infos:

  • Used Zammad version: 3.1
  • Used Zammad installation source: (source, package, …) deb
  • Operating system: debian 9.9
  • Browser + version:

Expected behavior:

/

Actual behavior:

I recive this ruby error messages in /var/log/zammad/production.log when a mail is beeing processed:

E, [2019-11-07T11:01:14.779658 #514-47453005592360] 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'

Steps to reproduce the behavior:

No clue…

I think fixed these errors with:
gem update --system

While the update took place, i recived some errors:

Regenerating binstubs
`/usr/share/rubygems-integration/all/gems/bundler-1.13.6/exe/bundle` does not exist, maybe `gem pristine bundler` will fix it?
`/usr/share/rubygems-integration/all/gems/bundler-1.13.6/exe/bundler` does not exist, maybe `gem pristine bundler` will fix it?
`/usr/share/rubygems-integration/2.3.0/gems/byebug-5.0.0/bin/byebug` does not exist, maybe `gem pristine byebug` will fix it?
`/usr/share/rubygems-integration/all/gems/erubis-2.7.0/bin/erubis` does not exist, maybe `gem pristine erubis` will fix it?
`/usr/share/rubygems-integration/all/gems/listen-3.0.3/bin/listen` does not exist, maybe `gem pristine listen` will fix it?
`/usr/share/rubygems-integration/all/gems/rack-1.6.4/bin/rackup` does not exist, maybe `gem pristine rack` will fix it?
`/usr/share/rubygems-integration/all/gems/railties-4.2.7.1/bin/rails` does not exist, maybe `gem pristine railties` will fix it?
`/usr/share/rubygems-integration/all/gems/rake-10.5.0/bin/rake` does not exist, maybe `gem pristine rake` will fix it?
`/usr/share/rubygems-integration/all/gems/sass-3.4.23/bin/sass` does not exist, maybe `gem pristine sass` will fix it?
`/usr/share/rubygems-integration/all/gems/sass-3.4.23/bin/sass-convert` does not exist, maybe `gem pristine sass` will fix it?
`/usr/share/rubygems-integration/all/gems/sass-3.4.23/bin/scss` does not exist, maybe `gem pristine sass` will fix it?
`/usr/share/rubygems-integration/all/gems/sdoc-0.4.1/bin/sdoc` does not exist, maybe `gem pristine sdoc` will fix it?
`/usr/share/rubygems-integration/all/gems/sdoc-0.4.1/bin/sdoc-merge` does not exist, maybe `gem pristine sdoc` will fix it?
`/usr/share/rubygems-integration/all/gems/spring-1.3.6/bin/spring` does not exist, maybe `gem pristine spring` will fix it?
`/usr/share/rubygems-integration/all/gems/sprockets-3.7.0/bin/sprockets` does not exist, maybe `gem pristine sprockets` will fix it?
`/usr/share/rubygems-integration/all/gems/thor-0.19.1/bin/thor` does not exist, maybe `gem pristine thor` will fix it?
`/usr/share/rubygems-integration/all/gems/tilt-2.0.1/bin/tilt` does not exist, maybe `gem pristine tilt` will fix it?
`/usr/share/rubygems-integration/all/gems/treetop-1.6.7/bin/tt` does not exist, maybe `gem pristine treetop` will fix it?

I run these commands succesfully and now no more errors appear (for now)

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