I have managed to set up a Zammad instance in Azure (Container App environment), using the Zammad docker-compose setup more or less as it is. Zammad is fully functional (login, search, email channels, etc.). Unfortunately, I have been struggling with a problem for the past three weeks, the cause of which I do not fully understand.
The search only works occasionally. In other words, when entering a search parameter multiple times (advanced or normal search), a correct search result is returned, and no errors are displayed in the logs from the ‘Railserver’. The same behavior is observed when displaying the statistics. However, I am about 90% sure that the cause of the error is the same.
Most of the time, an empty result is returned (the error is probably handled with 200 OK during the search). I have attached a few screenshots to better visualize this issue. Searching for the same term yields results once and not at another time. Additionally, I have included a screenshot of the Rails server log when no search results were found.
Suche funktioniert:
Oder manchmal auch nicht:
Railserver Log:
I can rule out that it is related to Elasticsearch. Calls via Curl with the same request parameters always deterministically return a search result that matches the result from Zammad, when the search does work.
I had a similar problem with the login and general communication with the Railserver through Nginx. The cause was likely related to the ingress that is placed in front of each container app in Azure. At that time, it helped to set the Connection header to empty in the Nginx configuration, as otherwise the ingress would append a Closed, which in turn caused Nginx to terminate the connection (proxy_set_header Connection "";). I suspect a similar issue here as well. The connection is being terminated prematurely. However, I am not certain. Has such a problem been observed during development, or does anyone have any idea what the cause might be?
- Zammad image version: zammad:6.3.1-95
- Elasticsearch image version: bitnami/elasticsearch:8.12.2
- Used Zammad installation type: docker-compose setup adapted for azure container app environment
- Browser + version: The problem ist definitiv not browser specific
Expected behavior:
- The search always works correctly without any error messages in the log.
Actual behavior:
- The search and the display of statistics only work occasionally.
- Sometimes <UserAgent::Result:0x0000739e0dde5a20 @success=false, @body=nil, @data=nil, @code=0, @content_type=nil, @error=“#<EOFError: end of file reached>”, @header=nil> occurs