ElasticSearch to OpenSearch - almost working [HELP needed]

hi.

Had 4.2 Graylog.
Got it to 4.3.
MongoDB is 5.0.
I want to move now to graylog 5.0

Still, before this i need to make the switch between elasticsearch to opensearch.

at this moment i followed the tutorial form youtube plus the links on GL documentation.

I managed to:
sync all the data from ES to OS
the OpenSearch service is fully up and running, all green.
So is the ElasticSearch one…

Now, problem is that i might have skipped something of the tutorial is not showing it…

HOW to make the actual switch now?

Because in this moment if i turn off the elasticsearch service, messages stop comming in.
So i presume the switch is not actually… done.

image

this is the tutorial:

and docu:
https://go2docs.graylog.org/5-0/planning_your_deployment/opensearch_on_debian__tarball_.htm

i am a single node cinfig

image
in here i can still see the Elasticsearch version, instead of the opensearch 1.3.2

this is the opensearch yml.

root@01-log:~# cat /mnt/data1/opensearch/config/opensearch.yml
# ======================== OpenSearch Configuration =========================
#
# NOTE: OpenSearch 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.opensearch.org
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: graylog
#
# ------------------------------------ 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: /mnt/data1/elasticsearch/lib
#
# Path to log files:
#
path.logs: /mnt/data1/elasticsearch/log
#
# ----------------------------------- 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.
#
# OpenSearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: 10.xx.xx.xx 
#
# Set a custom port for HTTP:
#
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: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
#cluster.initial_master_nodes: ["node-1", "node-2"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true
discovery.type: single_node
action.auto_create_index: false
plugins.security.disabled: true

also the graylog server config file

root@nameserver--log:~# cat /mnt/data1/opensearch/config/opensearch.yml
# ======================== OpenSearch Configuration =========================
#
# NOTE: OpenSearch 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.opensearch.org
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: graylog
#
# ------------------------------------ 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: /mnt/data1/elasticsearch/lib
#
# Path to log files:
#
path.logs: /mnt/data1/elasticsearch/log
#
# ----------------------------------- 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.
#
# OpenSearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: 10.00.00.00
#
# Set a custom port for HTTP:
#
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: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
#cluster.initial_master_nodes: ["node-1", "node-2"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true
discovery.type: single_node
action.auto_create_index: false
plugins.security.disabled: true

root@nameserver--log:~# cat /etc/graylog/server/server.conf
############################
# GRAYLOG CONFIGURATION FILE
############################
#
# This is the Graylog configuration file. The file has to use ISO 8859-1/Latin-1 character encoding.
# Characters that cannot be directly represented in this encoding can be written using Unicode escapes
# as defined in https://docs.oracle.com/javase/specs/jls/se8/html/jls-3.html#jls-3.3, using the \u prefix.
# For example, \u002c.
#
# * Entries are generally expected to be a single line of the form, one of the following:
#
# propertyName=propertyValue
# propertyName:propertyValue
#
# * White space that appears between the property name and property value is ignored,
#   so the following are equivalent:
#
# name=Stephen
# name = Stephen
#
# * White space at the beginning of the line is also ignored.
#
# * Lines that start with the comment characters ! or # are ignored. Blank lines are also ignored.
#
# * The property value is generally terminated by the end of the line. White space following the
#   property value is not ignored, and is treated as part of the property value.
#
# * A property value can span several lines if each line is terminated by a backslash (‘\’) character.
#   For example:
#
# targetCities=\
#         Detroit,\
#         Chicago,\
#         Los Angeles
#
#   This is equivalent to targetCities=Detroit,Chicago,Los Angeles (white space at the beginning of lines is ignored).
#
# * The characters newline, carriage return, and tab can be inserted with characters \n, \r, and \t, respectively.
#
# * The backslash character must be escaped as a double backslash. For example:
#
# path=c:\\docs\\doc1
#

# If you are running more than one instances of Graylog server you have to select one of these
# instances as master. The master will perform some periodical tasks that non-masters won't perform.
is_master = true

# The auto-generated node ID will be stored in this file and read after restarts. It is a good idea
# to use an absolute file path here if you are starting Graylog server from init scripts or similar.
node_id_file = /etc/graylog/server/node-id

# You MUST set a secret to secure/pepper the stored user passwords here. Use at least 64 characters.
# Generate one by using for example: pwgen -N 1 -s 96
# ATTENTION: This value must be the same on all Graylog nodes in the cluster.
# Changing this value after installation will render all user sessions and encrypted values in the database invalid. (e.g. encrypted access tokens)
password_secret = EWSry5Za1mLTc8tqAQ1LfSH9SoFsMSIBxQWA2Iw2DW90MAEb1aN5QWWU4XPeichOTFcrZ9YSwsODwLXWCxAa6uuRnEHBsRod

# The default root user is named 'admin'
#root_username = admin

# You MUST specify a hash password for the root user (which you only need to initially set up the
# system and in case you lose connectivity to your authentication backend)
# This password cannot be changed using the API or via the web interface. If you need to change it,
# modify it in this file.
# Create one by using for example: echo -n yourpassword | shasum -a 256
# and put the resulting hash value into the following line
root_password_sha2 = 4e25ffcb3c28b46d424fb2942400d9334fd1d1b7bb83a604a8825c8e588c3b49

# The email address of the root user.
# Default is empty
#root_email = ""

# The time zone setting of the root user. See http://www.joda.org/joda-time/timezones.html for a list of valid time zones.
# Default is UTC
#root_timezone = UTC

# Set the bin directory here (relative or absolute)
# This directory contains binaries that are used by the Graylog server.
# Default: bin
bin_dir = /usr/share/graylog-server/bin

# Set the data directory here (relative or absolute)
# This directory is used to store Graylog server state.
# Default: data
data_dir = /var/lib/graylog-server

# Set plugin directory here (relative or absolute)
plugin_dir = /usr/share/graylog-server/plugin

###############
# HTTP settings
###############

#### HTTP bind address
#
# The network interface used by the Graylog HTTP interface.
#
# This network interface must be accessible by all Graylog nodes in the cluster and by all clients
# using the Graylog web interface.
#
# If the port is omitted, Graylog will use port 9000 by default.
#
# Default: 127.0.0.1:9000
#http_bind_address = 10.00.00.00:9000
http_bind_address = log.int.iptor.cloud:9000
#http_bind_address = [2001:db8::1]:9000

#### HTTP publish URI
#
# The HTTP URI of this Graylog node which is used to communicate with the other Graylog nodes in the cluster and by all
# clients using the Graylog web interface.
#
# The URI will be published in the cluster discovery APIs, so that other Graylog nodes will be able to find and connect to this Graylog node.
#
# This configuration setting has to be used if this Graylog node is available on another network interface than $http_bind_address,
# for example if the machine has multiple network interfaces or is behind a NAT gateway.
#
# If $http_bind_address contains a wildcard IPv4 address (0.0.0.0), the first non-loopback IPv4 address of this machine will be used.
# This configuration setting *must not* contain a wildcard address!
#
# Default: http://$http_bind_address/
#http_publish_uri = http://192.168.1.1:9000/

#### External Graylog URI
#
# The public URI of Graylog which will be used by the Graylog web interface to communicate with the Graylog REST API.
#
# The external Graylog URI usually has to be specified, if Graylog is running behind a reverse proxy or load-balancer
# and it will be used to generate URLs addressing entities in the Graylog REST API (see $http_bind_address).
#
# When using Graylog Collector, this URI will be used to receive heartbeat messages and must be accessible for all collectors.
#
# This setting can be overriden on a per-request basis with the "X-Graylog-Server-URL" HTTP request header.
#
# Default: $http_publish_uri
#http_external_uri =

#### Enable CORS headers for HTTP interface
#
# This is necessary for JS-clients accessing the server directly.
# If these are disabled, modern browsers will not be able to retrieve resources from the server.
# This is enabled by default. Uncomment the next line to disable it.
#http_enable_cors = false

#### Enable GZIP support for HTTP interface
#
# This compresses API responses and therefore helps to reduce
# overall round trip times. This is enabled by default. Uncomment the next line to disable it.
#http_enable_gzip = false

# The maximum size of the HTTP request headers in bytes.
#http_max_header_size = 8192

# The size of the thread pool used exclusively for serving the HTTP interface.
#http_thread_pool_size = 16

################
# HTTPS settings
################

#### Enable HTTPS support for the HTTP interface
#
# This secures the communication with the HTTP interface with TLS to prevent request forgery and eavesdropping.
#
# Default: false
http_enable_tls = true

# The X.509 certificate chain file in PEM format to use for securing the HTTP interface.
http_tls_cert_file = /etc/ssl/certs/xxxx/wildcard.int.xxxx.cloud.pem

# The PKCS#8 private key file in PEM format to use for securing the HTTP interface.
http_tls_key_file = /etc/ssl/certs/xxxx/pkcs8-encrypted.pem

# The password to unlock the private key used for securing the HTTP interface.
http_tls_key_password = Secret123!


# Comma separated list of trusted proxies that are allowed to set the client address with X-Forwarded-For
# header. May be subnets, or hosts.
#trusted_proxies = 127.0.0.1/32, 0:0:0:0:0:0:0:1/128

# List of Elasticsearch hosts Graylog should connect to.
# Need to be specified as a comma-separated list of valid URIs for the http ports of your elasticsearch nodes.
# If one or more of your elasticsearch hosts require authentication, include the credentials in each node URI that
# requires authentication.
#
# Default: http://127.0.0.1:9200
elasticsearch_hosts = http://10.00.00.00:9200

# Maximum amount of time to wait for successfull connection to Elasticsearch HTTP port.
#
# Default: 10 Seconds
#elasticsearch_connect_timeout = 10s

# Maximum amount of time to wait for reading back a response from an Elasticsearch server.
#
# Default: 60 seconds
#elasticsearch_socket_timeout = 60s

# Maximum idle time for an Elasticsearch connection. If this is exceeded, this connection will
# be tore down.
#
# Default: inf
#elasticsearch_idle_timeout = -1s

# Maximum number of total connections to Elasticsearch.
#
# Default: 200
#elasticsearch_max_total_connections = 200

# Maximum number of total connections per Elasticsearch route (normally this means per
# elasticsearch server).
#
# Default: 20
#elasticsearch_max_total_connections_per_route = 20

# Maximum number of times Graylog will retry failed requests to Elasticsearch.
#
# Default: 2
#elasticsearch_max_retries = 2

# Enable automatic Elasticsearch node discovery through Nodes Info,
# see https://www.elastic.co/guide/en/elasticsearch/reference/5.4/cluster-nodes-info.html
#
# WARNING: Automatic node discovery does not work if Elasticsearch requires authentication, e. g. with Shield.
#
# Default: false
#elasticsearch_discovery_enabled = true

# Filter for including/excluding Elasticsearch nodes in discovery according to their custom attributes,
# see https://www.elastic.co/guide/en/elasticsearch/reference/5.4/cluster.html#cluster-nodes
#
# Default: empty
#elasticsearch_discovery_filter = rack:42

# Frequency of the Elasticsearch node discovery.
#
# Default: 30s
# elasticsearch_discovery_frequency = 30s

# Set the default scheme when connecting to Elasticsearch discovered nodes
#
# Default: http (available options: http, https)
#elasticsearch_discovery_default_scheme = http

# Enable payload compression for Elasticsearch requests.
#
# Default: false
#elasticsearch_compression_enabled = true

# Enable use of "Expect: 100-continue" Header for Elasticsearch index requests.
# If this is disabled, Graylog cannot properly handle HTTP 413 Request Entity Too Large errors.
#
# Default: true
#elasticsearch_use_expect_continue = true

# Graylog will use multiple indices to store documents in. You can configured the strategy it uses to determine
# when to rotate the currently active write index.
# It supports multiple rotation strategies:
#   - "count" of messages per index, use elasticsearch_max_docs_per_index below to configure
#   - "size" per index, use elasticsearch_max_size_per_index below to configure
# valid values are "count", "size" and "time", default is "count"
#
# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
#            to your previous 1.x settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
rotation_strategy = count

# (Approximate) maximum number of documents in an Elasticsearch index before a new index
# is being created, also see no_retention and elasticsearch_max_number_of_indices.
# Configure this if you used 'rotation_strategy = count' above.
#
# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
#            to your previous 1.x settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
elasticsearch_max_docs_per_index = 20000000

# (Approximate) maximum size in bytes per Elasticsearch index on disk before a new index is being created, also see
# no_retention and elasticsearch_max_number_of_indices. Default is 1GB.
# Configure this if you used 'rotation_strategy = size' above.
#
# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
#            to your previous 1.x settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
#elasticsearch_max_size_per_index = 1073741824

# (Approximate) maximum time before a new Elasticsearch index is being created, also see
# no_retention and elasticsearch_max_number_of_indices. Default is 1 day.
# Configure this if you used 'rotation_strategy = time' above.
# Please note that this rotation period does not look at the time specified in the received messages, but is
# using the real clock value to decide when to rotate the index!
# Specify the time using a duration and a suffix indicating which unit you want:
#  1w  = 1 week
#  1d  = 1 day
#  12h = 12 hours
# Permitted suffixes are: d for day, h for hour, m for minute, s for second.
#
# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
#            to your previous 1.x settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
#elasticsearch_max_time_per_index = 1d

# Disable checking the version of Elasticsearch for being compatible with this Graylog release.
# WARNING: Using Graylog with unsupported and untested versions of Elasticsearch may lead to data loss!
#elasticsearch_disable_version_check = true

# Disable message retention on this node, i. e. disable Elasticsearch index rotation.
#no_retention = false

# How many indices do you want to keep?
#
# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
#            to your previous 1.x settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
elasticsearch_max_number_of_indices = 20

# Decide what happens with the oldest indices when the maximum number of indices is reached.
# The following strategies are availble:
#   - delete # Deletes the index completely (Default)
#   - close # Closes the index and hides it from the system. Can be re-opened later.
#
# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
#            to your previous 1.x settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
retention_strategy = delete

# How many Elasticsearch shards and replicas should be used per index? Note that this only applies to newly created indices.
# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these
#            to your previous settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
elasticsearch_shards = 1
elasticsearch_replicas = 0

# Prefix for all Elasticsearch indices and index aliases managed by Graylog.
#
# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these
#            to your previous settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
elasticsearch_index_prefix = graylog

# Name of the Elasticsearch index template used by Graylog to apply the mandatory index mapping.
# Default: graylog-internal
#
# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these
#            to your previous settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
#elasticsearch_template_name = graylog-internal

# Do you want to allow searches with leading wildcards? This can be extremely resource hungry and should only
# be enabled with care. See also: http://docs.graylog.org/en/2.1/pages/queries.html
allow_leading_wildcard_searches = false

# Do you want to allow searches to be highlighted? Depending on the size of your messages this can be memory hungry and
# should only be enabled after making sure your Elasticsearch cluster has enough memory.
allow_highlighting = false

# Analyzer (tokenizer) to use for message and full_message field. The "standard" filter usually is a good idea.
# All supported analyzers are: standard, simple, whitespace, stop, keyword, pattern, language, snowball, custom
# Elasticsearch documentation: https://www.elastic.co/guide/en/elasticsearch/reference/2.3/analysis.html
# Note that this setting only takes effect on newly created indices.
#
# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these
#            to your previous settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
elasticsearch_analyzer = standard

# Global request timeout for Elasticsearch requests (e. g. during search, index creation, or index time-range
# calculations) based on a best-effort to restrict the runtime of Elasticsearch operations.
# Default: 1m
#elasticsearch_request_timeout = 1m

# Global timeout for index optimization (force merge) requests.
# Default: 1h
#elasticsearch_index_optimization_timeout = 1h

# Maximum number of concurrently running index optimization (force merge) jobs.
# If you are using lots of different index sets, you might want to increase that number.
# Default: 20
#elasticsearch_index_optimization_jobs = 20

# Time interval for index range information cleanups. This setting defines how often stale index range information
# is being purged from the database.
# Default: 1h
#index_ranges_cleanup_interval = 1h

# Time interval for the job that runs index field type maintenance tasks like cleaning up stale entries. This doesn't
# need to run very often.
# Default: 1h
#index_field_type_periodical_interval = 1h

# Batch size for the Elasticsearch output. This is the maximum (!) number of messages the Elasticsearch output
# module will get at once and write to Elasticsearch in a batch call. If the configured batch size has not been
# reached within output_flush_interval seconds, everything that is available will be flushed at once. Remember
# that every outputbuffer processor manages its own batch and performs its own batch write calls.
# ("outputbuffer_processors" variable)
output_batch_size = 500

# Flush interval (in seconds) for the Elasticsearch output. This is the maximum amount of time between two
# batches of messages written to Elasticsearch. It is only effective at all if your minimum number of messages
# for this time period is less than output_batch_size * outputbuffer_processors.
output_flush_interval = 1

# As stream outputs are loaded only on demand, an output which is failing to initialize will be tried over and
# over again. To prevent this, the following configuration options define after how many faults an output will
# not be tried again for an also configurable amount of seconds.
output_fault_count_threshold = 5
output_fault_penalty_seconds = 30

# The number of parallel running processors.
# Raise this number if your buffers are filling up.
processbuffer_processors = 5
outputbuffer_processors = 3

# The following settings (outputbuffer_processor_*) configure the thread pools backing each output buffer processor.
# See https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ThreadPoolExecutor.html for technical details

# When the number of threads is greater than the core (see outputbuffer_processor_threads_core_pool_size),
# this is the maximum time in milliseconds that excess idle threads will wait for new tasks before terminating.
# Default: 5000
#outputbuffer_processor_keep_alive_time = 5000

# The number of threads to keep in the pool, even if they are idle, unless allowCoreThreadTimeOut is set
# Default: 3
#outputbuffer_processor_threads_core_pool_size = 3

# The maximum number of threads to allow in the pool
# Default: 30
#outputbuffer_processor_threads_max_pool_size = 30

# UDP receive buffer size for all message inputs (e. g. SyslogUDPInput).
#udp_recvbuffer_sizes = 1048576

# Wait strategy describing how buffer processors wait on a cursor sequence. (default: sleeping)
# Possible types:
#  - yielding
#     Compromise between performance and CPU usage.
#  - sleeping
#     Compromise between performance and CPU usage. Latency spikes can occur after quiet periods.
#  - blocking
#     High throughput, low latency, higher CPU usage.
#  - busy_spinning
#     Avoids syscalls which could introduce latency jitter. Best when threads can be bound to specific CPU cores.
processor_wait_strategy = blocking

# Size of internal ring buffers. Raise this if raising outputbuffer_processors does not help anymore.
# For optimum performance your LogMessage objects in the ring buffer should fit in your CPU L3 cache.
# Must be a power of 2. (512, 1024, 2048, ...)
ring_size = 65536

inputbuffer_ring_size = 65536
inputbuffer_processors = 2
inputbuffer_wait_strategy = blocking

# Enable the disk based message journal.
message_journal_enabled = true

# The directory which will be used to store the message journal. The directory must be exclusively used by Graylog and
# must not contain any other files than the ones created by Graylog itself.
#
# ATTENTION:
#   If you create a seperate partition for the journal files and use a file system creating directories like 'lost+found'
#   in the root directory, you need to create a sub directory for your journal.
#   Otherwise Graylog will log an error message that the journal is corrupt and Graylog will not start.
message_journal_dir = /var/lib/graylog-server/journal

# Journal hold messages before they could be written to Elasticsearch.
# For a maximum of 12 hours or 5 GB whichever happens first.
# During normal operation the journal will be smaller.
#message_journal_max_age = 12h
#message_journal_max_size = 5gb

#message_journal_flush_age = 1m
#message_journal_flush_interval = 1000000
#message_journal_segment_age = 1h
#message_journal_segment_size = 100mb

# Number of threads used exclusively for dispatching internal events. Default is 2.
#async_eventbus_processors = 2

# How many seconds to wait between marking node as DEAD for possible load balancers and starting the actual
# shutdown process. Set to 0 if you have no status checking load balancers in front.
lb_recognition_period_seconds = 3

# Journal usage percentage that triggers requesting throttling for this server node from load balancers. The feature is
# disabled if not set.
#lb_throttle_threshold_percentage = 95

# Every message is matched against the configured streams and it can happen that a stream contains rules which
# take an unusual amount of time to run, for example if its using regular expressions that perform excessive backtracking.
# This will impact the processing of the entire server. To keep such misbehaving stream rules from impacting other
# streams, Graylog limits the execution time for each stream.
# The default values are noted below, the timeout is in milliseconds.
# If the stream matching for one stream took longer than the timeout value, and this happened more than "max_faults" times
# that stream is disabled and a notification is shown in the web interface.
#stream_processing_timeout = 2000
#stream_processing_max_faults = 3

# Since 0.21 the Graylog server supports pluggable output modules. This means a single message can be written to multiple
# outputs. The next setting defines the timeout for a single output module, including the default output module where all
# messages end up.
#
# Time in milliseconds to wait for all message outputs to finish writing a single message.
#output_module_timeout = 10000

# Time in milliseconds after which a detected stale master node is being rechecked on startup.
#stale_master_timeout = 2000

# Time in milliseconds which Graylog is waiting for all threads to stop on shutdown.
#shutdown_timeout = 30000

# MongoDB connection string
# See https://docs.mongodb.com/manual/reference/connection-string/ for details
mongodb_uri = mongodb://localhost/graylog

# Authenticate against the MongoDB server
# '+'-signs in the username or password need to be replaced by '%2B'
#mongodb_uri = mongodb://grayloguser:secret@localhost:27017/graylog

# Use a replica set instead of a single host
#mongodb_uri = mongodb://grayloguser:secret@localhost:27017,localhost:27018,localhost:27019/graylog?replicaSet=rs01

# DNS Seedlist https://docs.mongodb.com/manual/reference/connection-string/#dns-seedlist-connection-format
#mongodb_uri = mongodb+srv://server.example.org/graylog

# Increase this value according to the maximum connections your MongoDB server can handle from a single client
# if you encounter MongoDB connection problems.
mongodb_max_connections = 1000

# Number of threads allowed to be blocked by MongoDB connections multiplier. Default: 5
# If mongodb_max_connections is 100, and mongodb_threads_allowed_to_block_multiplier is 5,
# then 500 threads can block. More than that and an exception will be thrown.
# http://api.mongodb.com/java/current/com/mongodb/MongoOptions.html#threadsAllowedToBlockForConnectionMultiplier
mongodb_threads_allowed_to_block_multiplier = 5


# Email transport
transport_email_enabled = true
transport_email_hostname = smtp03.int.xxxx.cloud
transport_email_port = 25
transport_email_use_auth = false
#transport_email_auth_username = graylog@xxxx.cloud
#transport_email_auth_password = secret
transport_email_subject_prefix = [graylog]
transport_email_from_email = graylog@xxxx.cloud

continuing the config file


# Encryption settings
#
# ATTENTION:
#    Using SMTP with STARTTLS *and* SMTPS at the same time is *not* possible.

# Use SMTP with STARTTLS, see https://en.wikipedia.org/wiki/Opportunistic_TLS
#transport_email_use_tls = true

# Use SMTP over SSL (SMTPS), see https://en.wikipedia.org/wiki/SMTPS
# This is deprecated on most SMTP services!
#transport_email_use_ssl = false


# Specify and uncomment this if you want to include links to the stream in your stream alert mails.
# This should define the fully qualified base url to your web interface exactly the same way as it is accessed by your users.
#transport_email_web_interface_url = https://graylog.example.com

# The default connect timeout for outgoing HTTP connections.
# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
# Default: 5s
#http_connect_timeout = 5s

# The default read timeout for outgoing HTTP connections.
# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
# Default: 10s
#http_read_timeout = 10s

# The default write timeout for outgoing HTTP connections.
# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
# Default: 10s
#http_write_timeout = 10s

# HTTP proxy for outgoing HTTP connections
# ATTENTION: If you configure a proxy, make sure to also configure the "http_non_proxy_hosts" option so internal
#            HTTP connections with other nodes does not go through the proxy.
# Examples:
#   - http://proxy.example.com:8123
#   - http://username:password@proxy.example.com:8123
#http_proxy_uri =

# A list of hosts that should be reached directly, bypassing the configured proxy server.
# This is a list of patterns separated by ",". The patterns may start or end with a "*" for wildcards.
# Any host matching one of these patterns will be reached through a direct connection instead of through a proxy.
# Examples:
#   - localhost,127.0.0.1
#   - 10.0.*,*.example.com
#http_non_proxy_hosts =

# Disable the optimization of Elasticsearch indices after index cycling. This may take some load from Elasticsearch
# on heavily used systems with large indices, but it will decrease search performance. The default is to optimize
# cycled indices.
#
# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these
#            to your previous settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
#disable_index_optimization = true

# Optimize the index down to <= index_optimization_max_num_segments. A higher number may take some load from Elasticsearch
# on heavily used systems with large indices, but it will decrease search performance. The default is 1.
#
# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these
#            to your previous settings so they will be migrated to the database!
#            This configuration setting is only used on the first start of Graylog. After that,
#            index related settings can be changed in the Graylog web interface on the 'System / Indices' page.
#            Also see http://docs.graylog.org/en/2.3/pages/configuration/index_model.html#index-set-configuration.
#index_optimization_max_num_segments = 1

# The threshold of the garbage collection runs. If GC runs take longer than this threshold, a system notification
# will be generated to warn the administrator about possible problems with the system. Default is 1 second.
#gc_warning_threshold = 1s

# Connection timeout for a configured LDAP server (e. g. ActiveDirectory) in milliseconds.
#ldap_connection_timeout = 2000

# Disable the use of SIGAR for collecting system stats
#disable_sigar = false

# The default cache time for dashboard widgets. (Default: 10 seconds, minimum: 1 second)
#dashboard_widget_default_cache_time = 10s

# For some cluster-related REST requests, the node must query all other nodes in the cluster. This is the maximum number
# of threads available for this. Increase it, if '/cluster/*' requests take long to complete.
# Should be http_thread_pool_size * average_cluster_size if you have a high number of concurrent users.
proxied_requests_thread_pool_size = 32

# The server is writing processing status information to the database on a regular basis. This setting controls how
# often the data is written to the database.
# Default: 1s (cannot be less than 1s)
#processing_status_persist_interval = 1s

# Configures the threshold for detecting outdated processing status records. Any records that haven't been updated
# in the configured threshold will be ignored.
# Default: 1m (one minute)
#processing_status_update_threshold = 1m

# Configures the journal write rate threshold for selecting processing status records. Any records that have a lower
# one minute rate than the configured value might be ignored. (dependent on number of messages in the journal)
# Default: 1
#processing_status_journal_write_rate_threshold = 1

# Configures the prefix used for graylog event indices
# Default: gl-events
#default_events_index_prefix = gl-events

# Configures the prefix used for graylog system event indices
# Default: gl-system-events
#default_system_events_index_prefix = gl-system-events

# Automatically load content packs in "content_packs_dir" on the first start of Graylog.
#content_packs_loader_enabled = false

# The directory which contains content packs which should be loaded on the first start of Graylog.
#content_packs_dir = data/contentpacks

# A comma-separated list of content packs (files in "content_packs_dir") which should be applied on
# the first start of Graylog.
# Default: empty
#content_packs_auto_install = grok-patterns.json

# The allowed TLS protocols for system wide TLS enabled servers. (e.g. message inputs, http interface)
# Setting this to an empty value, leaves it up to system libraries and the used JDK to chose a default.
# Default: TLSv1.2,TLSv1.3  (might be automatically adjusted to protocols supported by the JDK)
#enabled_tls_protocols= TLSv1.2,TLSv1.3
elasticsearch_version = 7
elasticsearch_http_enabled = false
elasticsearch_discovery_zen_ping_unicast_hosts = 10.00.00.00:9200
mongodb_useauth = false
web_listen_uri = http://10.00.00.00:9000/
res_listen_uri = http://10.00.00.00:9000/api/```

Can you share the errors shown in that screenshot from the opensearch service status?

Also are there any errors in the opensearch log itself (should be in /var/log/opensearch)?

Hey @adrianrus

I can tell ya right now your Graylog configuration file is old, like version 2.5 settings

Graylog started using http_bind around version 3.x

I assume opensearch is for testing since its in a /mnt directory?

I was running CentOS 7 with Graylog version 4.3 then installed opensearch 1.3 (recommended for that GL version)

Suggestion I would install Opensearch 1.3 with Graylog 4.3 once completed Upgrade Graylog to 5.x then if yuo wish to upgrade Opensearch 2.x .

If your working with Deb packages here what i useed to upgrade, this doc is spot on, I had no issues.

https://go2docs.graylog.org/4-x/planning_your_deployment/opensearch_on_debian__tarball_.htm?Highlight=Opensearch

Hope that helps

opensearch errors cleared

still, GL is still using the elasticsearch instead of opensearch

i am using /mnt/… because is an separate disk that i want to use for the logs and lib folders as these get wild regarding space usage.

right now i have Graylog 4.3 upgraded from 4.2 fresh install, i don’t know why those 2.5 stuff you noticed.
I am on Ubuntu 20.

Thing is that both ES and OS look like corectly working, but tge GL server is still using ES for gathering the logs, and i presume i need to make some setting in somewhere to tell GL to use opensearch…

I can’t get this one right…

Hey

I understand :+1:

I have a tendency to find stuff like that :laughing:

In your Opensearch and/or Elasticsearch file you have this.

path.data: /var/lib/opensearch

I would adjust this to your needs first.
example.

path.data: /mnt/opensearch

Using this documentation example here Then leave the rest alone and see if that works.

this is the opensearch.yml file

# ======================== OpenSearch Configuration =========================
#
# NOTE: OpenSearch 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.opensearch.org
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: graylog
#
# ------------------------------------ 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: /mnt/data1/opensearch/lib
#
# Path to log files:
#
path.logs: /mnt/data1/opensearch/log
#
# ----------------------------------- 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.
#
# OpenSearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: 10.204.68.39
#
# Set a custom port for HTTP:
#
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: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
#cluster.initial_master_nodes: ["node-1", "node-2"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true
discovery.type: single_node
action.auto_create_index: false
plugins.security.disabled: true

and ES yml

# ======================== 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: graylog
#
# ------------------------------------ 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: /mnt/data1/elasticsearch/lib
#
# Path to log files:
#
path.logs: /mnt/data1/elasticsearch/log
#
# ----------------------------------- 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 -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: 10.204.68.39
#
# Set a custom port for HTTP:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when new node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.zen.ping.unicast.hosts: ["host1", "host2"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
#discovery.zen.minimum_master_nodes:
#
# For more information, consult the zen discovery module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true
action.auto_create_index: false
discovery.type: single-node

Hey

That weird, seams like it should have worked.
Just for reference I used this while back, not sure if it will help you issue.

#Download OpenSearch 1.3.4
wget https://artifacts.opensearch.org/releases/bundle/opensearch/1.3.4/opensearch-1.3.4-linux-x64.tar.gz

#Create user & group
sudo adduser --system --disabled-password --disabled-login --home /var/empty --no-create-home --quiet --force-badname --group opensearch

#Create Directories
sudo mkdir -p /var/lib/opensearch /var/log/opensearch

#Extract Contents from tar
sudo tar -zxf opensearch-1.3.4-linux-x64.tar.gz 
sudo mv opensearch-1.3.4 opensearch 
sudo mv opensearch /usr/share/

#Set Permissions
sudo chown -R opensearch:opensearch /usr/share/opensearch /var/log/opensearch /var/lib/opensearch
sudo chmod -R 2750 /usr/share/opensearch /var/log/opensearch /var/lib/opensearch

#Create System Service
sudo su -
cat > /etc/systemd/system/opensearch.service <<EOF
[Unit]
Description=OpenSearch
Documentation=https://OpenSearch.org/docs/latest
Requires=network.target remote-fs.target
After=network.target remote-fs.target
ConditionPathExists=/usr/share/opensearch
ConditionPathExists=/var/lib/opensearch
[Service]
Environment=OpenSearch_HOME=/usr/share/opensearch
Environment=OpenSearch_PATH_CONF=usr/share/opensearch/config
ReadWritePaths=/var/log/opensearch
User=opensearch
Group=opensearch
WorkingDirectory=/usr/share/opensearch
ExecStart=/usr/share/opensearch/bin/opensearch
# Specifies the maximum file descriptor number that can be opened by this process
LimitNOFILE=65535
# Specifies the maximum number of processes
LimitNPROC=4096
# Specifies the maximum size of virtual memory
LimitAS=infinity
# Specifies the maximum file size
LimitFSIZE=infinity
# Disable timeout logic and wait until process is stopped
TimeoutStopSec=0
# SIGTERM signal is used to stop the Java process
KillSignal=SIGTERM
# Send the signal only to the JVM rather than its control group
KillMode=process
# Java process is never killed
SendSIGKILL=no
# When a JVM receives a SIGTERM signal it exits with code 143
SuccessExitStatus=143
# Allow a slow startup before the systemd notifier module kicks in to extend the timeout
TimeoutStartSec=180
[Install]
WantedBy=multi-user.target
EOF

i used the same instructions, yes.
THing is that the Openservice service starts just fine, no errors, but graylog is still using the elasticsearch - i was wondering WHERE in the settings yu ‘tell’ graylog to use opensearch.

this is my opensearch service, made after that documentation you also used:

[Unit]
Description=OpenSearch
Documentation=https://OpenSearch.org/docs/latest
Requires=network.target remote-fs.target
After=network.target remote-fs.target
ConditionPathExists=/mnt/data1/opensearch
ConditionPathExists=/mnt/data1/opensearch//config
[Service]
Environment=OpenSearch_HOME=/mnt/data1/opensearch
Environment=OpenSearch_PATH_CONF=/mnt/data1/opensearch//config
ReadWritePaths=/mnt/data1/opensearch/log
User=opensearch
Group=opensearch
WorkingDirectory=/mnt/data1/opensearch
ExecStart=/mnt/data1/opensearch/bin/opensearch
# Specifies the maximum file descriptor number that can be opened by this process
LimitNOFILE=65535
# Specifies the maximum number of processes
LimitNPROC=4096
# Specifies the maximum size of virtual memory
LimitAS=infinity
# Specifies the maximum file size
LimitFSIZE=infinity
# Disable timeout logic and wait until process is stopped
TimeoutStopSec=0
# SIGTERM signal is used to stop the Java process
KillSignal=SIGTERM
# Send the signal only to the JVM rather than its control group
KillMode=process
# Java process is never killed
SendSIGKILL=no
# When a JVM receives a SIGTERM signal it exits with code 143
SuccessExitStatus=143
# Allow a slow startup before the systemd notifier module kicks in to extend the timeout
TimeoutStartSec=180
[Install]
WantedBy=multi-user.target

Are opensearch and elasticsearch installed on the same server?
What version of opensearch do you have installed?

Restart opensearch service and then do journalctl -u opensearch to see errors. You can also check errors in /var/log/opensearch/graylog.log.

cat /mnt/data1/opensearch/log/graylog.log
[2023-06-20T14:29:13,926][INFO ][o.o.n.Node ] [ipt-fr-01-log] version[1.3.2], pid[627], build[tar/6febcf7b53ff189de767e460e905e9e5aeecc8cb/2022-05-04T03:58:48.328641Z], OS[Linux/5.4.0-1050-ibm/amd64], JVM[Eclipse Adoptium/OpenJDK 64-Bit Server VM/11.0.15/11.0.15+10]
[2023-06-20T14:29:13,982][INFO ][o.o.n.Node ] [ipt-fr-01-log] JVM home [/mnt/data1/opensearch/jdk], using bundled JDK [true]
[2023-06-20T14:29:13,989][INFO ][o.o.n.Node ] [ipt-fr-01-log] JVM arguments [-Xshare:auto, -Dopensearch.networkaddress.cache.ttl=60, -Dopensearch.networkaddress.cache.negative.ttl=10, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dio.netty.allocator.numDirectArenas=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.locale.providers=SPI,COMPAT, -Xms2g, -Xmx2g, -XX:+UseG1GC, -XX:G1ReservePercent=25, -XX:InitiatingHeapOccupancyPercent=30, -Djava.io.tmpdir=/tmp/opensearch-11045329116021674982, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/hs_err_pid%p.log, -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m, -XX:MaxDirectMemorySize=1073741824, -Dopensearch.path.home=/mnt/data1/opensearch, -Dopensearch.path.conf=/mnt/data1/opensearch/config, -Dopensearch.distribution.type=tar, -Dopensearch.bundled_jdk=true]
[2023-06-20T14:29:19,134][WARN ][stderr ] [ipt-fr-01-log] SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.
[2023-06-20T14:29:19,135][WARN ][stderr ] [ipt-fr-01-log] SLF4J: Defaulting to no-operation (NOP) logger implementation
[2023-06-20T14:29:19,135][WARN ][stderr ] [ipt-fr-01-log] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[2023-06-20T14:29:19,214][INFO ][o.o.s.s.t.SSLConfig ] [ipt-fr-01-log] SSL dual mode is disabled
[2023-06-20T14:29:19,222][WARN ][o.o.s.OpenSearchSecurityPlugin] [ipt-fr-01-log] OpenSearch Security plugin installed but disabled. This can expose your configuration (including passwords) to the public.
[2023-06-20T14:29:21,649][INFO ][o.o.p.c.PluginSettings ] [ipt-fr-01-log] Trying to create directory /dev/shm/performanceanalyzer/.
[2023-06-20T14:29:21,651][INFO ][o.o.p.c.PluginSettings ] [ipt-fr-01-log] Config: metricsLocation: /dev/shm/performanceanalyzer/, metricsDeletionInterval: 1, httpsEnabled: false, cleanup-metrics-db-files: true, batch-metrics-retention-period-minutes: 7, rpc-port: 9650, webservice-port 9600
[2023-06-20T14:29:22,819][INFO ][o.o.i.r.ReindexPlugin ] [ipt-fr-01-log] ReindexPlugin reloadSPI called
[2023-06-20T14:29:22,832][INFO ][o.o.i.r.ReindexPlugin ] [ipt-fr-01-log] Unable to find any implementation for RemoteReindexExtension
[2023-06-20T14:29:22,968][INFO ][o.o.j.JobSchedulerPlugin ] [ipt-fr-01-log] Loaded scheduler extension: opendistro_anomaly_detector, index: .opendistro-anomaly-detector-jobs
[2023-06-20T14:29:23,136][INFO ][o.o.j.JobSchedulerPlugin ] [ipt-fr-01-log] Loaded scheduler extension: reports-scheduler, index: .opendistro-reports-definitions
[2023-06-20T14:29:23,144][INFO ][o.o.j.JobSchedulerPlugin ] [ipt-fr-01-log] Loaded scheduler extension: opendistro-index-management, index: .opendistro-ism-config
[2023-06-20T14:29:23,167][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [aggs-matrix-stats]
[2023-06-20T14:29:23,167][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [analysis-common]
[2023-06-20T14:29:23,170][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [geo]
[2023-06-20T14:29:23,171][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [ingest-common]
[2023-06-20T14:29:23,171][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [ingest-geoip]
[2023-06-20T14:29:23,174][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [ingest-user-agent]
[2023-06-20T14:29:23,175][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [lang-expression]
[2023-06-20T14:29:23,175][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [lang-mustache]
[2023-06-20T14:29:23,176][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [lang-painless]
[2023-06-20T14:29:23,178][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [mapper-extras]
[2023-06-20T14:29:23,179][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [opensearch-dashboards]
[2023-06-20T14:29:23,179][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [parent-join]
[2023-06-20T14:29:23,182][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [percolator]
[2023-06-20T14:29:23,183][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [rank-eval]
[2023-06-20T14:29:23,183][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [reindex]
[2023-06-20T14:29:23,184][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [repository-url]
[2023-06-20T14:29:23,190][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded module [transport-netty4]
[2023-06-20T14:29:23,191][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-alerting]
[2023-06-20T14:29:23,192][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-anomaly-detection]
[2023-06-20T14:29:23,192][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-asynchronous-search]
[2023-06-20T14:29:23,193][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-cross-cluster-replication]
[2023-06-20T14:29:23,193][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-index-management]
[2023-06-20T14:29:23,198][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-job-scheduler]
[2023-06-20T14:29:23,201][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-knn]
[2023-06-20T14:29:23,202][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-ml]
[2023-06-20T14:29:23,202][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-observability]
[2023-06-20T14:29:23,202][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-performance-analyzer]
[2023-06-20T14:29:23,203][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-reports-scheduler]
[2023-06-20T14:29:23,203][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-security]
[2023-06-20T14:29:23,204][INFO ][o.o.p.PluginsService ] [ipt-fr-01-log] loaded plugin [opensearch-sql]
[2023-06-20T14:29:23,384][INFO ][o.o.e.NodeEnvironment ] [ipt-fr-01-log] using [1] data paths, mounts [[/mnt/data1 (/dev/vdb)]], net usable_space [305.4gb], net total_space [1tb], types [ext4]
[2023-06-20T14:29:23,385][INFO ][o.o.e.NodeEnvironment ] [ipt-fr-01-log] heap size [2gb], compressed ordinary object pointers [true]
[2023-06-20T14:29:23,551][INFO ][o.o.n.Node ] [ipt-fr-01-log] node name [ipt-fr-01-log], node ID [9B8PITtmRuGTO55BIR4Rig], cluster name [graylog], roles [master, remote_cluster_client, data, ingest]
[2023-06-20T14:29:40,956][INFO ][o.o.a.b.ADCircuitBreakerService] [ipt-fr-01-log] Registered memory breaker.
[2023-06-20T14:29:43,117][INFO ][o.o.m.c.b.MLCircuitBreakerService] [ipt-fr-01-log] Registered ML memory breaker.
[2023-06-20T14:29:47,480][INFO ][o.o.t.NettyAllocator ] [ipt-fr-01-log] creating NettyAllocator with the following configs: [name=opensearch_configured, chunk_size=256kb, suggested_max_allocation_size=256kb, factors={opensearch.unsafe.use_netty_default_chunk_and_page_size=false, g1gc_enabled=true, g1gc_region_size=1mb}]
[2023-06-20T14:29:47,927][ERROR][o.o.b.Bootstrap ] [ipt-fr-01-log] Exception
java.lang.IllegalArgumentException: Unknown discovery type [single_node]
at org.opensearch.discovery.DiscoveryModule.(DiscoveryModule.java:227) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.node.Node.(Node.java:815) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.node.Node.(Node.java:319) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.Bootstrap$5.(Bootstrap.java:242) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:242) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:412) [opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:178) [opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:169) [opensearch-1.3.2.jar:1.3.2]
at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:100) [opensearch-1.3.2.jar:1.3.2]
at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138) [opensearch-cli-1.3.2.jar:1.3.2]
at org.opensearch.cli.Command.main(Command.java:101) [opensearch-cli-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:135) [opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:101) [opensearch-1.3.2.jar:1.3.2]
[2023-06-20T14:29:47,964][ERROR][o.o.b.OpenSearchUncaughtExceptionHandler] [ipt-fr-01-log] uncaught exception in thread [main]
org.opensearch.bootstrap.StartupException: java.lang.IllegalArgumentException: Unknown discovery type [single_node]
at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:182) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:169) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:100) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138) ~[opensearch-cli-1.3.2.jar:1.3.2]
at org.opensearch.cli.Command.main(Command.java:101) ~[opensearch-cli-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:135) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:101) ~[opensearch-1.3.2.jar:1.3.2]
Caused by: java.lang.IllegalArgumentException: Unknown discovery type [single_node]
at org.opensearch.discovery.DiscoveryModule.(DiscoveryModule.java:227) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.node.Node.(Node.java:815) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.node.Node.(Node.java:319) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.Bootstrap$5.(Bootstrap.java:242) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:242) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:412) ~[opensearch-1.3.2.jar:1.3.2]
at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:178) ~[opensearch-1.3.2.jar:1.3.2]
… 6 more

JOurnal cmd, some of it


pender.rolling.RollingFileManager$RollingFileManagerFactory.createManager(RollingFileManager.java:746)
pender.rolling.RollingFileManager$RollingFileManagerFactory.createManager(RollingFileManager.java:716)
pender.AbstractManager.getManager(AbstractManager.java:114)
pender.OutputStreamManager.getManager(OutputStreamManager.java:100)
pender.rolling.RollingFileManager.getFileManager(RollingFileManager.java:217)
pender.RollingFileAppender$Builder.build(RollingFileAppender.java:146)
pender.RollingFileAppender$Builder.build(RollingFileAppender.java:62)
 ESCOD
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:169)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:100)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.cli.Command.main(Command.java:101)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:135)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:101)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]: 2023-06-16 10:44:36,217 main ERROR Unable to invoke factory method in class org.apache.logging.log4j.core.appender.RollingFileAppender>
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.findFactoryMethod(PluginBuilder.java:236)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:134)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1120)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1045)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1037)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:651)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:247)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:293)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:626)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:302)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.common.logging.LogConfigurator.configure(LogConfigurator.java:246)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.common.logging.LogConfigurator.configure(LogConfigurator.java:142)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:373)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:178)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:169)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:100)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.cli.Command.main(Command.java:101)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:135)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:101)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]: 2023-06-16 10:44:36,229 main ERROR RollingFileManager (/mnt/data1/elasticsearch/log/graylog.log) java.io.FileNotFoundException: /mnt/d>
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at java.base/java.io.FileOutputStream.open0(Native Method)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:237)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:158)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory.createManager(RollingFileManage>
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory.createManager(RollingFileManage>
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:114)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.appender.rolling.RollingFileManager.getFileManager(RollingFileManager.java:217)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.appender.RollingFileAppender$Builder.build(RollingFileAppender.java:146)
Jun 16 10:44:36 ipt-fr-01-log opensearch[29039]:         at org.apache.logging.log4j.core.appender.RollingFileAppender$Builder.build(RollingFileAppender.java:62)
 ESCOC
rch.execute(OpenSearch.java:169)
areCommand.execute(EnvironmentAwareCommand.java:100)
ithoutErrorHandling(Command.java:138)
Command.java:101)
rch.main(OpenSearch.java:135)
rch.main(OpenSearch.java:101)
o invoke factory method in class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile: java.lang.IllegalStateException: No factory method found for class>
nfig.plugins.util.PluginBuilder.findFactoryMethod(PluginBuilder.java:236)
nfig.plugins.util.PluginBuilder.build(PluginBuilder.java:134)
nfig.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1120)
nfig.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1045)
nfig.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1037)
nfig.AbstractConfiguration.doConfigure(AbstractConfiguration.java:651)
nfig.AbstractConfiguration.initialize(AbstractConfiguration.java:247)
nfig.AbstractConfiguration.start(AbstractConfiguration.java:293)
ggerContext.setConfiguration(LoggerContext.java:626)
ggerContext.start(LoggerContext.java:302)
gConfigurator.configure(LogConfigurator.java:246)
gConfigurator.configure(LogConfigurator.java:142)
ap.init(Bootstrap.java:373)
rch.init(OpenSearch.java:178)
rch.execute(OpenSearch.java:169)
areCommand.execute(EnvironmentAwareCommand.java:100)
ithoutErrorHandling(Command.java:138)
Command.java:101)
rch.main(OpenSearch.java:135)
rch.main(OpenSearch.java:101)
ileManager (/mnt/data1/elasticsearch/log/graylog.log) java.io.FileNotFoundException: /mnt/data1/elasticsearch/log/graylog.log (Permission denied) java.io.FileNotFoundException: /mnt/d>
am.open0(Native Method)
am.open(FileOutputStream.java:298)
am.<init>(FileOutputStream.java:237)
am.<init>(FileOutputStream.java:158)
pender.rolling.RollingFileManager$RollingFileManagerFactory.createManager(RollingFileManager.java:746)
pender.rolling.RollingFileManager$RollingFileManagerFactory.createManager(RollingFileManager.java:716)
pender.AbstractManager.getManager(AbstractManager.java:114)
pender.OutputStreamManager.getManager(OutputStreamManager.java:100)
pender.rolling.RollingFileManager.getFileManager(RollingFileManager.java:217)
pender.RollingFileAppender$Builder.build(RollingFileAppender.java:146)
pender.RollingFileAppender$Builder.build(RollingFileAppender.java:62)

ileManager (/mnt/data1/elasticsearch/log/graylog.log) java.io.FileNotFoundException: /mnt/data1/elasticsearch/log/graylog.log (Permission denied) java.io.FileNotFoundException: /mnt/d>

this got my attention from all above, because also i cannot interpret any of the other errors even with google :smiley: :))

Still this is abt a permission to a LOG file, not something capital, still, the other errors might help you to get some idea of it

i really hope i can find a solution tho this as i am so not willing to reinstall form scratch 5.0 with everything on
anyone…? :frowning:

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