# Logstash 6.5.4 does not output to output file

**URL:** <https://discuss.elastic.co/t/logstash-6-5-4-does-not-output-to-output-file/167084>\
**Category:** Logstash\
**Created:** [February 5, 2019, 9:04am UTC](https://discuss.elastic.co/t/logstash-6-5-4-does-not-output-to-output-file/167084 "2019-02-05T09:04:40Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexas](https://avatars.discourse-cdn.com/v4/letter/a/58956e/32.png) [@Alexas](https://discuss.elastic.co/u/Alexas)\
**Post date:** [February 5, 2019, 9:04am UTC](https://discuss.elastic.co/t/logstash-6-5-4-does-not-output-to-output-file/167084/1 "2019-02-05T09:04:41Z")

</div>

Hello!  
I have an installed version of logstash.version "=\>" 6.5.4 "

I start logstash: sudo initctl start logstash  
I want to execute the script recorded in the file 777.conf  
input {file {path =\> "/ home / sonic / log / vs01 / test\_new.log" start\_position =\> "beginning" ignore\_older =\> 0 sincedb\_path =\> "/ dev / null"}} output {file {path =\> " /home/sonic/log/vs01/test\_out.log "}}

There are no errors in the logstash-plain.log file with the installed parameter --log.level debug.  
When adding entries to test\_new.log in the test\_out.log file, no changes occur.

If I run logstash:  
cd / usr / share / logstash /  
bin / logstash -e 'input {file {path =\> "/ home / sonic / log / vs01 / test\_new.log" start\_position =\> "beginning" ignore\_older =\> 0 sincedb\_path =\> "/ dev / null"}} output { file {path =\> "/ home / sonic / log / vs01 / test\_out.log"}} '  
Everything works well.

What could be the problem?

---

<div class="post-metadata">

**Author:** ![reschenburg](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@reschenburg](https://discuss.elastic.co/u/reschenburg)\
**Post date:** [February 5, 2019, 10:34am UTC](https://discuss.elastic.co/t/logstash-6-5-4-does-not-output-to-output-file/167084/2 "2019-02-05T10:34:44Z")

</div>

> [@Alexas](#):
>
> 777.conf

assuming this file is what contains your input/output logstash config? where have you put that file in the filesystem in relation to your logstash directory?

---

<div class="post-metadata">

**Author:** ![Alexas](https://avatars.discourse-cdn.com/v4/letter/a/58956e/32.png) [@Alexas](https://discuss.elastic.co/u/Alexas)\
**Post date:** [February 6, 2019, 5:35am UTC](https://discuss.elastic.co/t/logstash-6-5-4-does-not-output-to-output-file/167084/3 "2019-02-06T05:35:45Z")

</div>

/etc/logstash/conf.d/777.conf

From the logstash-plain.log file you can see that the inputs file and the outputs file are defined.

[2019-02-05T10:08:06,916][DEBUG][logstash.inputs.file] config LogStash::Inputs::File/@path = ["/home/sonic/log/vs01/test\_new.log"]  
[2019-02-05T10:08:07,017][DEBUG][logstash.outputs.file] config LogStash::Outputs::File/@path = "/home/sonic/log/vs01/test\_out.log"

Sonic user under which I work does not have admin rights on Linux. Maybe a problem with the rights?

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [February 6, 2019, 1:49pm UTC](https://discuss.elastic.co/t/logstash-6-5-4-does-not-output-to-output-file/167084/4 "2019-02-06T13:49:06Z")

</div>

> [@Alexas](#):
>
> ignore\_older =\> 0

This says to ignore files that are more than zero seconds old. Probably not what you want.

---

<div class="post-metadata">

**Author:** ![Alexas](https://avatars.discourse-cdn.com/v4/letter/a/58956e/32.png) [@Alexas](https://discuss.elastic.co/u/Alexas)\
**Post date:** [February 7, 2019, 8:10am UTC](https://discuss.elastic.co/t/logstash-6-5-4-does-not-output-to-output-file/167084/5 "2019-02-07T08:10:00Z")

</div>

Hello!

I have already tried to remove this parametr does not help. If you run logstash via bin / logstash -e 'input ....., then everything works with "ignore\_older =\> 0".  
The difference is that when you run through bin / logstash -e 'input some files are not found  
WARNING: Could not find logstash.yml which is typically located in $ LS\_HOME / config or / etc / logstash. You can specify the path using --path.settings. Continuing using the defaults  
Could not find log4j2 configuration at path /usr/share/logstash/config/log4j2.properties. Using default config which logs errors to the console  
[WARN] 2019-02-07 08: 47: 03.377 [LogStash :: Runner] multilocal - Ignoring the 'pipelines.yml'

I tried to remove the logstash.yml and log4j2 configuration files anyway when you start the "sudo initctl start logstash" changes are not displayed in the Outputs file.

---

<div class="post-metadata">

**Author:** ![Alexas](https://avatars.discourse-cdn.com/v4/letter/a/58956e/32.png) [@Alexas](https://discuss.elastic.co/u/Alexas)\
**Post date:** [February 18, 2019, 5:39am UTC](https://discuss.elastic.co/t/logstash-6-5-4-does-not-output-to-output-file/167084/6 "2019-02-18T05:39:03Z")

</div>

Hello!

Any thoughts on how to solve this problem?

---

<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 18, 2019, 5:39am UTC](https://discuss.elastic.co/t/logstash-6-5-4-does-not-output-to-output-file/167084/7 "2019-03-18T05:39:04Z")

</div>

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