- Used Zammad version: 5.01
- Used Zammad installation type: (source, package, docker-compose, …) docker-compose
- Operating system: Ubuntu
- Browser + version: Chrome
Does anyone know where to go to shutdown the UserDeviceJobLog?
Job does not seem to have a real practical use case for generating thousands of jobs a minute.
This is causing major issues with other jobs as they do not process through such as elastic - it takes over 2 days for index jobs to index leading to user frustration.
- Low priority jobs are given a low priority to not impact usability of the system.
- Jobs are extremely backlogged.
Steps to reproduce the behavior:
No offense, but you really should ensure that your system suits Zammads hardware recommendations:
Performance tuning may be a relevant section for you as well.
And yes that’s a thing for docker compose: Docker Compose Environment Variables — Zammad documentation
Please don’t try to solve issues by disabling scheduler tasks randomly. If they’re not needed they wouldn’t be in the system.
Thanks - appreciate the reply. I actually found the root cause. On the official helm chart, nginx conf does not properly set the real user ip and uses the node ip resulting in a change in IP per request which generations hundreds of thousands of device job logs per hour.
We resolved the issue by updating the nginx conf map to use the proxy real ip.
Please consider contributing to the orignal chart upstream if you believe this is a enhancement that everyone should benefit from.
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.