Searchindex:rebuild fails on 3.2.0

Hello,
we work with a source Zammad 3.2.0 update from 3.1.0 , Debian 9.9 and elasticsearch 7.5.1
now we get the following error with “rake searchindex:rebuild”

drop indexes…done
delete pipeline (pipeline)… done
create indexes…done
create pipeline (pipeline)… done
reload data…
reload Cti::Log

Response:
#<UserAgent::Result:0x000056482ba7d040 @success=false, @body="{“error”:{“root_cause”:[{“type”:“illegal_argument_exception”,“reason”:“field [article] not present as part of path [article]”}],“type”:“illegal_argument_exception”,“reason”:“field [article] not present as part of path [article]”},“status”:400}", @data=nil, @code=“400”, @content_type=nil, @error=“Client Error: #<Net::HTTPBadRequest 400 Bad Request readbody=true>!”>

Payload:
{“id”=>9482, “direction”=>“in”, “state”=>“hangup”, “from”=>“022266835”, “from_comment”=>nil, “to”=>“queue-660”, “to_comment”=>“Local/241@only-dialextension-q660”, “queue”=>“queue-660”, “call_id”=>“1578305487.1133”, “comment”=>“normalClearing”, “initialized_at”=>Mon, 06 Jan 2020 10:12:20 UTC +00:00, “start_at”=>Mon, 06 Jan 2020 10:17:39 UTC +00:00, “end_at”=>Mon, 06 Jan 2020 10:19:37 UTC +00:00, “duration_waiting_time”=>319, “duration_talking_time”=>118, “done”=>true, “preferences”=>{}, “created_at”=>Mon, 06 Jan 2020 10:12:20 UTC +00:00, “updated_at”=>Mon, 06 Jan 2020 10:19:37 UTC +00:00, “from_pretty”=>“022266835”, “to_pretty”=>“660”}

Payload size: 0M>
/opt/zammad/app/models/concerns/has_search_index_backend.rb:145:in rescue in block in search_index_reload' /opt/zammad/app/models/concerns/has_search_index_backend.rb:139:inblock in search_index_reload’
/opt/zammad/app/models/concerns/has_search_index_backend.rb:134:in each' /opt/zammad/app/models/concerns/has_search_index_backend.rb:134:insearch_index_reload’
/opt/zammad/lib/tasks/search_index_es.rake:143:in block (3 levels) in <main>' /opt/zammad/lib/tasks/search_index_es.rake:139:ineach’
/opt/zammad/lib/tasks/search_index_es.rake:139:in block (2 levels) in <main>' /opt/zammad/lib/tasks/search_index_es.rake:159:inblock (2 levels) in ’
/opt/zammad/.rvm/gems/ruby-2.5.5/gems/rake-12.3.2/exe/rake:27:in <top (required)>' /opt/zammad/.rvm/gems/ruby-2.5.5/bin/ruby_executable_hooks:24:ineval’
/opt/zammad/.rvm/gems/ruby-2.5.5/bin/ruby_executable_hooks:24:in `’

downgrade to elasticsearch 7.4.2 fixed the problem

1 Like

Or you update your Zammad to the latest available version, as this as been addressed already. :slight_smile:

Hi,
we had updated to 3.2 on 06.01.2020
is there a newer version?

Last successfully package built is from 20th December 2019.
The fix has been applied on 04th December 2019 and thus should be available in your installation as well.

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