# Leap Day Issues?

**URL:** <https://discuss.elastic.co/t/leap-day-issues/43018>\
**Category:** Kibana\
**Created:** [February 29, 2016, 4:36pm UTC](https://discuss.elastic.co/t/leap-day-issues/43018 "2016-02-29T16:36:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vzweits](https://avatars.discourse-cdn.com/v4/letter/v/848f3c/32.png) [@vzweits](https://discuss.elastic.co/u/vzweits)\
**Post date:** [February 29, 2016, 4:36pm UTC](https://discuss.elastic.co/t/leap-day-issues/43018/1 "2016-02-29T16:36:15Z")

</div>

Just curious if anyone else is experiencing leap day issues. I'm creating a daily index with Logstash, so today's index looks something like **logstash-{custom\_name}-2016.02.29** with "Index contains time-based events" enabled, and Kibana started throwing an error today:

```
Courier Fetch: [unsupported_operation_exception] custom format isn't supported

Version: 4.3.0
Build: 9369
Error: [unsupported_operation_exception] custom format isn't supported
    at respond (http://<hostname_removed>:5601/bundles/kibana.bundle.js:76160:16)
    at checkRespForFailure (http://<hostname_removed>:5601/bundles/kibana.bundle.js:76123:8)
    at http://<hostname_removed>:5601/bundles/kibana.bundle.js:74741:8
    at processQueue (http://<hostname_removed>:5601/bundles/commons.bundle.js:42339:29)
    at http://<hostname_removed>:5601/bundles/commons.bundle.js:42355:28
    at Scope.$eval (http://<hostname_removed>:5601/bundles/commons.bundle.js:43583:29)
    at Scope.$digest (http://<hostname_removed>:5601/bundles/commons.bundle.js:43394:32)
    at Scope.$apply (http://<hostname_removed>:5601/bundles/commons.bundle.js:43691:25)
    at done (http://<hostname_removed>:5601/bundles/commons.bundle.js:38140:48)
    at completeRequest (http://<hostname_removed>:5601/bundles/commons.bundle.js:38338:8)

```

I'm going to try reindexing data using a different name to see if that helps. Just wanted to see if anyone else had the same issue and if there is any resolution.

---

<div class="post-metadata">

**Author:** ![vzweits](https://avatars.discourse-cdn.com/v4/letter/v/848f3c/32.png) [@vzweits](https://discuss.elastic.co/u/vzweits)\
**Post date:** [February 29, 2016, 6:46pm UTC](https://discuss.elastic.co/t/leap-day-issues/43018/2 "2016-02-29T18:46:57Z")

</div>

Discovered the issue, though I'm not sure on the root cause yet. Somehow Logstash created an index with the wrong format ( **logstash-4568844.09.02** ) which threw off Kibana.

---

<div class="post-metadata">

**Author:** ![111118](https://avatars.discourse-cdn.com/v4/letter/1/65b543/32.png) [@111118](https://discuss.elastic.co/u/111118)\
**Post date:** [May 31, 2016, 1:54am UTC](https://discuss.elastic.co/t/leap-day-issues/43018/3 "2016-05-31T01:54:01Z")

</div>

Then how can we resolve it?

Is logstash-4568844.09.02 a file?

I encounter the issue almost every time when I import new data.

---

<div class="post-metadata">

**Author:** ![vzweits](https://avatars.discourse-cdn.com/v4/letter/v/848f3c/32.png) [@vzweits](https://discuss.elastic.co/u/vzweits)\
**Post date:** [June 2, 2016, 1:50pm UTC](https://discuss.elastic.co/t/leap-day-issues/43018/4 "2016-06-02T13:50:04Z")

</div>

In my case, this was a data issue. On leap day this year, one of my data sources produced an invalid date which caused Logstash to create an index that didn't match the date pattern I configured in Kibana. To get around it, I simply deleted the invalid index. Of course, you'll lose whatever data you had in that index, but in my case I was able to live with it since it was only one record of insignificant data that caused this to happen.

---

<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:** [July 6, 2017, 1:51pm UTC](https://discuss.elastic.co/t/leap-day-issues/43018/5 "2017-07-06T13:51:48Z")

</div>