Logstash service don't work

[Sam67000 (Samir)]

Hello,

I have installed logstash as a service (rpm). But when I start the logstash service he doesn't send me anything to elasticsearch.

I try to lauch logstash in /usr/share/logstash/bin and it works fine.

What is strange is that when I check my processor, logstash consumes cpu. But I don't know what ho doing !

Someone can help ?

[blackOcean (Sagar Rout)]

Hi Samir,

Please post your configuration file in the forum. It will be very helpful for everyone.

[Sam67000 (Samir)]

Ok. Here is my logstash config file :

# 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: /var/lib/logstash
#
# ------------ 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: /etc/logstash/conf.d
#
# 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: /var/log/logstash
#
# ------------ Other Settings --------------
#
# Where to find custom plugins
# path.plugins: []

[Sam67000 (Samir)]

And here is my file.conf :

input { 
   beats {
          port => 5044
         }
      }

filter  {

grok {
        break_on_match => false
	match => {"message" => "(.*?)(?<ConnID>[0-9a-f]{16})(.*)" }
	match => {"message" => "^%{TIMESTAMP_ISO8601:event_timestamp}"}
	match => { "message" => "(.*?)(AttributeCallUUID\t)'(?<CallUUID>[0-9A-Z]{32})(.*)" }
	match => {"message" => "iReturn\(LOCAL\) <- INTEGER: %{NUMBER:Return}"}
	  }
grok {
        match => {"message" => "(?<Suivi>(?:^|\n)[^\n]*send\sto\sts[^\n]*(?:\n|$))"}
        add_tag => ["Parsed"]
        }
date  {
          match => ["event_timestamp","YYYY-MM-dd'T'HH:mm:ss.SSS"]
          target => "@timestamp"
          locale => "en"
          timezone => "Europe/Paris"
         }
if "Parsed" not in [tags] {
		drop {}
                            }

output  {  
	 elasticsearch {
	         		 hosts => ["10.58.123.222:9200"]
	                 manage_template => false
	                 index => "cofbe-%{+YYYY.MM.dd}"
	                 }
        }

When I run this configuration file with the following command it works very well.
It's just when I run logstash as a service that it does nothing at all.