Can' rebuild elasticsearch index

FrankB · April 17, 2024, 5:08pm

Infos:

Used Zammad version: 6.3
Used Zammad installation type: source
Operating system: Ubuntu
Browser + version: 20.04.6 LTS

Expected behavior:

Rebuild of ElasticSearch-Indices

Actual behavior:

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
rake aborted!
Unable to process GET request to elasticsearch URL ‘[https]://localhost:9200’. Check the response and payload for detailed information:

([https] was modified by me cause of no links in topics)

Response:
#<UserAgent::Result:0x00007f1947f98208 @success=false, @body=nil, @data=nil, @code=0, @content_type=nil, @error=“#<OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 peeraddr=127.0.0.1:9200 state=error: wrong version number>”, @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 ’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:281:in block in execute' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:281:in each’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:281:in execute' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:219:in block in invoke_with_call_chain’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:199:in synchronize' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:199:in invoke_with_call_chain’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:243:in block in invoke_prerequisites' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:241:in each’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:241:in invoke_prerequisites' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:218:in block in invoke_with_call_chain’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:199:in synchronize' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:199:in invoke_with_call_chain’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/task.rb:188:in invoke' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/application.rb:182:in invoke_task’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/application.rb:138:in block (2 levels) in top_level' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/application.rb:138:in each’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/application.rb:138:in block in top_level' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/application.rb:147:in run_with_threads’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/application.rb:132:in top_level' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/application.rb:83:in block in run’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/application.rb:208:in standard_exception_handling' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/lib/rake/application.rb:80:in run’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/exe/rake:27:in <top (required)>' /opt/zammad/vendor/bundle/ruby/3.2.0/bin/rake:25:in load’
/opt/zammad/vendor/bundle/ruby/3.2.0/bin/rake:25:in <top (required)>' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/lib/bundler/cli/exec.rb:58:in load’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/lib/bundler/cli/exec.rb:58:in kernel_load' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/lib/bundler/cli/exec.rb:23:in run’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/lib/bundler/cli.rb:492:in exec' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor/command.rb:28:in run’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in invoke_command' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor.rb:527:in dispatch’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/lib/bundler/cli.rb:34:in dispatch' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor/base.rb:584:in start’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/lib/bundler/cli.rb:28:in start' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/exe/bundle:37:in block in <top (required)>’
/opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/lib/bundler/friendly_errors.rb:117:in with_friendly_errors' /opt/zammad/vendor/bundle/ruby/3.2.0/gems/bundler-2.4.22/exe/bundle:29:in <top (required)>’
/opt/zammad/bin/bundle:121:in load' /opt/zammad/bin/bundle:121:in ’
Tasks: TOP => zammad:searchindex:rebuild => zammad:searchindex:version_supported

Steps to reproduce the behavior:

zammad run rake zammad:searchindex:rebuild

Currently ElasticSearch does not work anymore.
Tried this: /opt/zammad/contrib/packager.io/postinstall.sh
but without any effort.

The only hint i found was “SSLError: SSL_connect returned=1” and “wrong version found” in the response string.

My Zammad-site is still working with a certificate, does elasticsearch need it again?
How to put it in?

Any hints appreciated.

Regards
Frank

MrGeneration · April 17, 2024, 8:11pm

What Elasticsearch version are you using? Quite an important piece of information if you have issues with ES.

FrankB · April 18, 2024, 6:18am

elasticsearch/stable,now 7.17.20 amd64 [installed]
zammad/unknown,now 6.3.0-1713332260.1e2f95d3.focal amd64 [installed]

just updated as the complete Ubuntu-Server and Zammd via apt upgrade

tschaefer · April 18, 2024, 7:01am

Hi @FrankB,

the OpensSSL error message is misleading. Your ES server does not serve via HTTPS.

MrGeneration · April 18, 2024, 7:40am

Your issue is caused by a documentation bug:

run rails r "Setting.set('es_url', 'http://localhost:9200') and you’ll be fine.

FrankB · April 18, 2024, 9:02am

sorry, i’m not allowed to answer with urls

how to mask an URL in a post, so that i can do a reply?

MrGeneration · April 18, 2024, 9:09am

You now have permission to. New users are not allowed because… spammer bots love to post URLs.

FrankB · April 18, 2024, 9:10am

ok done (i have to edit all URLs in this post, cause real ones are forbidden)
in /etc/elasticsearch/elasticsearch.yml the ip and http-ports are commented out

sudo service elasticsearch restart

verified, its working on http
curl -XGET ‘http://localhost:9200’
{
“name” : “zammad”,
“cluster_name” : “elasticsearch”,
“cluster_uuid” : “yCgxm95uR4-uIIihzHGm0Q”,
“version” : {
“number” : “7.17.20”,
“build_flavor” : “default”,
“build_type” : “deb”,
“build_hash” : “b26557f585b7d95c71a5549e571a6bcd2667697d”,
“build_date” : “2024-04-08T08:34:31.070382898Z”,
“build_snapshot” : false,
“lucene_version” : “8.11.3”,
“minimum_wire_compatibility_version” : “6.8.0”,
“minimum_index_compatibility_version” : “6.0.0-beta1”
},
“tagline” : “You Know, for Search”
}

on https is nothing, (thats what we want)
curl -XGET ‘https://localhost:9200’
curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number

but why is this still looking for https?
zammad run rake zammad:searchindex:rebuild
rake aborted!
Unable to process GET request to elasticsearch URL ‘https://localhost:9200’. Check the response and payload for detailed information

the post-install-script has written some advices, one is with https:
/opt/zammad/contrib/packager.io/postinstall.sh

	# Enforcing Redis…
	# Creating Redis bootstart
	Synchronizing state of redis-server.service with SysV service script with /lib/systemd/systemd-sysv-install.
	Executing: /lib/systemd/systemd-sysv-install enable redis-server
	# Starting Redis server
	# Redis server is running.
	# (Re)creating init scripts
	Nothing to do.
	Nothing to do.
	Nothing to do.
	# Enabling Zammad on boot
	# Stopping Zammad
	# Clear cache…
	# database.yml found. Updating db…
	# Updating translations…
	# No custom packages detected…
	# Configuring Elasticsearch…
	→ removing [ingest-attachment]…
	→ Installing ingest-attachment
	→ Downloading ingest-attachment from elastic
	[=================================================] 100%
	@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
	@ WARNING: plugin requires additional permissions @
	@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
	* java.lang.RuntimePermission accessClassInPackage.sun.java2d.cmm.kcms
	* java.lang.RuntimePermission accessDeclaredMembers
	* java.lang.RuntimePermission getClassLoader
	* java.lang.reflect.ReflectPermission suppressAccessChecks
	* java.security.SecurityPermission createAccessControlContext
	See Permissions in the JDK
	for descriptions of what these permissions allow and the associated risks.

	→ Installed ingest-attachment
	→ Please restart Elasticsearch to activate any plugins installed

	**It seems you’re running an external Elasticsearch server on https://localhost:9200

	We’ll not touch your Elasticsearch on the local and remote system.

	Please get sure to install the ‘ingest-attachment’ plugin on your Elasticsearch server by:
	/usr/share/elasticsearch/bin/elasticsearch-plugin -s install ingest-attachment

	After this you might need to rebuild the searchindex by:
	zammad run rake zammad:searchindex:rebuild
	# Enforcing 0600 on database.yml …
	# Starting Zammad
	# Creating webserver bootstart
	Synchronizing state of nginx.service with SysV service script with /lib/systemd/systemd-sysv-install.
	Executing: /lib/systemd/systemd-sysv-install enable nginx
	# Restarting webserver nginx
	####################################################################################

	Add your fully qualified domain name or public IP to servername directive of
	nginx, if this installation is done on a remote server. You have to change:
	/etc/nginx/sites-available/zammad.conf and restart nginx process.
	Otherwise just open http://localhost/ in your browser to start using Zammad.

	####################################################################################

do i have to edit something else for that rake-command?

MrGeneration · April 18, 2024, 9:16am

You’re mixing topics.
You show curls not a rebuild try.

If you’re just run my command I provided, a rebuild should be possible if that’s what you want to do. I can’t follow sorry.

FrankB · April 18, 2024, 9:39am

Sorry,
curl was used only for verifying

next try:
first (again)
zammad run rails r “Setting.set(‘es_url’, ‘http://localhost:9200’)”
than
zammad run rake zammad:searchindex:rebuild
Dropping indexes… done.
Deleting pipeline… done.
Creating indexes… done.
Creating pipeline… done.
Reloading data…

Chat::Session…
done in 0 seconds.
Cti::Log…
done in 0 seconds.
Group…
done in 0 seconds.
KnowledgeBase::Answer::Translation…
done in 2 seconds.
KnowledgeBase::Category::Translation…
done in 0 seconds.
KnowledgeBase::Translation…
done in 0 seconds.
Organization…
done in 1 seconds.
StatsStore…
done in 1 seconds.
Ticket::Priority…
done in 0 seconds.
Ticket::State…
done in 0 seconds.
Ticket…
done in 317 seconds.
User…
done in 16 seconds.

Now it seem to work again.
The Zammad search finds tickets and contacts again.

GREAT and MANY THANKS,
as we say in Germany: you rescued my head

system · April 25, 2024, 9:39am

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

Can' rebuild elasticsearch index

Infos:

Expected behavior:

Actual behavior:

zammad run rake zammad:searchindex:rebuild --trace

Steps to reproduce the behavior: