Unable to process PUT at http://localhost:9200/_ingest/pipeline/zammad-attachment

[antboll]

Infos:

• Used Zammad version: 2.2
• Used Zammad installation source: (source, package, …) package centos
• Operating system: CENT OS
• Elasicseach 5.6.5 with mapper plugin
• Browser + version: cli

Expected behavior:

• Index build

Actual behavior:

Search index will not be build, search tickets or customers does not work, Statsitic does not work.
Behavior after reboot of the server.
Elasticsearch was working in past, after reboot we cant search for Tickes or customers. So we tried to rebuild the index. Elasticsearch and mapper plugins removed and installed again, did not help. Firewall ist open. Even if the firewall is disabled the behavior is the same. It doesnt matter if I Use localhost, fqdn, or, IP Adress.

Unable to process PUT at http://localhost:9200/_ingest/pipeline/zammad-attachment
#<UserAgent::Result:0x0055e4d2cb2c78 @success=false, @body=nil, @data=nil, @code=“400”, @content_type=nil, @error=“Client Error: #<Net::HTTPBadRequest 400 Bad Request readbody=true>!”>
/opt/zammad/lib/search_index_backend.rb:95:in block (2 levels) in processors' /opt/zammad/lib/search_index_backend.rb:62:in each’
/opt/zammad/lib/search_index_backend.rb:62:in block in processors' /opt/zammad/lib/search_index_backend.rb:59:in each’
/opt/zammad/lib/search_index_backend.rb:59:in processors' /opt/zammad/lib/tasks/search_index_es.rake:68:in block (2 levels) in <top (required)>’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/task.rb:251:in block in execute' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/task.rb:251:in each’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/task.rb:251:in execute' /opt/zammad/lib/tasks/search_index_es.rake:121:in block (2 levels) in <top (required)>’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/task.rb:251:in block in execute' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/task.rb:251:in each’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/task.rb:251:in execute' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/task.rb:195:in block in invoke_with_call_chain’
/opt/zammad/vendor/ruby-2.4.1/lib/ruby/2.4.0/monitor.rb:214:in mon_synchronize' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/task.rb:188:in invoke_with_call_chain’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/task.rb:181:in invoke' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/application.rb:160:in invoke_task’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/application.rb:116:in block (2 levels) in top_level' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/application.rb:116:in each’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/application.rb:116:in block in top_level' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/application.rb:125:in run_with_threads’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/application.rb:110:in top_level' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/application.rb:83:in block in run’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/application.rb:186:in standard_exception_handling' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/lib/rake/application.rb:80:in run’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.0/exe/rake:27:in <top (required)>' /opt/zammad/vendor/bundle/ruby/2.4.0/bin/rake:22:in load’
/opt/zammad/vendor/bundle/ruby/2.4.0/bin/rake:22:in <top (required)>' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:74:in load’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:74:in kernel_load' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:27:in run’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:360:in exec' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in run’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in invoke_command' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor.rb:369:in dispatch’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:20:in dispatch' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/base.rb:444:in start’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:10:in start' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/exe/bundle:35:in block in <top (required)>’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/friendly_errors.rb:121:in with_friendly_errors' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/exe/bundle:27:in <top (required)>’
/opt/zammad/bin/bundle:3:in load' /opt/zammad/bin/bundle:3:in ’
Tasks: TOP => searchindex:rebuild

Steps to reproduce the behavior:

*zammad run rake searchindex:rebuild --trace
*zammad run rake searchindex:drop --trace
*curl http://localhost:9200

{
“name” : “fthmWhb”,
“cluster_name” : “elasticsearch”,
“cluster_uuid” : “sqj3B91DT6ujXjnubp7dgw”,
“version” : {
“number” : “5.6.5”,
“build_hash” : “6a37571”,
“build_date” : “2017-12-04T07:50:10.466Z”,
“build_snapshot” : false,
“lucene_version” : “6.6.1”
},
“tagline” : “You Know, for Search”
}

Can Anyone please give us a hint?

[dvnkln]

Hey @antboll,

for Elasticsearch > 5.6.x it’s recommended to use the ingest-attachment plugin instead of the outdated mapper-attachments plugin.

Have a look at the documentation:

https://docs.zammad.org/en/latest/install-elasticsearch.html

Maybe you can give this a try?

cheers

[antboll]

Many Thanks svnr-dvnkln
it works again.
But the documentation is out of date.
In the cent os sections the mapper plugin ist named.
Thanks you very much
Problem resolved!!!