# Mysterious \_dateparsefailure on identical fields

**URL:** <https://discuss.elastic.co/t/mysterious-dateparsefailure-on-identical-fields/240597>\
**Category:** Logstash\
**Created:** [July 9, 2020, 7:43pm UTC](https://discuss.elastic.co/t/mysterious-dateparsefailure-on-identical-fields/240597 "2020-07-09T19:43:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [July 9, 2020, 7:46pm UTC](https://discuss.elastic.co/t/mysterious-dateparsefailure-on-identical-fields/240597/2 "2020-07-09T19:46:19Z")

</div>

Is the hour part 2 AM? That did not exist on 2015/3/8. DST started and we went straight from 1:59:59 to 3:00:00. See [here](https://discuss.elastic.co/t/logstash-date-function-mapping-timestamp-ends-with-error-dateparsefailure-when-a-hour-is-02/227679/5) for a possible solution.

---

_[View the full topic](https://discuss.elastic.co/t/mysterious-dateparsefailure-on-identical-fields/240597)._