Logstash binary as service is not running on CentOS 7 - SOLVED

Elastic Stack Logstash
1

Dear All,

I have installed latest logstash for CentOS 7 as per the official documents. When i run logstash

sudo service logstash start

It just doesn't work , no log files (even if i set the log level as debug in logstash.yml) nothing in /var/log/logstash/logstash-plain.log.

However if i run it like below
#sudo bin/logstash --path.settings /etc/logstash -f /etc/logstash/conf.d/01-twitter.conf
it works fine and start generating the logs. Seems some issue with starting logstash as service?
Can someone please help.

2

What was the problem ? I'm in the same case.

3

samir I had issues in the conf file i created. If you are having issues paste your config file here and I will be able to advise you.

4

ok thank you. 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: []
5

Hi,

I do not need logstash config but need to see the .conf file you have created in /etc/logstash/conf.d

6

Ah ok sorry.

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.

7

can you please share the logstash logs as well? please do run the logstash as service and then do a tail -f /var/log/logstash/logstash-plain

8

I have run logstash as service but my logstash-plain file is empty ! there is nothing.
One strange thing is when I check the use of my CPU, logstash consumes a lot !! But I don't receive anything on Elasticsearch.

9

give it 10 minutes to start showing the logs also the service you are collecting logs for make sure its generating the events

10

Always nothing.

11

you sure user logstash have the permission to the file you are collecting the log from?

12

Yes I just check. it has access to all files

13

how did you give the access to logstash user ? can you show me the output of

ls -l

14

Here is the output of ls -l for /etc/logstash :

drwxrwxrwx 2 logstash root 4096 Jul  5 11:56 conf.d
-rw-r--r-- 1 root     root 1738 May 29 18:41 jvm.options
-rw-r--r-- 1 root     root 1334 May 29 18:41 log4j2.properties
-rw-r--r-- 1 root     root 4484 Jul  4 14:57 logstash.yml
-rw-r--r-- 1 root     root 1658 Jul  3 15:38 startup.options

for /etc/logstash/conf.d :

 -rwxrwxrwx 1 logstash root 4484 Jul  4 14:58 logstash.yml
 -rwxrwxrwx 1 logstash root 9914 Jul  4 17:02 URS2.conf

for /usr/share/logstash : 

drwxr-xr-x 2 logstash logstash   4096 Jul  5 11:38 bin
-rw-r--r-- 1 logstash logstash 111573 May 29 18:41 CHANGELOG.md
-rw-r--r-- 1 logstash logstash   2249 May 29 18:41 CONTRIBUTORS
drwxrwxr-x 4 logstash logstash   4096 Jun  6 14:04 data
-rw-r--r-- 1 logstash logstash   3851 Jun 15 16:18 Gemfile
-rw-r--r-- 1 logstash logstash  21372 Jun  2 13:19 Gemfile.jruby-1.9.lock
drwxr-xr-x 5 logstash logstash   4096 Jun  2 11:55 lib
-rw-r--r-- 1 logstash logstash    589 May 29 18:41 LICENSE
drwxr-xr-x 4 logstash logstash   4096 Jun  2 13:19 logstash-core
drwxr-xr-x 3 logstash logstash   4096 Jun  2 11:55 logstash-core-plugin-api
-rw-r--r-- 1 logstash logstash  28114 May 29 18:41 NOTICE.TXT
drwxr-xr-x 4 logstash logstash   4096 Jun  2 11:55 vendor
15

please read what i have asked for .... I wanted to know the permissions of the file you are collecting the event. For example if you are collecting the apache error log events then you need to show me the permissions of /var/log/httpd/error_log ...

16

I collecte logs that are on a remote windows server and that I send with filebeat to the logstash server. But when I run logstash with the command logstash -f file.conf it works fine so i guess it has the permissions. Otherwise I don't see how to check exactly.

17

can you please add
stdout { codec => rubydebug }
}
in output section and restart logstash and see if it generates any log. Also make sure in logstash,yml the log level set to debug

18

My log level is Info (default).

I add stdout { codec => rubydebug } in output, and restart logstash as a service. But there generate nothing. They just told me that logstash is running.

I check logstash-plain.log and also nothing.

19

change the log level to debug and restart logstash

20

Nothing change ...