- Used Zammad version: 3.3.0
- Used Zammad installation source: source inside a self built docker image
- Operating system: ubuntu 20.04 (but zammad is running in docker)
- Browser + version: -
- Agents can work simultaneously without problems.
- When a certain amount of agents are connected to zammad, zammad hangs trying to open tickets, send tickets, look up tickets etc.
we are currently running a modified version of the following repo:
We modified it because we are using AWS RDS Postgres as our database for zammad, hence we needed to make a few adjustments to the images inside the above mentioned repository.
So our setup looks like this:
- RDS Postgres (db.t3.medium -> 1 core 4GB RAM)
- EC2 Instance (c5.4xlarge -> 16 cores 32 GB Ram)
- AWS LoadBalancer which forwards requests on our domain to the nginx container on the EC2 instance
On the EC2 Instance we have the zammad-railsserver, zammad-scheduler, nginx, elasticsearch, memcached and the zammad-websocket-server all in a separate docker container.
Moving the EC2 instance up from 8 cores to 16 cores did not help with our problem that zammad keeps hanging occasionally when a certain threshold of simultaneously connected agents is reached. The EC2 instance does not seem to be sweating all that much. The RAM usage is constantly rising though, so we occasionally have to restart the zammad-scheduler. The RDS instance is also not really overused. CPU Usage is at most at 20%.
What I did notice on the ec2-instance is that the puma process is usually above 100% CPU usage, when zammad keeps hanging.
We currently have 330K tickets in the system. We have six email accounts connected and over 50 filters. We also have over 50 groups and a couple of overviews. We are also using the ldap integration.
From what I understand it’s currently not possible to run several instances of the zammad railsserver is this correct?
Do you guys have any suggestions how we can debug this issue further?