Infos:
- Used Zammad version: 5.2.3
- Used Zammad installation type: Source
- Operating system: Ubuntu
- Browser + version: All(Chrome Version 114.0.5735.134 (Official Build) (64-bit))
Expected behavior:
- Email sent to Zammad is received and indexed, then it shows up in the queue.
Actual behavior:
- The email is received but does not show up anywhere in the system.
When i check the productions logs i see the below error.
#<UserAgent::Result:0x00007f848391a050 @success=false, @body=“{"error":{"root_cause":[{"type":"query_shard_exception","reason":"Failed to parse query [C/Stevens*]","index_uuid":"_lkHjyMWS7GBnb5A7JNIVw","index":"zammad_production_organization"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"zammad_production_organization","node":"bAZJd7eHQC2cOmokRW3cIQ","reason":{"type":"query_shard_exception","reason":"Failed to parse query [C/Stevens*]","index_uuid":"_lkHjyMWS7GBnb5A7JNIVw","index":"zammad_production_organization","caused_by":{"type":"parse_exception","reason":"Cannot parse ‘C/Stevens*’: Lexical error at line 1, column 11. Encountered: after : [\"/Stevens*\"","caused_by":{"type":"token_mgr_error","reason":"Lexical](file:///%22/Stevens*/%22/%22,/%22caused_by/%22:%7b/%22type/%22:/%22token_mgr_error/%22,/%22reason/%22:/%22Lexical) error at line 1, column 11. Encountered: after : [\"/Stevens*\""}}}}]},"status":400](file:///%22/Stevens*/%22/%22%7d%7d%7d%7d%5d%7d,/%22status/%22:400)}”, @data=nil, @code=“400”, @content_type=nil, @error=“Client Error: #<Net::HTTPBadRequest 400 Bad Request readbody=true>!”, @header={“x-elastic-product”=>“Elasticsearch”, “warning”=>“299 Elasticsearch-7.17.6-f65e9d338dc1d07b642e14a27f338990148ee5b6 "Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone. See Set up minimal security for Elasticsearch | Elasticsearch Guide [7.17] | Elastic to enable security."”, “content-type”=>“application/json; charset=UTF-8”, “content-length”=>“390”}>
Steps to reproduce the behavior:
- Send a specific email to the system, i cannot add that here for privacy reasons.But you can see the error its throws above.
I am running Elasticsearch 7.17, I plan to upgrade to 8.8, but this is a shot in the dark and i cannot guarantee it fixes the issue.