Elasticsearch exception: Unexpected error while indexing monitoring document


(Shraddha Srivastav) #1

Hi,
When i run ES it gives me an exception of
Unexpected error while indexing monitoring document org.elasticsearch.xpack.monitoring

My ES config file is as following:

======================== 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: my-application

------------------------------------ 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: /path/to/data

Path to log files:

#path.logs: /path/to/logs

----------------------------------- 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: 192.168.0.1
network.host: 0.0.0.0
network.bind_host: 0.0.0.0

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

I have few dounts:

  1. The ES cant create index so i am unable to pull the data in Kibana.
  2. What is the correct syntax to pass the index to ES ? I used the following in my config file:

input {
file{
path => "C:\Users\shraddhasrivastav\Downloads\cars.csv"
start_position => "beginning"
sincedb_path => "nul"
}

		}

filter{
csv{
columns => [ "BMU_Debug_Wnty_Tot_s_NRuntwo","RBMU_Stats_Temp_Cell_Max"]
}

		mutate {
				convert => {
				"RBMU_Stats_Temp_Cell_Max"  => "integer" 
				"BMU_Debug_Wnty_Tot_s_NRuntwo" =>  "float"
									}
						}
	 }

output {
elasticsearch {
hosts => ["localhost:9200"]
index => "cars"
}
stdout { }
}

P.S. My logstash is running fine, giving all the parameters on cmd.

Please help.


(Tim Vernum) #2

Please make the effort to format your post to be as readable as possible, in particular configuration files and code should be inserted as pre-formatted blocks (either with the </> button, or by wrapping them in between pairs or "```" ) . There's a live preview panel so you can see what your post looks like before you submit it.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.


(Tim Vernum) #3

Please provide full details of the exception, including any stack trace. While it is very helpful to provide configuration files, the number 1 thing we need to see in order to debug an error message, is the details of the error message.


(system) #4

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