If you are a Zammad Support or hosted customer and experience a technical issue, please refer to: email@example.com using your zammad-hostname / or company contract.
- Used Zammad version: 2.8
- Used Zammad installation source: (source, package, …) package
- Operating system: Ubuntu 18
- Browser + version: Chrome
Steps to reproduce the behavior:
This problem is something that is not easily produced, but what we are noticing is that when we have a few hundred folks signed into Zammad and creating tickets, Zammad will bog down and the UI will be slow in responsiveness. Checking the “monitoring” menu option, we notice " * scheduler may not run (last execution of OnlineNotification.cleanup about 3 hours over) - please contact your system administrator".
We can use the CLI to initiate processing of these but I would assume it would do it’s on own, i.e. manage its workload without human intervention.
We monitor the hosting system and there are plenty of system resources, i.e. CPU, memory, etc. The system is hosted on 3 AWS EC2 instances, one for Zammad, another for Postgress, and another for Elastic search. All with very large systems, i.e. multicore and lots of memory.
Are there tuning parameters or could you explain how the schedular works and why we see this when we have a good load of users creating tickets on the system?