Reporting -all- error

Infos:

  • Used Zammad version: 5.2.3
  • Used Zammad installation type: source
  • Operating system: debian 11.5
  • Browser + version: chrome 108.0.5359.125/edge/firefox
  • elasticsearch/stable,now 7.17.7

Actual behavior:

*Click “reporting-all” will be displayed as follows Error

============================================

StatusCode: 500

Unable to process GET request to elasticsearch URL 'http://localhost:9200/zammad_production_ticket/_search'. Check the response and payload for detailed information:

Response:
#<UserAgent::Result:0x00007f67e169e7e0 @success=false, @body="{\"error\":{\"root_cause\":[{\"type\":\"x_content_parse_exception\",\"reason\":\"[1:51] [bool] failed to parse field [must]\"}],\"type\":\"x_content_parse_exception\",\"reason\":\"[1:51] [bool] failed to parse field [must]\",\"caused_by\":{\"type\":\"illegal_argument_exception\",\"reason\":\"field name is null or empty\"}},\"status\":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.7-78dcaaa8cee33438b91eca7f5c7f56a70fec9e80 \"Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone. See https://www.elastic.co/guide/en/elasticsearch/reference/7.17/security-minimal-setup.html to enable security.\"", "content-type"=>"application/json; charset=UTF-8", "content-length"=>"182"}>

Payload:
{"query":{"bool":{"must":[{"term":{"state_id":null}},{"range":{"created_at":{"from":"2021-12-31T16:00:00Z","to":"2022-12-31T15:59:59Z"}}}],"must_not":[{"term":{"state.name.keyword":"merged"}}]}},"size":0,"aggs":{"time_buckets":{"date_histogram":{"field":"created_at","calendar_interval":"month","time_zone":"Asia/Shanghai"}}},"sort":[{"updated_at":{"order":"desc"}},"_score"]}

Payload size: 0M

============================================

HELLO Teams
What is the problem?

[bool] failed to parse field

That’s the issue you’re dealing with.
Usually happens if you add a new object with existing tickets or (which would be worse) if you remove an attribute and re-add another type with the exact same name due to the old data still being present.

A reindex might solve the issue already.

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