58 failing background jobs

  • Used Zammad version: 6.2.0-1705920690.db7738e0.focal
  • Used Zammad installation type: (source, package, docker-compose, …) source
  • Operating system: debian
  • Browser + version: NA

Expected behavior:

  • 0 issues on monitor

Actual behavior:

  • These issues appear

    58 failing background jobs
    Failed to run background job #1 ‘SearchIndexAssociationsJob’ 5 time(s) with 88 attempt(s).
    Failed to run background job #2 ‘SearchIndexJob’ 5 time(s) with 88 attempt(s).

I tried solving by executing zammad run rake zammad:searchindex:rebuild, but no. I get this with --trace:

zammad run rake zammad:searchindex:rebuild --trace
** Invoke zammad:searchindex:rebuild (first_time)
** Invoke zammad:searchindex:version_supported (first_time)
** Invoke zammad:searchindex:configured (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute zammad:searchindex:configured
** Execute zammad:searchindex:version_supported
** Execute zammad:searchindex:rebuild
** Execute zammad:searchindex:drop
Dropping indexes… done.
** Execute zammad:searchindex:drop_pipeline
Deleting pipeline… done.
** Execute zammad:searchindex:create
Creating indexes… done.
** Execute zammad:searchindex:create_pipeline
Creating pipeline… rake aborted!
Unable to process put request to elasticsearch URL ‘http://localhost:9200/_ingest/pipeline/zammad2f51f22d-81b6-43eb-87a4-2018c63ff287’. Check the response and payload for detailed information:

Response:
#<UserAgent::Result:0x00007fc84d022610 @success=false, @body=“{"error":{"root_cause":[{"type":"parse_exception","reason":"No processor type exists with name [attachment]","processor_type":"foreach","suppressed":[{"type":"parse_exception","reason":"No processor type exists with name [attachment]","processor_type":"foreach"}]}],"type":"parse_exception","reason":"No processor type exists with name [attachment]","processor_type":"foreach","suppressed":[{"type":"parse_exception","reason":"No processor type exists with name [attachment]","processor_type":"foreach"}]},"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.17-aba4da413a368e296dfc64fb20897334d0340aa1 "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”=>“519”}>

Payload:
{“description”:“Extract zammad-attachment information from arrays”,“processors”:[{“foreach”:{“field”:“article”,“processor”:{“foreach”:{“field”:“_ingest._value.attachment”,“processor”:{“attachment”:{“target_field”:“_ingest._value”,“field”:“_ingest._value._content”,“ignore_failure”:true,“ignore_missing”:true}},“ignore_failure”:true,“ignore_missing”:true}},“ignore_failure”:true,“ignore_missing”:true}},{“foreach”:{“field”:“attachment”,“processor”:{“attachment”:{“target_field”:“_ingest._value”,“field”:“_ingest._value._content”,“ignore_failure”:true,“ignore_missing”:true}},“ignore_failure”:true,“ignore_missing”:true}}]}

Payload size: 0M
/opt/zammad/lib/search_index_backend.rb:744:in make_request_and_validate' /opt/zammad/lib/search_index_backend.rb:88:in block (2 levels) in processors’
/opt/zammad/lib/search_index_backend.rb:72:in each' /opt/zammad/lib/search_index_backend.rb:72:in block in processors’
/opt/zammad/lib/search_index_backend.rb:69:in each' /opt/zammad/lib/search_index_backend.rb:69:in processors’
/opt/zammad/lib/search_index_backend.rb:934:in create_pipeline' /opt/zammad/lib/tasks/zammad/search_index_es.rake:25:in block (3 levels) in ’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in block in execute' /opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in each’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in execute' /opt/zammad/lib/tasks/zammad/search_index_es.rake:19:in block (3 levels) in ’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in block in execute' /opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in each’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in execute' /opt/zammad/lib/tasks/zammad/search_index_es.rake:59:in block (3 levels) in ’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in block in execute' /opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in each’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in execute' /opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:219:in block in invoke_with_call_chain’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:199:in synchronize' /opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:199:in invoke_with_call_chain’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:188:in invoke' /opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/application.rb:160:in invoke_task’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/application.rb:116:in block (2 levels) in top_level' /opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/application.rb:116:in each’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/application.rb:116:in block in top_level' /opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/application.rb:125:in run_with_threads’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/application.rb:110:in top_level' /opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/application.rb:83:in block in run’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/application.rb:186:in standard_exception_handling' /opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/lib/rake/application.rb:80:in run’
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/exe/rake:27:in <top (required)>' /opt/zammad/vendor/bundle/ruby/3.1.0/bin/rake:25:in load’
/opt/zammad/vendor/bundle/ruby/3.1.0/bin/rake:25:in <top (required)>' /opt/zammad/vendor/ruby-3.1.3/lib/ruby/3.1.0/bundler/cli/exec.rb:58:in load’
/opt/zammad/vendor/ruby-3.1.3/lib/ruby/3.1.0/bundler/cli/exec.rb:58:in kernel_load' /opt/zammad/vendor/ruby-3.1.3/lib/ruby/3.1.0/bundler/cli/exec.rb:23:in run’
/opt/zammad/vendor/ruby-3.1.3/lib/ruby/3.1.0/bundler/cli.rb:486:in exec' /opt/zammad/vendor/ruby-3.1.3/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor/command.rb:27:in run’
/opt/zammad/vendor/ruby-3.1.3/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor/invocation.rb:127:in invoke_command' /opt/zammad/vendor/ruby-3.1.3/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor.rb:392:in dispatch’
/opt/zammad/vendor/ruby-3.1.3/lib/ruby/3.1.0/bundler/cli.rb:31:in dispatch' /opt/zammad/vendor/ruby-3.1.3/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor/base.rb:485:in start’
/opt/zammad/vendor/ruby-3.1.3/lib/ruby/3.1.0/bundler/cli.rb:25:in start' /opt/zammad/vendor/ruby-3.1.3/lib/ruby/gems/3.1.0/gems/bundler-2.3.26/libexec/bundle:48:in block in <top (required)>’
/opt/zammad/vendor/ruby-3.1.3/lib/ruby/3.1.0/bundler/friendly_errors.rb:120:in with_friendly_errors' /opt/zammad/vendor/ruby-3.1.3/lib/ruby/gems/3.1.0/gems/bundler-2.3.26/libexec/bundle:36:in <top (required)>’
/opt/zammad/bin/bundle:121:in load' /opt/zammad/bin/bundle:121:in
Tasks: TOP => zammad:searchindex:rebuild

Now I can’t get results from searches. Tried restarting elasticsearch but nothing. Please help!!!

Read and follow the documentation, please:
https://docs.zammad.org/en/latest/install/elasticsearch.html

Hi, thank you for your answer. Unfortunately, I’ve read it and did everything, but I still get the same problem. Could I have a bit more of orientation, please?

You’re installation is missing the ingest-attachment plugin for Elasticsearch.

I just got the same issue, been running it fine for little less than a year. Installing ingest-attachment again fixed it. Any idea why that may have been removed? Could be a peculiarity of AlmaLinux 8 I suppose