# Log rotate introduced blank offset entry in registry

**URL:** <https://discuss.elastic.co/t/log-rotate-introduced-blank-offset-entry-in-registry/50351>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [May 18, 2016, 2:55pm UTC](https://discuss.elastic.co/t/log-rotate-introduced-blank-offset-entry-in-registry/50351 "2016-05-18T14:55:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![logilouis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/logilouis/32/5525_2.png) [@logilouis](https://discuss.elastic.co/u/logilouis)\
**Post date:** [May 18, 2016, 2:55pm UTC](https://discuss.elastic.co/t/log-rotate-introduced-blank-offset-entry-in-registry/50351/1 "2016-05-18T14:55:57Z")

</div>

Hi,

I noticed that when Filebeat detected a log rotation, it will create a new entry in registry. I discovered that the new entry will have blank offset. An example of the rotated log entry from my registry file (I expanded the JSON):

> /home/mule/apps/mule-enterprise-standalone-3.7.3/logs/mule-app-HREventPublisher-1.4.0-v201605130543.log'.'2016-05-14":{  
> "source":"/home/mule/apps/mule-enterprise-standalone-3.7.3/logs/mule-app-SAPFixedAssetsToCoupaConsumer-1.0.2.log.2016-05-16",  
> "FileStateOS":{  
> "inode":712795,  
> "device":64778  
> }  
> }

If Filebeat were to restart it will then reprocess the file from the beginning.

Is this a known design?

Thanks for the advice.

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [May 18, 2016, 6:19pm UTC](https://discuss.elastic.co/t/log-rotate-introduced-blank-offset-entry-in-registry/50351/2 "2016-05-18T18:19:00Z")

</div>

This is a know issue and was fixed in the 1.2.3 release today: [https://www.elastic.co/guide/en/beats/libbeat/current/release-notes-1.2.3.html](https://www.elastic.co/guide/en/beats/libbeat/current/release-notes-1.2.3.html)

Thanks for reporting it.

---

<div class="post-metadata">

**Author:** ![logilouis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/logilouis/32/5525_2.png) [@logilouis](https://discuss.elastic.co/u/logilouis)\
**Post date:** [May 19, 2016, 2:17pm UTC](https://discuss.elastic.co/t/log-rotate-introduced-blank-offset-entry-in-registry/50351/3 "2016-05-19T14:17:37Z")

</div>

Thanks ruflin! I have tested and confirmed that 1.2.3 fixed the missing offset of rotated log entry.

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [May 19, 2016, 2:37pm UTC](https://discuss.elastic.co/t/log-rotate-introduced-blank-offset-entry-in-registry/50351/4 "2016-05-19T14:37:39Z")

</div>

Good to hear. Thanks for testing.

---

<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 5, 2017, 9:51pm UTC](https://discuss.elastic.co/t/log-rotate-introduced-blank-offset-entry-in-registry/50351/5 "2017-07-05T21:51:45Z")

</div>