Could someone help me to have a cluster with a main machine that has elasticsearch and kibana and other 9 machines with only elasticsearch that are slaves.
Elasticsearch doesn't have slaves.
What version are you running?
What does your config look like?
I am trying to connect another machine to the main machine but when I uncomment the line: cluster.initial_master_nodes, it does not start kibana.
# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: techbase
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# By default Elasticsearch is only accessible on localhost. Set a different
# address here to expose this node on the network:
#
network.host: 0.0.0.0
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
discovery.seed_hosts: ["192.168.10.74", "192.168.10.70"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
#cluster.initial_master_nodes: ["node-1"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# --------------------------------- Readiness ----------------------------------
#
# Enable an unauthenticated TCP readiness endpoint on localhost
#
#readiness.port: 9399
#
# ---------------------------------- Various -----------------------------------
#
# Allow wildcard deletion of indices:
#
#action.destructive_requires_name: false
#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------#
# The following settings, TLS certificates, and keys have been automatically
# generated to configure Elasticsearch security features on 22-03-2023 13:02:55
#
# --------------------------------------------------------------------------------
# Enable security features
xpack.security.enabled: true
xpack.security.enrollment.enabled: true
# Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents
xpack.security.http.ssl:
enabled: true
keystore.path: certs/http.p12
# Enable encryption and mutual authentication between cluster nodes
xpack.security.transport.ssl:
enabled: true
verification_mode: certificate
keystore.path: certs/transport.p12
truststore.path: certs/transport.p12
# Create a new cluster with the current node only
# Additional nodes can still join the cluster later
cluster.initial_master_nodes: ["techbase"]
# Allow HTTP API connections from anywhere
# Connections are encrypted and require user authentication
http.host: 0.0.0.0
# Allow other nodes to join the cluster from anywhere
# Connections are encrypted and mutually authenticated
#transport.host: 0.0.0.0
#----------------------- END SECURITY AUTO CONFIGURATION -------------------------
THE ERROR:
root@techbase:/home/techbase# journalctl -xe
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at org.elasticsearch.launcher.CliToolLauncher.main(CliTo>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: Caused by: org.elasticsearch.xcontent.XContentParseException: [1>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at [Source: (ByteArrayInputStream); line: 114, column: 29]
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at org.elasticsearch.xcontent.provider.json.JsonXContent>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at org.elasticsearch.xcontent.provider.json.JsonXContent>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at org.elasticsearch.common.settings.Settings.fromXConte>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at org.elasticsearch.common.settings.Settings.fromXConte>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at org.elasticsearch.common.settings.Settings$Builder.lo>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: ... 7 more
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: Caused by: com.fasterxml.jackson.core.JsonParseException: Duplic>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at [Source: (ByteArrayInputStream); line: 114, column: 29]
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at com.fasterxml.jackson.core.json.JsonReadContext._chec>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at com.fasterxml.jackson.core.json.JsonReadContext.setCu>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at com.fasterxml.jackson.dataformat.yaml.YAMLParser.next>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at com.fasterxml.jackson.core.JsonParser.nextFieldName(J>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: at org.elasticsearch.xcontent.provider.json.JsonXContent>
Mar 24 09:54:53 techbase systemd-entrypoint[31526]: ... 10 more
Mar 24 09:54:53 techbase systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit elasticsearch.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Mar 24 09:54:53 techbase systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit elasticsearch.service has entered the 'failed' state with result 'exit-code'.
Mar 24 09:54:54 techbase systemd[1]: Failed to start Elasticsearch.
░░ Subject: A start job for unit elasticsearch.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit elasticsearch.service has finished with a failure.
░░
░░ The job identifier is 11907 and the job result is failed.
Mar 24 09:54:54 techbase systemd[1]: elasticsearch.service: Consumed 4.820s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit elasticsearch.service completed and consumed the indicated resources.
Mar 24 09:54:54 techbase kibana[5315]: [2023-03-24T09:54:54.690+00:00][WARN ][plugins.usageCollection.usage-collecti>
Mar 24 09:54:54 techbase kibana[5315]: at KibanaTransport.request (/usr/share/kibana/node_modules/@elastic/trans>
Mar 24 09:54:54 techbase kibana[5315]: at runMicrotasks (<anonymous>)
Mar 24 09:54:54 techbase kibana[5315]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
Mar 24 09:54:54 techbase kibana[5315]: at KibanaTransport.request (/usr/share/kibana/node_modules/@kbn/core-elas>
Mar 24 09:54:54 techbase kibana[5315]: at ClientTraced.UpdateApi [as update] (/usr/share/kibana/node_modules/@el>
Mar 24 09:55:00 techbase kibana[5315]: [2023-03-24T09:55:00.405+00:00][WARN ][plugins.monitoring.monitoring.kibana-m>
Mar 24 09:55:00 techbase kibana[5315]: at KibanaTransport.request (/usr/share/kibana/node_modules/@elastic/trans>
Mar 24 09:55:00 techbase kibana[5315]: at runMicrotasks (<anonymous>)
Mar 24 09:55:00 techbase kibana[5315]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
Mar 24 09:55:00 techbase kibana[5315]: at KibanaTransport.request (/usr/share/kibana/node_modules/@kbn/core-elas>
Mar 24 09:55:00 techbase kibana[5315]: at Monitoring.bulk (/usr/share/kibana/node_modules/@elastic/elasticsearch>
Mar 24 09:55:00 techbase kibana[5315]: at sendBulkPayload (/usr/share/kibana/x-pack/plugins/monitoring/server/ki>
Mar 24 09:55:00 techbase kibana[5315]: at BulkUploader._onPayload (/usr/share/kibana/x-pack/plugins/monitoring/s>
Mar 24 09:55:00 techbase kibana[5315]: at BulkUploader._fetchAndUpload (/usr/share/kibana/x-pack/plugins/monitor>
Mar 24 09:55:00 techbase kibana[5315]: [2023-03-24T09:55:00.406+00:00][WARN ][plugins.monitoring.monitoring.kibana-m>```This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.