My "Logstash.conf" gives errors

Elastic Stack Logstash
1

Hello there !

I'm trying to configure an ELK to have a better overview of my CSV files.

But when I launch my conf file, I get some issues I can't solve despite my searches and my tries for solving.

My conf file :

input {
file {
path => "C:/...*.csv"
start_position => beginning
sincedb_path => "/dev/null"
}
}

filter {
csv {
columns => ["IP Address", "DNS Name", "Scan Period"]
separator => ";"
}
}

output {
stdout { codec => rubydebug }
elasticsearch {
host => "localhost:9200"
index => "csv_index"
}
}

The result next a logstash -f "*.csv" command line :

[2017-06-12T14:52:17,639][ERROR][logstash.outputs.elasticsearch] Unknown setting
'host' for elasticsearch
[2017-06-12T14:52:17,655][ERROR][logstash.agent ] Cannot create pipeli
ne {:reason=>"Something is wrong with your configuration."}
[2017-06-12T14:52:17,967][INFO ][logstash.outputs.elasticsearch] Elasticsearch p
ool URLs updated {:changes=>{:removed=>[], :added=>[http://logstash_system:xxxxx
x@localhost:9200/_xpack/monitoring/?system_id=logstash&system_api_version=2&inte
rval=1s]}}
[2017-06-12T14:52:17,967][INFO ][logstash.outputs.elasticsearch] Running health
check to see if an Elasticsearch connection is working {:healthcheck_url=>http:/
/logstash_system:xxxxxx@localhost:9200/, :path=>"/"}
[2017-06-12T14:52:18,232][WARN ][logstash.outputs.elasticsearch] Restored connec
tion to ES instance {:url=>#<URI::HTTP:0x6cfddc20 URL:http://logstash_system:xxx
xxx@localhost:9200/>}
[2017-06-12T14:52:18,232][INFO ][logstash.outputs.elasticsearch] New Elasticsear
ch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>[#<URI::HTTP:0x77
6b50d8 URL:http://localhost:9200>]}
[2017-06-12T14:52:18,248][INFO ][logstash.outputs.elasticsearch] Elasticsearch p
ool URLs updated {:changes=>{:removed=>[], :added=>[http://logstash_system:xxxxx
x@localhost:9200/_xpack/monitoring/?system_id=logstash&system_api_version=2&inte
rval=1s]}}
[2017-06-12T14:52:18,248][INFO ][logstash.outputs.elasticsearch] Running health
check to see if an Elasticsearch connection is working {:healthcheck_url=>http:/
/logstash_system:xxxxxx@localhost:9200/, :path=>"/"}
[2017-06-12T14:52:18,263][WARN ][logstash.outputs.elasticsearch] Restored connec
tion to ES instance {:url=>#<URI::HTTP:0x3ff94539 URL:http://logstash_system:xxx
xxx@localhost:9200/>}
[2017-06-12T14:52:18,263][INFO ][logstash.outputs.elasticsearch] New Elasticsear
ch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>[#<URI::HTTP:0x72
e9016 URL:http://localhost:9200>]}
[2017-06-12T14:52:18,263][INFO ][logstash.pipeline ] Starting pipeline {"
id"=>".monitoring-logstash", "pipeline.workers"=>1, "pipeline.batch.size"=>2, "p
ipeline.batch.delay"=>5, "pipeline.max_inflight"=>2}
[2017-06-12T14:52:18,279][INFO ][logstash.pipeline ] Pipeline .monitoring
-logstash started
[2017-06-12T14:52:18,513][INFO ][logstash.agent ] Successfully started
Logstash API endpoint {:port=>9600}
[2017-06-12T14:52:28,285][ERROR][logstash.inputs.metrics ] Failed to create mon
itoring event {:message=>"For path: events", :error=>"LogStash::Instrument::Metr
icStore::MetricNotFound"}

I tried everything, nothing effective. So a little help could be great.

Thanks in advance, and have a nice day !

2

The -f flag is for defining your config path and not your input files, like so

/bin/logstash -f /path/to/config_folder/

Try this and post any potential errors that should arise.

3

As indicated by the first line in the error message, host is no longer a valid parameter for the Elasticsearch output. If you look in the documentation you will see that is now supposed to be hosts instead. make sure you check against the correct version of the documentation if you are following old tutorials.

4

I fixed what you said. Same error.

[2017-06-12T15:15:58,515][ERROR][logstash.inputs.metrics ] Failed to create mon
itoring event {:message=>"For path: events", :error=>"LogStash::Instrument::Metr
icStore::MetricNotFound"}

5

Same answer as above.

6

Which version of Logstash are you using? Do you have X-Pack installed?

7

I've got the last version (5.4.0) with X-pack installed.

8

Have you added the required configuration to the logstash.yml file?

9

try:
output {
stdout { codec => rubydebug } }

elastisearch {
hosts => ["localhost:9200"]
...
}
try this two modify if send you error change localhost with your IP:9200.

10

Hi again !

I tried to reconfigure the .yml like Christian asked, but no, nothing changes.

11

I' thinking about one thing right now. In the YML of Logstash, should I remove the hashtags to apply the changes I've made with the required configuration ?

12

Can you share your logstash.yml file. Please make sure it is formatted as code.

13

Sure, there it is.

   # Settings file in YAML
    #
    # Settings can be specified either in hierarchical form, e.g.:
    #
    #   pipeline:
    #     batch:
    #       size: 125
    #       delay: 5
    #
    # Or as flat keys:
    #
    #   pipeline.batch.size: 125
    #   pipeline.batch.delay: 5
    #
    # ------------  Node identity ------------
    #
    # Use a descriptive name for the node:
    #
    # node.name: test
    #
    # If omitted the node name will default to the machine's host name
    #
    # ------------ Data path ------------------
    #
    # Which directory should be used by logstash and its plugins
    # for any persistent needs. Defaults to LOGSTASH_HOME/data
    #
    # path.data:
    #
    # ------------ Pipeline Settings --------------
    #
    # Set the number of workers that will, in parallel, execute the filters+outputs
    # stage of the pipeline.
    #
    # This defaults to the number of the host's CPU cores.
    #
    # pipeline.workers: 2
    #
    # How many workers should be used per output plugin instance
    #
    # pipeline.output.workers: 1
    #
    # How many events to retrieve from inputs before sending to filters+workers
    #
    # pipeline.batch.size: 125
    #
    # How long to wait before dispatching an undersized batch to filters+workers
    # Value is in milliseconds.
    #
    # pipeline.batch.delay: 5
    #
    # Force Logstash to exit during shutdown even if there are still inflight
    # events in memory. By default, logstash will refuse to quit until all
    # received events have been pushed to the outputs.
    #
    # WARNING: enabling this can lead to data loss during shutdown
    #
    # pipeline.unsafe_shutdown: false
    #
    # ------------ Pipeline Configuration Settings --------------
    #
    # Where to fetch the pipeline configuration for the main pipeline
    #
    # path.config:
    #
    # Pipeline configuration string for the main pipeline
    #
    # config.string:
    #
    # At startup, test if the configuration is valid and exit (dry run)
    #
    # config.test_and_exit: false
    #
    # Periodically check if the configuration has changed and reload the pipeline
    # This can also be triggered manually through the SIGHUP signal
    #
    # config.reload.automatic: false
    #
    # How often to check if the pipeline configuration has changed (in seconds)
    #
    # config.reload.interval: 3
    #
    # Show fully compiled configuration as debug log message
    # NOTE: --log.level must be 'debug'
    #
    # config.debug: false
    #
    # ------------ Queuing Settings --------------
    #
    # Internal queuing model, "memory" for legacy in-memory based queuing and
    # "persisted" for disk-based acked queueing. Defaults is memory
    #
    # queue.type: memory
    #
    # If using queue.type: persisted, the directory path where the data files will be stored.
    # Default is path.data/queue
    #
    # path.queue:
    #
    # If using queue.type: persisted, the page data files size. The queue data consists of
    # append-only data files separated into pages. Default is 250mb
    #
    # queue.page_capacity: 250mb
    #
    # If using queue.type: persisted, the maximum number of unread events in the queue.
    # Default is 0 (unlimited)
    #
    # queue.max_events: 0
    #
    # If using queue.type: persisted, the total capacity of the queue in number of bytes.
    # If you would like more unacked events to be buffered in Logstash, you can increase the
    # capacity using this setting. Please make sure your disk drive has capacity greater than
    # the size specified here. If both max_bytes and max_events are specified, Logstash will pick
    # whichever criteria is reached first
    # Default is 1024mb or 1gb
    #
    # queue.max_bytes: 1024mb
    #
    # If using queue.type: persisted, the maximum number of acked events before forcing a checkpoint
    # Default is 1024, 0 for unlimited
    #
    # queue.checkpoint.acks: 1024
    #
    # If using queue.type: persisted, the maximum number of written events before forcing a checkpoint
    # Default is 1024, 0 for unlimited
    #
    # queue.checkpoint.writes: 1024
    #
    # If using queue.type: persisted, the interval in milliseconds when a checkpoint is forced on the head page
    # Default is 1000, 0 for no periodic checkpoint.
    #
    # queue.checkpoint.interval: 1000
    #
    # ------------ Metrics Settings --------------
    #
    # Bind address for the metrics REST endpoint
    #
    # http.host: "127.0.0.1"
    #
    # Bind port for the metrics REST endpoint, this option also accept a range
    # (9600-9700) and logstash will pick up the first available ports.
    #
    # http.port: 9600-9700
    #
    # ------------ Debugging Settings --------------
    #
    # Options for log.level:
    #   * fatal
    #   * error
    #   * warn
    #   * info (default)
    #   * debug
    #   * trace
    #
    # log.level: info
    # path.logs:
    #
    # ------------ Other Settings --------------
    #
    # Where to find custom plugins
    # path.plugins: []
    #xpack.monitoring.elasticsearch.url: ["http://es-prod-node-1:9200", "http://es-prod-node-2:9200"] 
    #xpack.monitoring.elasticsearch.username: "elastic" 
    #xpack.monitoring.elasticsearch.password: "changeme"
14

None of that config will be used as it is all commented out, so you need to remove hashtags for the relevant parts.

15

Yeah it's what I thought. I'll fix that and I'll keep you posted.

16

Ok, there's progress ! I've touched the yml in more details, and no more big errors like before. Therefore,

[2017-06-14T15:01:18,111][ERROR][logstash.outputs.elasticsearch] Unknown setting
 'host' for elasticsearch
[2017-06-14T15:01:18,111][FATAL][logstash.runner          ] The given configurat
ion is invalid. Reason: Something is wrong with your configuration.

So I can see it's from the host option from the elastic search function, but i thought it was ok.

The output from my conf file :

output {
    stdout { codec => rubydebug }
    elasticsearch {
        host => ["https://127.0.0.1:9200"]
        index => "csv_index"
    }
}
17

The parameter should be 'hosts', not 'host'.

18 
Configuration OK
[2017-06-14T16:30:23,248][INFO ][logstash.runner          ] Using config.test_an
d_exit mode. Config Validation Result: OK. Exiting Logstash

And I don't have anything about Logstash in ElasticSearch's logs.

19

After installing xpac encounter this error:

[2017-06-14T15:11:13,598][ERROR][logstash.inputs.file ] Unknown setting 'user' for file
[2017-06-14T15:11:13,601][ERROR][logstash.inputs.file ] Unknown setting 'password' for file
[2017-06-14T15:11:13,608][ERROR][logstash.agent ] Cannot create pipeline {:reason=>"Something is wrong with your configuration."}

Any tips?

20

It's me again.

Next i disabled the "config.test_and_exit mode", I fall on a error next i launch the logstash command ( the pipeline is created first fyi)

It's kinda strange because it looks like the pipeline is operationnal, despite this error what appears to be in the plugin.

Any ideas ? And of course, thanks again for your help !