# Logstash server not starting on system reboot

**URL:** <https://discuss.elastic.co/t/logstash-server-not-starting-on-system-reboot/122008>\
**Category:** Logstash\
**Created:** [March 1, 2018, 9:22am UTC](https://discuss.elastic.co/t/logstash-server-not-starting-on-system-reboot/122008 "2018-03-01T09:22:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dennis.1157](https://avatars.discourse-cdn.com/v4/letter/d/dfb087/32.png) [@dennis.1157](https://discuss.elastic.co/u/dennis.1157)\
**Post date:** [March 1, 2018, 9:22am UTC](https://discuss.elastic.co/t/logstash-server-not-starting-on-system-reboot/122008/1 "2018-03-01T09:22:16Z")

</div>

I have the ELK stack installed on Ubuntu 14.04.

Everything works when I run Logstash from the command line but as a service, the server does not seem to be able to start by itself. Here's the log from `/var/log/logstash/logstash-plain.log` (all logs were deleted and the host was restarted):

```
[INFO][logstash.modules.scaffold] Initializing module {:module_name=>"netflow", :directory=>"/usr/share/logstash/modules/netflow/configuration"}
[INFO][logstash.modules.scaffold] Initializing module {:module_name=>"fb_apache", :directory=>"/usr/share/logstash/modules/fb_apache/configuration"}
[WARN][logstash.config.source.multilocal] Ignoring the 'pipelines.yml' file because modules or command line options are specified
[INFO][logstash.runner] Starting Logstash {"logstash.version"=>"6.1.2"}
[INFO][logstash.agent] Successfully started Logstash API endpoint {:port=>9600}

```

A telnet to `localhost:5044` returns:

```
$ telnet localhost 5044
Trying 127.0.0.1...
Trying ::1...
telnet: Unable to connect to remote host: Cannot assign requested address

```

1. Why is Logstash not using my pipeline config in `/etc/logstash/conf.d`?
2. How do I get the service to start the Logstash server that runs on port 5044?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [March 1, 2018, 10:36am UTC](https://discuss.elastic.co/t/logstash-server-not-starting-on-system-reboot/122008/2 "2018-03-01T10:36:41Z")

</div>

What's in /etc/logstash/logstash.yml (format the file' contents as preformatted text when you post it)? What does Logstash's command line look like (check with `ps aux | grep logstash`)?

---

<div class="post-metadata">

**Author:** ![dennis.1157](https://avatars.discourse-cdn.com/v4/letter/d/dfb087/32.png) [@dennis.1157](https://discuss.elastic.co/u/dennis.1157)\
**Post date:** [March 2, 2018, 3:34am UTC](https://discuss.elastic.co/t/logstash-server-not-starting-on-system-reboot/122008/3 "2018-03-02T03:34:50Z")

</div>

`/etc/logstash/logstash.yml`:

```
# pipeline:
# batch:
# size: 125
# delay: 5
#
# Or as flat keys:
#
# pipeline.batch.size: 125
# pipeline.batch.delay: 5
#
#
#
# node.name: test
#
#
path.data: /var/lib/logstash
#
# pipeline.workers: 2
#
#
# pipeline.output.workers: 1
#
#
# pipeline.batch.size: 125
#
#
# pipeline.batch.delay: 5
#
#
#
# pipeline.unsafe_shutdown: false
#
path.config: /etc/logstash/conf.d/*.conf
#
# 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: true
#
# How often to check if the pipeline configuration has changed (in seconds)
#
# config.reload.interval: 3s
#
# Show fully compiled configuration as debug log message
# NOTE: --log.level must be 'debug'
#
# config.debug: false
#
# When enabled, process escaped characters such as \n and \" in strings in the
# pipeline configuration files.
#
# config.support_escapes: false
#
# Define modules here. Modules definitions must be defined as an array.
# The simple way to see this is to prepend each `name` with a `-`, and keep
# all associated variables under the `name` they are associated with, and
# above the next, like this:
#
# modules:
# - name: MODULE_NAME
# var.PLUGINTYPE1.PLUGINNAME1.KEY1: VALUE
# var.PLUGINTYPE1.PLUGINNAME1.KEY2: VALUE
# var.PLUGINTYPE2.PLUGINNAME1.KEY1: VALUE
# var.PLUGINTYPE3.PLUGINNAME3.KEY1: VALUE
#
# Module variable names must be in the format of
#
# var.PLUGIN_TYPE.PLUGIN_NAME.KEY
#
# modules:
#
# Define Elastic Cloud settings here.
# Format of cloud.id is a base64 value e.g. dXMtZWFzdC0xLmF3cy5mb3VuZC5pbyRub3RhcmVhbCRpZGVudGlmaWVy
# and it may have an label prefix e.g. staging:dXMtZ...
# This will overwrite 'var.elasticsearch.hosts' and 'var.kibana.host'
# cloud.id: <identifier>
#
# Format of cloud.auth is: <user>:<pass>
# This is optional
# If supplied this will overwrite 'var.elasticsearch.username' and 'var.elasticsearch.password'
# If supplied this will overwrite 'var.kibana.username' and 'var.kibana.password'
# cloud.auth: elastic:<password>
#
#
# 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
#
# Flag to turn on dead-letter queue.
#
# dead_letter_queue.enable: false

# If using dead_letter_queue.enable: true, the maximum size of each dead letter queue. Entries
# will be dropped if they would increase the size of the dead letter queue beyond this setting.
# Default is 1024mb
# dead_letter_queue.max_bytes: 1024mb

# If using dead_letter_queue.enable: true, the directory path where the data files will be stored.
# Default is path.data/dead_letter_queue
#
# path.dead_letter_queue:
#
# 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
#
# Options for log.level:
# * fatal
# * error
# * warn
# * info (default)
# * debug
# * trace
#
# log.level: info
path.logs: /var/log/logstash
#
# Where to find custom plugins
# path.plugins: []

```

`ps aux | grep logstash`:

```
/usr/bin/java -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+DisableExplicitGC -Djava.awt.headless=true -Dfile.encoding=UTF-8 -XX:+HeapDumpOnOutOfMemoryError -Xmx1g -Xms256m -Xss2048k -Djffi.boot.library.path=/usr/share/logstash/vendor/jruby/lib/jni -Xbootclasspath/a:/usr/share/logstash/vendor/jruby/lib/jruby.jar -classpath : -Djruby.home=/usr/share/logstash/vendor/jruby -Djruby.lib=/usr/share/logstash/vendor/jruby/lib -Djruby.script=jruby -Djruby.shell=/bin/sh org.jruby.Main /usr/share/logstash/lib/bootstrap/environment.rb logstash/runner.rb --path.settings /etc/logstash
```

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [March 2, 2018, 6:57am UTC](https://discuss.elastic.co/t/logstash-server-not-starting-on-system-reboot/122008/4 "2018-03-02T06:57:16Z")

</div>

Okay, so it looks like it should be loading your configuration files. What's in those files (`cat /etc/logstash/conf.d/*.conf`)? If you increase the logging verbosity to debug Logstash will log the exact configuration it loads.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 30, 2018, 10:19am UTC](https://discuss.elastic.co/t/logstash-server-not-starting-on-system-reboot/122008/6 "2018-03-30T10:19:52Z")

</div>

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