# FSCrawler won't crawl new files

**URL:** <https://discuss.elastic.co/t/fscrawler-wont-crawl-new-files/102491>\
**Category:** Elasticsearch\
**Created:** [October 2, 2017, 9:57pm UTC](https://discuss.elastic.co/t/fscrawler-wont-crawl-new-files/102491 "2017-10-02T21:57:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Quix0r](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quix0r/32/22709_2.png) [@Quix0r](https://discuss.elastic.co/u/Quix0r)\
**Post date:** [October 2, 2017, 9:57pm UTC](https://discuss.elastic.co/t/fscrawler-wont-crawl-new-files/102491/1 "2017-10-02T21:57:02Z")

</div>

The crawler seem not to add any new files. So I investigated and found below warning message on all profiles:

```auto
Can't find stored field name to check existing filenames in path
[/some/path]. Please set store: true on field [file.filename]

```

I currently run updated `master` branch. I have tried to look for it generically as it is ES-specific and came up with this:

```auto
PUT /myindex/bla/_mapping
{
    "properties": {
      "file.filename": {
        "type": "keyword", 
        "store" : true
      }
    }
}

```

But it gives back:

```auto
{
  "error": {
    "root_cause": [
      {
        "type": "illegal_argument_exception",
        "reason": "Mapper for [file.filename] conflicts with existing mapping in other types:\n[mapper [file.filename] has different [store] values]"
      }
    ],
    "type": "illegal_argument_exception",
    "reason": "Mapper for [file.filename] conflicts with existing mapping in other types:\n[mapper [file.filename] has different [store] values]"
  },
  "status": 400
}

```

What can I do to fix this?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 2, 2017, 10:11pm UTC](https://discuss.elastic.co/t/fscrawler-wont-crawl-new-files/102491/2 "2017-10-02T22:11:29Z")

</div>

Did you upgrade FSCrawler or started from scratch (no index)?

---

<div class="post-metadata">

**Author:** ![Quix0r](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quix0r/32/22709_2.png) [@Quix0r](https://discuss.elastic.co/u/Quix0r)\
**Post date:** [October 2, 2017, 11:11pm UTC](https://discuss.elastic.co/t/fscrawler-wont-crawl-new-files/102491/3 "2017-10-02T23:11:56Z")

</div>

Bonsoir.

I upgraded and used `--upgrade` before starting jobs.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 3, 2017, 6:01am UTC](https://discuss.elastic.co/t/fscrawler-wont-crawl-new-files/102491/4 "2017-10-03T06:01:55Z")

</div>

Yeah.

You need to read `Upgrade to 2.5` Section.

I did not implement a upgrade mechanism for this as I don’t believe there are many users in production with this project but I might be wrong.

Do you think we should support an upgrade option for 2.5? Could you open an issue? At the very least I should warn users running the upgrade command that no upgrade is made for 2.5 yet.

---

<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:** [October 31, 2017, 6:02am UTC](https://discuss.elastic.co/t/fscrawler-wont-crawl-new-files/102491/5 "2017-10-31T06:02:00Z")

</div>

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