# Logstash exit with code 0

**URL:** <https://discuss.elastic.co/t/logstash-exit-with-code-0/279891>\
**Category:** Logstash\
**Tags:** docker\
**Created:** [July 28, 2021, 4:07pm UTC](https://discuss.elastic.co/t/logstash-exit-with-code-0/279891 "2021-07-28T16:07:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![abdo37](https://avatars.discourse-cdn.com/v4/letter/a/71c47a/32.png) [@abdo37](https://discuss.elastic.co/u/abdo37)\
**Post date:** [July 28, 2021, 4:07pm UTC](https://discuss.elastic.co/t/logstash-exit-with-code-0/279891/1 "2021-07-28T16:07:32Z")

</div>

heey i'm trynig to use docker-compose for logstash,elasticsearch,postgresql and when i start docker-compose all containers are working except logstash container it gives me logstash exit with code 0 there is my docker-compose.yml and my file.conf

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/8/48496feae7a89a8698e47a7380fd412a487562e9.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/0/d0d00668131ffc0708c75a47e792fa7128e7487f.png)  
thanks for any help

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 28, 2021, 11:22pm UTC](https://discuss.elastic.co/t/logstash-exit-with-code-0/279891/2 "2021-07-28T23:22:27Z")

</div>

Welcome to our community! 😃

Please don't post pictures of text or code. They are difficult to read, impossible to search and replicate (if it's code), and some people may not be even able to see them 🙂

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [July 29, 2021, 7:55am UTC](https://discuss.elastic.co/t/logstash-exit-with-code-0/279891/3 "2021-07-29T07:55:27Z")

</div>

in order to reduce complexity, first try running everything outside of a container. Does it work? Any error message that you are seeing? Can you share logs? Have you tried just parsing the config file? Does it work?

Thanks!

---

<div class="post-metadata">

**Author:** ![abdo37](https://avatars.discourse-cdn.com/v4/letter/a/71c47a/32.png) [@abdo37](https://discuss.elastic.co/u/abdo37)\
**Post date:** [July 29, 2021, 11:34am UTC](https://discuss.elastic.co/t/logstash-exit-with-code-0/279891/4 "2021-07-29T11:34:43Z")

</div>

thanks for replying,when i try to run outside a container everything works,nope no error message,but when i use containers it gives me logstash exit with code 0 there is my configuration files :  
docker-compose.yml

```auto
logstash: 
        image: logstash:7.13.4
        environment:
            - LOGSTASH_JDBC_URL=jdbc:postgresql://postgres:5432/test1
            - LOGSTASH_JDBC_DRIVER=org.postgresql.Driver
            - LOGSTASH_JDBC_DRIVER_JAR_LOCATION=/usr/share/logstash/logstash-core/lib/jars/postgresql.jar
            - LOGSTASH_JDBC_USERNAME=postgres
            - LOGSTASH_JDBC_PASSWORD=postgres
            - LOGSTASH_ELASTICSEARCH_HOST=http://elasticsearch:9200
        volumes: 
            - ./logstashconfig/logstash.yml:/usr/share/logstash/config/logstash.yml
            - ./logstashconfig/:/usr/share/logstash/pipeline/
            - ./filesconfig/:/usr/share/logstash/pipeline/
            - ./jars/postgresql-42.2.22.jar:/usr/share/logstash/logstash-core/lib/jars/postgresql-42.2.22.jar
                       
                # - type: bind
                # source: ./logstashconfig/
                # target: /usr/share/logstash/pipeline/ 
                # - type: bind
                # #can be either a host path or volume name.
                # source: ./logstashconfig/piplines.yml
                # #is the container path where the volume is mounted
                # target: /usr/share/logstash/pipeline/piplines.yml
                # read_only: true
        ports:   
        
        - "5000:5000"
        
        depends_on: 
            - postgres 
            - elasticsearch

```

and :

file2.conf

```auto
input { 
   tcp{
        port=> "9600"
    }

jdbc {
jdbc_connection_string =>
"jdbc:postgresql://postgres:5432/test1"
jdbc_user => "postgres"
jdbc_password => "postgres"
jdbc_driver_library => "/usr/share/logstash/logstash-core/lib/jars/postgresql-42.2.22.jar"
jdbc_driver_class =>"org.postgresql.Driver"
schedule => "* * * * *"
statement => "select email,id from public."test" " 
}
stdin { } }
output {
  elasticsearch { hosts => ["elasticsearch:9200"] 
  index => "test"
  document_id => "test_%{id}"
  

}
  stdout { codec => rubydebug }
}

```

and :  
logstash.yml

```auto
## Default Logstash configuration from Logstash base image.
## https://github.com/elastic/logstash/blob/master/docker/data/logstash/config/logstash-full.yml
#
http.host: "0.0.0.0"
xpack.monitoring.elasticsearch.hosts: ["http://elasticsearch:9200"]
## X-Pack security credentials
#
#xpack.monitoring.enabled: true
#xpack.monitoring.elasticsearch.username: elastic
#xpack.monitoring.elasticsearch.password: changeme
# Settings file in YAML

```

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [August 2, 2021, 7:25am UTC](https://discuss.elastic.co/t/logstash-exit-with-code-0/279891/5 "2021-08-02T07:25:39Z")

</div>

please share your complete configuration in a gist. Maybe you are missing network configuration in your docker compose files, it's hard to tell without seeing the full setup.

---

<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:** [August 30, 2021, 7:25am UTC](https://discuss.elastic.co/t/logstash-exit-with-code-0/279891/6 "2021-08-30T07:25:42Z")

</div>

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