Scheduler may not run (last execution of ImportJob.start_registered 4 days over) - please contact your system administrator


  • Used Zammad version: 4.0
  • Used Zammad installation source: (source, package, …) package from APT
  • Operating system: Ubuntu 16.04.
  • Browser + version: Chrome

Expected behavior:

fetching mails regulary

Actual behavior:

Not fetching mails
System is very slow and creates high load.

Steps to reproduce the behavior:

Since some days fetching worked only after server restart.

Then I upgraded to Zammad 4.0

Ubuntu 16 with APT.

I was able now to fetch mails manual but I see these errors:

I, [2021-04-12T14:37:58.190263 #6435-47131396331940] INFO – : Checking left over delayed job #<Delayed::Backend::ActiveRecord::Job id: 192730, priority: 0, attempts: 0, handler: “— !ruby/object:Transaction::BackgroundJob\nitem:\n…”, last_error: nil, run_at: “2021-04-08 10:26:12”, locked_at: “2021-04-08 10:27:02”, failed_at: nil, locked_by: “host:euve269896 pid:13693”, queue: nil, created_at: “2021-04-08 10:26:12”, updated_at: “2021-04-08 10:26:12”> started.

And when I try to destroy I get this:

irb(main):001:0> Delayed::Job.find(192730).destroy
Traceback (most recent call last):
2: from (irb):1
1: from config/initializers/delayed_jobs_ensure_active_job_lock_removal.rb:10:in `remove_active_job_lock’
Delayed::DeserializationError (Job failed to load: undefined class/module Transaction::BackgroundJob. Handler: “— !ruby/object:Transaction::BackgroundJob\nitem:\n :object: Ticket\n :object_id: 13138\n :user_id: 88\n :created_at: !ruby/object:ActiveSupport::TimeWithZone\n utc: &1 2021-04-08 10:26:00.921876098 Z\n zone: !ruby/object:ActiveSupport::TimeZone\n name: Etc/UTC\n time: *1\n :type: create\n :article_id: 16847\nparams:\n :interface_handle: scheduler\n”)

irb(main):002:0> Delayed::Job.count
=> 3619

Your help is very appreciated.

Best wishes


You may want to stop blindly destroying delayed jobs.
Destroying stuff without understanding the scope is a very dangerous operation and may cause data loss.

As you upgraded to Zammad 4.0 ensure that you did run the required reindex of Elasticsearch:
zammad run rake searchindex:rebuild.

If you did that and received error messages, ensure it’s running and you’re running a supported version: Software — Zammad documentation

You may also want to double check what exactly draws so much power of your ressources. Sounds fishy but is impossible to help you with at this state. We don’t even know from which version you came.

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