Used Zammad version: 2.6.x
Installation method (source, package, …): package
Operating system: Debian 9.5
Database + version: mysqld 10.1.26-MariaDB-0+deb9u1
Elasticsearch version: 5.6.10
Browser + version: Independent from browser
Expected behavior:
Search output is displayed (Searchs Tickets, Companies etc.)
Actual behavior:
Every search in Zammad that uses Elasticsearch displays: StatusCode: 500
Steps to reproduce the behavior:
Search
Yes I’m sure this is a bug and no feature request or a general question.
System was rebooted, all services restarted.
The max_allowed_packet-warning is added to every elasticsearch query, so the elasticsearch URL is broken. The max_allowed_packet is actually 128M, the maximum mailsize in Zammad 64MB. Fetching mails works fine.
+++
This is production.log output, where you can see that the URL sent to Elasticsearch contains the error that max_allowed_packet is too low - which is not the case.
http://127.0.0.1:9200/zammad_production/User/_search"
E, [2018-08-14T06:51:00.572197 #959] ERROR – : bad URI(is not URI?): Warning: Database config value ‘max_allowed_packet’ less than Zammad setting ‘Maximum Email Size’
Zammad will fail to process emails (both incoming and outgoing)
larger than the value of ‘max_allowed_packet’ (64MB).
Please increase this value in your MariaDB configuration accordingly.
Warning: Database config value ‘max_allowed_packet’ less than Zammad setting ‘Maximum Email Size’
Zammad will fail to process emails (both incoming and outgoing)
+++
Health says:
181 failing background jobs.
Failed to run background job #1 ‘BackgroundJobSearchIndex’ 10 time(s) with 180 attempt(s).
+++
Github Issue which leads here: