- Used Zammad version: 3.3.0
- Used Zammad installation source: RPM
some of our agents report a generic Error ID (“error ID xxxxyyyy: please contact your administrator”) updating a ticket or creating a new ticket (Error 422 in the console). The error occurs more often in “long-thread” tickets. The same agents when the system does not give them this error, report an extreme slowness in updating tickets.
We tried to put
proxy_set_header X-Forwarded-Ssl on;
in zammad.conf file but the error persists.
Our postgresql configuration are:
max_connections = 1500
shared_buffers = 1GB
temp_buffers = 256MB
work_mem = 10MB
max_stack_depth = 5MB
Analyzing the log file we have this error:
E, [2020-10-16T14:46:03.735200 #7420-70231417403000] ERROR – : PG::TRDeadlockDetected: ERROR: deadlock detected
E, [2020-10-16T14:46:03.738227 #7420-70231417403000] ERROR – : Error ID Fc-NgpCP: PG::TRDeadlockDetected: ERROR: deadlock detected
What would you advise me to indagate?