Since updating to 5.0.3 -> Status Code 500 | Internal Server Error

Hi everyone,

Since the update to Zammad 5.X from version 4, we have constantly had failures and error messages in Zammad (Status Code 500 | Internal Server Error). Changes to the tickets are then not possible in Status and we have recently been unable to create new tickets because no owners can be selected.

I found the following errors in the production.log:
I hope you can help.

E, [2022-01-05T14: 02: 54.760904 # 5724-4720] ERROR -: Error performing core workflow engine.
E, [2022-01-05T14: 02: 54.760948 # 5724-4720] ERROR -: FATAL: remaining connection slots are reserved for non-replication superuser connections

  • Used Zammad version: 5.0.3
  • Used Zammad installation type: package
  • Operating system: Ubuntu 20.04
  • Browser + version: Chrome, Firefox

Expected behavior:

Actual behavior:

Steps to reproduce the behavior:

No changes are possible in the right window. we then have to discard the changes and restart zammad. That only helps for a short time

Changes in the “main window” are possible. We can reply to tickets and also take notes. Full text search via Elasticsearch also works.

Update 3
the self-created objects all have the same position!? This numbering is new to me.


I was able to solve the problem myself. I increased the max_connections value from 100 to 2.000 in the postgres sql configuration file. since then no more crashes and errors

Please use the official documentation instead and not my personal playgrounds.
Information on the official documentation can always be expected to be most current, other sources may not be up to date for whatever reason.

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