# Help on: Error creating runner from config: Can only start an input when all related states are finished

**URL:** <https://discuss.elastic.co/t/help-on-error-creating-runner-from-config-can-only-start-an-input-when-all-related-states-are-finished/176240>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 10, 2019, 2:28pm UTC](https://discuss.elastic.co/t/help-on-error-creating-runner-from-config-can-only-start-an-input-when-all-related-states-are-finished/176240 "2019-04-10T14:28:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bikoumba](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bikoumba/32/43875_2.png) [@bikoumba](https://discuss.elastic.co/u/bikoumba)\
**Post date:** [April 10, 2019, 2:28pm UTC](https://discuss.elastic.co/t/help-on-error-creating-runner-from-config-can-only-start-an-input-when-all-related-states-are-finished/176240/1 "2019-04-10T14:28:14Z")

</div>

Hello,

I have an issue with my filebeat configuration. I have an api running on k8s, logs are written to stdout and requests-logs to stderr in order to get them both in my ES Cluster.  
I m using filebeat 6.7.1 OSS with autodicovery (to work with AWS ElasticSearch). In my config I have defined one kubernetes provider with 2 docker type templates:

```auto
filebeat.autodiscover:
      providers:
        - type: kubernetes
          templates:
            - condition:
                equals:
                  kubernetes.labels.team: pipeline
              config:
                - type: docker
                  containers.ids:
                    - "${data.kubernetes.container.id}"
                  containers.stream: stdout
                  pipeline: java_application
                  tags: ["application"]
                  # any line not starting with know log levels match multiline pattern
                  multiline.pattern: "^[FEWIDT]+"
                  multiline.negate: true
                  multiline.match: after
                  exclude_lines: "^[^FEWIDT].*$"
                  processors:
                  - dissect:
                      tokenizer: "%{level} [%{timestamp}] %{classpath}: %{message}"
                      field: "message"
                      target_prefix: "ingest"
            - condition:
                equals:
                  kubernetes.labels.team: pipeline
              config:
                - type: docker
                  containers.ids:
                    - "${data.kubernetes.container.id}"
                  containers.stream: stderr
                  pipeline: http_requests
                  tags: ["requests"]
                  processors:
                  - dissect:
                      tokenizer: '[%{timestamp}] %{client_ip} "%{method} %{path} %{?http_version}" %{status} %{response_size} %{response_time}'
                      field: "message"
                      target_prefix: "http"

processors:
      - add_cloud_metadata: ~

output.elasticsearch:
      hosts: ['${ELASTICSEARCH_HOST}:${ELASTICSEARCH_PORT}']
      indices:
        - index: "logs-filebeat-%{[beat.version]}-%{+yyyy.MM.dd}"
          when:
            contains:
              tags: application
        - index: "requests-filebeat-%{[beat.version]}-%{+yyyy.MM.dd}"
          when:
            contains:
              tags: requests

```

This configuration seems to work but after a short time filebeat stop reporting logs to ES and show this error:  
`Error creating runner from config: Can only start an input when all related states are finished`  
I found an explanation to this error, filebeat has the same file open twice but I need to do this to read stdout and stderr to process either application and requests logs with a different dissect processor, multiline configuration and writing to different indexes in ES. Does anyone knows how to do this?

---

<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:** [May 8, 2019, 2:28pm UTC](https://discuss.elastic.co/t/help-on-error-creating-runner-from-config-can-only-start-an-input-when-all-related-states-are-finished/176240/2 "2019-05-08T14:28:25Z")

</div>

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