Hi Team, frequently fIlebeat is stopped suddenly and can see below error in logs. please help on this. File is inactive: Closing because close_inactive of 5m0s reached 2020-04-14T02:56:12.960-0500 INFO log/harvester.go:320 Reader was closed: /path/access.log. Closing. 2020-04-14T02:56:1…

File is inactive: Closing because close_inactive of 15m0s reached

nikhilesh (nikhilesh) April 15, 2020, 2:46am 3

I tired with that option keeping close_inactive as 30m0s , but still it is crashing

1 Like

Topic		Replies	Views
Closing because close_inactive of 5m0s reached Beats filebeat	3	22289	February 2, 2018
Filebeat close_inactive while file is still active Beats filebeat	2	5332	September 19, 2019
File is inactive: Closing because close_inactive of 5m0s reached Beats filebeat	1	3607	May 21, 2021
Filebeat re-opens a harvester for a inactive file Beats filebeat	7	5838	July 3, 2017
Filebeat never releases unupdated logfiles Beats filebeat	9	1525	November 7, 2017