Overview won't refresh


overall our zammad runs smooth (6 active Agents ~200-500Tickets/day, 90% are beeing closed via triggers). One issue remains: overviews won’t refresh any more. Even after I switched servers.

On the new server I installed zammad from package. The Elasticsearch server is on a different VM. I got another zammad VM (3 active agents), which runs just fine. I restored the data via zammad_restore.sh

I already took those measures:

  • zammad config:set WEB_CONCURRENCY=4

  • mount -t tmpfs -o size=8g tmpfs /opt/zammad/tmp

  • zammad run rails r ‘p Delayed::Job.count’ = 0

attached you’ll find stats from the VM and inside the VM:

  • Used Zammad version:
  • Used Zammad installation source: package
  • Operating system: Ubuntu 18.04 LTS
  • Browser + version: any

Expected behavior:

  • refreshing the overwiew automatically

Actual behavior:

  • agents have to refresh the browser window

Steps to reproduce the behavior:

  • open ticket, close it - still on the “only open tickets” overview

What’s my best line here?


Have you made any changes to Zammad itself? E.g. disable jobs via rails console or so?

Please provide the following output:
zammad run rails r "p Scheduler.where(active: false).pluck(:name)"

Further more important: Does Zammad fetch and send mails as expected? Search functionality is being updated and working as expected…?

Also, the number of overviews may be interesting: zammad run rails r "p Overview.count".
While you’re at it, have a look at your overviews and ensure you don’t have more than 2100 entries.

Normally your scheduler.rb should run at 100% in these above scenarious I’m aiming at, but who knows, sometimes we have features. :man_shrugging:

thanks for the quick reply:

`zammad run rails r “p Scheduler.where(active: false).pluck(:name)”
[“Delete old online notification entries.”, “Generate Session data”, “Generate user based stats.”, “Sync calendars with ical feeds.”]

zammad run rails r “p Overview.count”

Everything works as expected, besides refreshing the overview.


Well here’s your problem.
Why in the world did you deactivate the above Scheduler-Tasks?

I mean I geniuly am curious why one would do that.

zammad run rails r "p Scheduler.where(active: false).update_all(active: true)"
Will re-activate all Zammad tasks and solve your issue.

Thanks for the fix.
How do I deactivate them?
would I have to run: zammad run rails r "p Scheduler.where(active: false).update_all(active: false)" , or is there another way, too?

What is your use case?
Why would you deactivate system relevant tasks??

Seriously, I’m curious to learn what you’re trying to achieve, it seems sketchy to me.

I think there’s a misunderstanding.
IMO I never did - I’ll try to find out how it did happen.

The scheduler got deactivated when I was on holiday, so I really don’t know what it triggered.

Okay, but upgrade processes from Zammad don’t do that as well.
So my guess is someone has been playing around.

I don’t suggest deactivating scheduler jobs, leaving them active should solve your issues.

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