# In RHEL how to run Configuration file along with logstash?

**URL:** <https://discuss.elastic.co/t/in-rhel-how-to-run-configuration-file-along-with-logstash/121479>\
**Category:** Logstash\
**Created:** [February 26, 2018, 12:04pm UTC](https://discuss.elastic.co/t/in-rhel-how-to-run-configuration-file-along-with-logstash/121479 "2018-02-26T12:04:01Z")\
**Posts on this page:** 5\
**Page:** 3

<div class="post-metadata">

**Author:** ![naveen\_K.N](https://avatars.discourse-cdn.com/v4/letter/n/8e8cbc/32.png) [@naveen\_K.N](https://discuss.elastic.co/u/naveen_K.N)\
**Post date:** [March 20, 2018, 3:49am UTC](https://discuss.elastic.co/t/in-rhel-how-to-run-configuration-file-along-with-logstash/121479/41 "2018-03-20T03:49:20Z")

</div>

Hi @Suman_Reddy1

pipelines.yml file is as follows:

* * *

#List of pipelines to be loaded by Logstash

# 

#This document must be a list of dictionaries/hashes, where the keys/values are pipeline settings.  
#Default values for ommitted settings are read from the `logstash.yml` file.  
#When declaring multiple pipelines, each MUST have its own `pipeline.id`.

# 

#Example of two pipelines:

# 

- pipeline.id: test  
pipeline.workers: 2  
pipeline.batch.size: 1  
path.config: "C:\Users\nakn\Downloads\logstash-6.1.1\bin\config\logs-server.conf"  
#config.string: "input { generator {} } filter { sleep { time =\> 1 } } output { stdout { codec =\> dots } }"  
#- pipeline.id: another\_test  
#queue.type: persisted  
#path.config: "/tmp/logstash/\*.config"

# 

#Available options:

# 

##name of the pipeline  
#pipeline.id: mylogs

# 

##The configuration string to be used by this pipeline  
#config.string: "input { generator {} } filter { sleep { time =\> 1 } } output { stdout { codec =\> dots } }"

# 

##The path from where to read the configuration text  
#path.config: "C:\Users\nakn\Downloads\logstash-6.1.1\config\logs-server.conf"

# 

#How many worker threads execute the Filters+Outputs stage of the pipeline  
#pipeline.workers: 1 (actually defaults to number of CPUs)

# 

##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  
#pipeline.batch.delay: 5

# 

#How many workers should be used per output plugin instance  
#pipeline.output.workers: 1

# 

#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 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.  
#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

# 

#Enable Dead Letter Queueing for this pipeline.  
#dead\_letter\_queue.enable: false

# 

#If using dead\_letter\_queue.enable: true, the maximum size of dead letter queue for this pipeline. 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:

* * *

Thanks,  
Naveena

---

<div class="post-metadata">

**Author:** ![Suman\_Reddy1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suman_reddy1/32/27303_2.png) [@Suman\_Reddy1](https://discuss.elastic.co/u/Suman_Reddy1)\
**Post date:** [March 20, 2018, 11:04am UTC](https://discuss.elastic.co/t/in-rhel-how-to-run-configuration-file-along-with-logstash/121479/42 "2018-03-20T11:04:55Z")

</div>

It seems ok to me. I am not so sure why it is failing to start.

---

<div class="post-metadata">

**Author:** ![naveen\_K.N](https://avatars.discourse-cdn.com/v4/letter/n/8e8cbc/32.png) [@naveen\_K.N](https://discuss.elastic.co/u/naveen_K.N)\
**Post date:** [March 20, 2018, 11:21am UTC](https://discuss.elastic.co/t/in-rhel-how-to-run-configuration-file-along-with-logstash/121479/43 "2018-03-20T11:21:25Z")

</div>

Thanks suman for U r kind information!

---

<div class="post-metadata">

**Author:** ![Suman\_Reddy1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suman_reddy1/32/27303_2.png) [@Suman\_Reddy1](https://discuss.elastic.co/u/Suman_Reddy1)\
**Post date:** [March 20, 2018, 2:51pm UTC](https://discuss.elastic.co/t/in-rhel-how-to-run-configuration-file-along-with-logstash/121479/44 "2018-03-20T14:51:52Z")

</div>

Aaaah, how did I missed it.  
`path.config: "C:\Users\nakn\Downloads\logstash-6.1.1\bin\config\logs-server.conf"`  
it should be  
`path.config: "C:\\Users\\nakn\\Downloads\\logstash-6.1.1\\bin\\config\\logs-server.conf"`  
Hell with windows

---

<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:** [April 17, 2018, 2:52pm UTC](https://discuss.elastic.co/t/in-rhel-how-to-run-configuration-file-along-with-logstash/121479/45 "2018-04-17T14:52:04Z")

</div>

Closed on April 17, 2018, 2:52pm UTC

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

[Previous page](https://discuss.elastic.co/t/in-rhel-how-to-run-configuration-file-along-with-logstash/121479.md?page=2)
