# Issue of Configuring in Logstash

**URL:** https://discuss.elastic.co/t/issue-of-configuring-in-logstash/294387
**Category:** Logstash
**Created:** [January 14, 2022, 9:13am UTC](https://discuss.elastic.co/t/issue-of-configuring-in-logstash/294387 "2022-01-14T09:13:52Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![leyleynewt](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@leyleynewt](https://discuss.elastic.co/u/leyleynewt)
#### Post date: [January 14, 2022, 9:13am UTC](https://discuss.elastic.co/t/issue-of-configuring-in-logstash/294387/1 "2022-01-14T09:13:52Z")

</div>

This is the configuration in logstash-sample.conf:

```auto
input{
	stdin{}      
}
output{
        elasticsearch{
                hosts => ["localhost:9200"]
                index => "my-index-name"
		user => "elastic"
		password => "changeme"
        }
        file{
                path => "/etc/logstash/conf.d/logstash-sample-output"
    }
       stdout {

	 }
}

```

This is the configuration in the pipeline.conf file:

```auto
- pipeline.id: main
  path.config: "/etc/logstash/conf.d/*.conf"

```

When I run this command:

```auto
/usr/share/logstash/bin/logstash -f logstash-sample.conf

```

This is the log:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/a/8a0eadc98e20d1f09aeb9e76335bcfaff4c71ebe.png)

The expected output which is the index name is (my-index-name)  
should be reflected in Kibana Dashboard Index Management:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/4/d40b70949a099c8bec9aa49bcf1ab1a00a3dabcc.png)

How to resolve this issue?

---

<div class="post-metadata">

### Author: ![Tomo\_M](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@Tomo\_M](https://discuss.elastic.co/u/Tomo_M)
#### Post date: [January 14, 2022, 9:30am UTC](https://discuss.elastic.co/t/issue-of-configuring-in-logstash/294387/2 "2022-01-14T09:30:32Z")

</div>

Hi,

The log says another logstash sharing the same "path.data" setting.

---

<div class="post-metadata">

### Author: ![leyleynewt](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@leyleynewt](https://discuss.elastic.co/u/leyleynewt)
#### Post date: [January 14, 2022, 9:37am UTC](https://discuss.elastic.co/t/issue-of-configuring-in-logstash/294387/3 "2022-01-14T09:37:16Z")

</div>

Hello! This is our logstash.yml file:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/4/74f0b2f50d26faae12f6c984c8b915ae2a220fb6.png)

---

<div class="post-metadata">

### Author: ![Tomo\_M](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@Tomo\_M](https://discuss.elastic.co/u/Tomo_M)
#### Post date: [January 14, 2022, 9:39am UTC](https://discuss.elastic.co/t/issue-of-configuring-in-logstash/294387/4 "2022-01-14T09:39:15Z")

</div>

There may be two ways.

1. change the path.data, or
2. stop another logstash instance using the same path.data path.

---

<div class="post-metadata">

### Author: ![leyleynewt](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@leyleynewt](https://discuss.elastic.co/u/leyleynewt)
#### Post date: [January 14, 2022, 10:38am UTC](https://discuss.elastic.co/t/issue-of-configuring-in-logstash/294387/5 "2022-01-14T10:38:21Z")

</div>

Hello, I run this command to pass path.setting:

```auto
/usr/share/logstash/bin/logstash --path.settings /etc/logstash/ -f logstash-sample.conf 

```

and this is the log:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/9/f96d554aad8a9e9a030aa36ddda5ba957319643e.png)

---

<div class="post-metadata">

### Author: ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [January 14, 2022, 1:13pm UTC](https://discuss.elastic.co/t/issue-of-configuring-in-logstash/294387/6 "2022-01-14T13:13:51Z")

</div>

Your log is saying that you have another logstash running in your server, you need to check that and stopped the other instance.

---

<div class="post-metadata">

### Author: ![grumo35](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grumo35/32/59451_2.png) [@grumo35](https://discuss.elastic.co/u/grumo35)
#### Post date: [January 14, 2022, 1:30pm UTC](https://discuss.elastic.co/t/issue-of-configuring-in-logstash/294387/7 "2022-01-14T13:30:27Z")

</div>

ps -aux | grep "logstash" Will show running instances.

You should make it as a systemd service or try a init / kill script that catch the PID.

---

<div class="post-metadata">

### Author: ![leyleynewt](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@leyleynewt](https://discuss.elastic.co/u/leyleynewt)
#### Post date: [January 18, 2022, 2:16am UTC](https://discuss.elastic.co/t/issue-of-configuring-in-logstash/294387/8 "2022-01-18T02:16:07Z")

</div>

Hello @grumo35 , Thank you issue is resolved!!!  
**Steps:**

1. Show running instances.

```auto
ps -aux | grep logstash

```

1. Kill running instances.

```auto
Kill -9 <PID>

```

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/3/838fc3f763a0308b5c17b6c9eaa62e16d0488b5d.jpeg)

**Additional Information:**  
You could pass the path.settings in the CLI with this command:

```auto
/usr/share/logstash/bin/logstash --path.settings /etc/logstash/ -f logstash-sample.conf 

```

---

<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: [February 15, 2022, 2:16am UTC](https://discuss.elastic.co/t/issue-of-configuring-in-logstash/294387/9 "2022-02-15T02:16:55Z")

</div>

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