# Filebeat 6.2.3: Unable to create runner due to error: Can only start a prospector when all related states are finished: {Id: Finished:false Fileinfo:0xc420196b60 Source:/var/log/nginx/access.log

**URL:** <https://discuss.elastic.co/t/filebeat-6-2-3-unable-to-create-runner-due-to-error-can-only-start-a-prospector-when-all-related-states-are-finished-id-finished-false-fileinfo-0xc420196b60-source-var-log-nginx-access-log/129455>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 25, 2018, 10:31am UTC](https://discuss.elastic.co/t/filebeat-6-2-3-unable-to-create-runner-due-to-error-can-only-start-a-prospector-when-all-related-states-are-finished-id-finished-false-fileinfo-0xc420196b60-source-var-log-nginx-access-log/129455 "2018-04-25T10:31:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nacesprin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nacesprin/32/30024_2.png) [@nacesprin](https://discuss.elastic.co/u/nacesprin)\
**Post date:** [April 25, 2018, 10:31am UTC](https://discuss.elastic.co/t/filebeat-6-2-3-unable-to-create-runner-due-to-error-can-only-start-a-prospector-when-all-related-states-are-finished-id-finished-false-fileinfo-0xc420196b60-source-var-log-nginx-access-log/129455/1 "2018-04-25T10:31:48Z")

</div>

Filebeat 6.2.3  
Error on /var/log/filebeat/filebeat

`Unable to create runner due to error: Can only start a prospector when all related states are finished: {Id: Finished:false Fileinfo:0xc420196b60 Source:/var/log/nginx/access.log Offset:169527 Timestamp:2018-04-25 12:22:05.087086821 +0200 CEST m=+932.461573499 TTL:-1ns Type:log FileStateOS:39185-2048}`

filebeat config:

```
- type: log

  enabled: true

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - /var/log/*.log
    - /var/log/nginx/*.log
    - /var/log/elasticsearch/*.log
  tags: ["sistema"]

```

Only generate errors for all files under /var/log/nginx/\*.log  
If I remove /var/log/nginx/error.log, then get error with /var/log/nginx/access.log and so on

Why only fails under nginx logs?

Note: I've installed on all client servers and not errors found, but when filebeat is installed on the same ELK server, I got the errors mentioned.

---

<div class="post-metadata">

**Author:** ![harshbajaj16](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harshbajaj16/32/44970_2.png) [@harshbajaj16](https://discuss.elastic.co/u/harshbajaj16)\
**Post date:** [April 25, 2018, 11:23am UTC](https://discuss.elastic.co/t/filebeat-6-2-3-unable-to-create-runner-due-to-error-can-only-start-a-prospector-when-all-related-states-are-finished-id-finished-false-fileinfo-0xc420196b60-source-var-log-nginx-access-log/129455/2 "2018-04-25T11:23:34Z")

</div>

Hi,

> [@nacesprin](#):
>
> Note: I've installed on all client servers and not errors found, but when filebeat is installed on the same ELK server, I got the errors mentioned.

sorry to ask you but I'm not able to understand that why you install filebeat on same(ELK) server even you can use the **File** plugin in logstash for the same.

Thanks,  
Harsh Bajaj

---

<div class="post-metadata">

**Author:** ![nacesprin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nacesprin/32/30024_2.png) [@nacesprin](https://discuss.elastic.co/u/nacesprin)\
**Post date:** [April 25, 2018, 11:36am UTC](https://discuss.elastic.co/t/filebeat-6-2-3-unable-to-create-runner-due-to-error-can-only-start-a-prospector-when-all-related-states-are-finished-id-finished-false-fileinfo-0xc420196b60-source-var-log-nginx-access-log/129455/3 "2018-04-25T11:36:42Z")

</div>

My ignorance. Thanks, I will try File plugin.  
Any way... is it normal that error on the ELK server?

---

<div class="post-metadata">

**Author:** ![harshbajaj16](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harshbajaj16/32/44970_2.png) [@harshbajaj16](https://discuss.elastic.co/u/harshbajaj16)\
**Post date:** [April 26, 2018, 3:51am UTC](https://discuss.elastic.co/t/filebeat-6-2-3-unable-to-create-runner-due-to-error-can-only-start-a-prospector-when-all-related-states-are-finished-id-finished-false-fileinfo-0xc420196b60-source-var-log-nginx-access-log/129455/4 "2018-04-26T03:51:02Z")

</div>

Hi Javier Leal,

No, It's not normal. It should work we need to check the logs and config files for RCA.

Better you use logstash file plugin you don't need to install filebeat on same server as it will use extra system resources and memory.

Thanks,  
Harsh Bajaj

---

<div class="post-metadata">

**Author:** ![nacesprin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nacesprin/32/30024_2.png) [@nacesprin](https://discuss.elastic.co/u/nacesprin)\
**Post date:** [April 26, 2018, 7:32am UTC](https://discuss.elastic.co/t/filebeat-6-2-3-unable-to-create-runner-due-to-error-can-only-start-a-prospector-when-all-related-states-are-finished-id-finished-false-fileinfo-0xc420196b60-source-var-log-nginx-access-log/129455/5 "2018-04-26T07:32:36Z")

</div>

Thanks @harshbajaj16 . File plugin worked for me 😉

---

<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 24, 2018, 7:32am UTC](https://discuss.elastic.co/t/filebeat-6-2-3-unable-to-create-runner-due-to-error-can-only-start-a-prospector-when-all-related-states-are-finished-id-finished-false-fileinfo-0xc420196b60-source-var-log-nginx-access-log/129455/6 "2018-05-24T07:32:40Z")

</div>

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