Closed Fernien closed 7 months ago
@Fernien thanks for your report. If you want to use Zammad 6.4.x, you need to include the changes from #402 in your deployment. Specifically the POSTGRESQL_OPTIONS
with the explicit setting of the database pool size. Please let us know if it works for you.
I'm closing this issue as it is not about a supported Zammad version.
@Fernien thanks for your report. If you want to use Zammad 6.4.x, you need to include the changes from #402 in your deployment. Specifically the
POSTGRESQL_OPTIONS
with the explicit setting of the database pool size. Please let us know if it works for you.I'm closing this issue as it is not about a supported Zammad version.
It seems to have solved the prolems. Thanks for the quick help and sorry for the inconvenience
Infos
Expected behavior
Actual behavior
Steps to reproduce the behavior
I'm not completely sure how to reproduce it since the fetching just stops working seemingly randomly. The log errors are after a fresh installation
I added vm.max_map_count=262144 to sysctl.conf. I have the same problem on 2 different host systems with 2 different zammad installations. Zammad Version 6.4.x