Quantcast
Channel: Zammad - Community - Latest posts
Viewing all articles
Browse latest Browse all 6862

Can' rebuild elasticsearch index

$
0
0

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?


Viewing all articles
Browse latest Browse all 6862

Trending Articles