Infos:
- Used Zammad version: 3.6
- Used Zammad installation source: package
- Operating system: Centos 6
- Browser + version: not applicabale
Expected behavior:
- zammad run rake searchindex:rebuild rebuilds all indexes and restores Search function after updating zu zammad 3.6
Actual behavior:
- drop indexes…done
delete pipeline (pipeline)… done
create indexes…done
create pipeline (pipeline)… done
reload data…
reload Chat::Session- started at 2021-01-14 08:31:48 UTC
- took 0 seconds
reload Cti::Log - started at 2021-01-14 08:31:48 UTC
- took 0 seconds
reload KnowledgeBase::Answer::Translation - started at 2021-01-14 08:31:48 UTC
- took 0 seconds
reload KnowledgeBase::Category::Translation - started at 2021-01-14 08:31:48 UTC
- took 0 seconds
reload KnowledgeBase::Translation - started at 2021-01-14 08:31:48 UTC
- took 0 seconds
reload Ticket - started at 2021-01-14 08:31:48 UTC
rake aborted!
Unable to send Ticket.find(54423).search_index_update_backend backend: #<RuntimeError: Unable to process POST request to elasticsearch URL ‘http://127.0.0.1:9200/zammad_production_ticket/_doc/54423?pipeline=zammad731495648940’. Check the response and payload for detailed information:
Response:
#<UserAgent::Result:0x00005610724b86a0 @success=false, @body="{“error”:{“root_cause”:[{“type”:“cluster_block_exception”,“reason”:“blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];”}],“type”:“cluster_block_exception”,“reason”:“blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];”},“status”:403}", @data=nil, @code=“403”, @content_type=nil, @error=“Client Error: #<Net::HTTPForbidden 403 Forbidden readbody=true>!”>
Payload:
{“id”=>54423, “group_id”=>5, “priority_id”=>3, “state_id”=>3, “organization_id”=>nil, “number”=>“2019053116000529”, …
Steps to reproduce the behavior:
- zammad run rake searchindex:rebuild using root user
is there any option to skip a certain id or force option to carry on after failure?