OpenSearch is up and available. But if I try to have Zammad talk to OpenSearch, Zammad aborts:
$ zammad run rake zammad:searchindex:rebuild
rake aborted!
Unable to process GET request to elasticsearch URL 'http://localhost:9200'. Check the response and payload for detailed information:
Response:
#<UserAgent::Result:0x00007f32ac69ff10 @success=false, @body=nil, @data=nil, @code=0, @content_type=nil, @error="#<EOFError: end of file reached>", @header=nil>
Payload:
null
Payload size: 0M
/opt/zammad/lib/search_index_backend.rb:36:in `info'
/opt/zammad/lib/tasks/zammad/search_index_es.rake:64:in `block (3 levels) in <main>'
/opt/zammad/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/opt/zammad/bin/bundle:121:in `load'
/opt/zammad/bin/bundle:121:in `<main>'
Tasks: TOP => zammad:searchindex:rebuild => zammad:searchindex:version_supported
(See full trace by running task with --trace)
So, is anybody running Zammad version 6 with OpenSearch? What did you have to do?
OpenSearch is made to be compatible with ElasticSearch. It works perfectly fine after setting compatibility.override_main_response_version: true
With this setting, OpenSearch reports the version number as it would be ES.
Also mentioned here:
This is an interesting observation because we had it running with Zammad 5 and now it works with Zammad 6. What did you find in your analysis?
If the version check failed, the error message would be different, but yours is:
Unable to process GET request to elasticsearch URL 'http://localhost:9200'
...
@body=nil, @data=nil, @code=0 ... @error="#<EOFError: end of file reached>", @header=nil>
All that suggests an empty response and that puzzles me. Are username/password in OpenSearch and Zammad set correctly (the same)?
What is the result of curl -X GET https://localhost:9200 -u '$user:$pass' --insecure (fill in the configured username/password combination, standard is admin/admin)?
For me on a working installation the result of the request is
Make sure you are talking the right protocol. I think the .deb package published by OpenSearch (not sure if this is the default everywhere) talks https out of :9200, but by default Zammad expects http.