You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We see most of our pods logs being duplicated over and over again. Seemingly the pods logfile is being re-read periodically from the beginning every time.
Whenever I check the positions.yaml for a given logfile, it always has a byte offset that matches the last byte, so it seems to set it correctly when getting to the end.
Here is an sample of 4 repeating log entries that sit in the beginning of the pod logfile being indexed over and over again.
Promtail output shows that the tailer is running into to some issues with file handles after move/delete of the file:
The number of "Re-opening moved/deleted file" entries in the promtail log rougly correlates with the number of duplicates I observe, but I can't exactly correlate the timestamps. But that may be due due to ingestion delay or other system pressure.
However, seeing: "Seeked /var/log/pods/prod_authserver-6f5b5bf757-h9rgw_8eaea579-bffb-4ddf-a2d6-155bc3df5fc7/authserver/0.log - &{Offset:75360158 Whence:0}" indicates that it successfully starts at the correct offset after experiencing the "Re-opening moved/deleted"-issue , which is not supporting my theory that the re-opening leads to this issue.
Describe the bug
We see most of our pods logs being duplicated over and over again. Seemingly the pods logfile is being re-read periodically from the beginning every time.
Whenever I check the positions.yaml for a given logfile, it always has a byte offset that matches the last byte, so it seems to set it correctly when getting to the end.
Here is an sample of 4 repeating log entries that sit in the beginning of the pod logfile being indexed over and over again.
Promtail output shows that the tailer is running into to some issues with file handles after move/delete of the file:
Observations
The number of "Re-opening moved/deleted file" entries in the promtail log rougly correlates with the number of duplicates I observe, but I can't exactly correlate the timestamps. But that may be due due to ingestion delay or other system pressure.
However, seeing: "Seeked /var/log/pods/prod_authserver-6f5b5bf757-h9rgw_8eaea579-bffb-4ddf-a2d6-155bc3df5fc7/authserver/0.log - &{Offset:75360158 Whence:0}" indicates that it successfully starts at the correct offset after experiencing the "Re-opening moved/deleted"-issue , which is not supporting my theory that the re-opening leads to this issue.
Promtail itself does not restart
Promtail configuration:
Expected behavior
Expected not to see duplicated indexed entries.
Environment:
Screenshots, Promtail config, or terminal output
If applicable, add any output to help explain your problem.
The text was updated successfully, but these errors were encountered: