Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
filebeat 1.2.2 reships rotated log files upon restart due to lost offset #1528
We just updated from filebeat 1.1.2 to 1.2.2 to resolve #1281 in our environment. This has revealed a new issue.
We are experiencing the problem on a local ext4 file system on Ubuntu 14.04 running in AWS EC2 and also running in Virtualbox 5.
I have created a bash script which reproduces the issue and published it as a gist, including a log of the output:
Essentially when filebeat exits, the registry is recorded with the entry for the fully-shipped and recently-rotated log file not having an offset specified.
When filebeat is started again, the missing offset value is treated effectively the same as