Filebeat locks file when logstash is not runnig

(Ievgen Luppol) #1

I'm using filebeat to ship logs created by log4cxx to ELK stack.
When filebeat is running but logstash is not available, log4cxx cannot rotate log file, so it becomes large (log generation speed is about 4 MB per minute, we use log rotation by 1 MB).
I tried to set close_timeout option to 1m, but filebeat still keeps the file open.

Please see the log file generated by filebeat:

So how to make filebeat not block the file rotation?

(ruflin) #2

I assume what you mean by block file rotation is keeping the file open. Because filebeat should not block any file rotation but will keep the file open until data is sent.

As documented here close_timeout will not work if the output is completely blocked.

What is your expect behaviour for filebeat related to the data? Should it just drop the data it did not send so far (means data loss)?

(Ievgen Luppol) #3

Yes, I expect that filebeat will drop the data which it cannot send.
How to achieve this behavior?

(ruflin) #4

Currently there is no way to do this if your output is completely blocked. One "workaround" here is to use harvester_limit so not too much space is taken up. The disadvantage of this is that the files that are already open are kept and sent when the output gets available again, means some newer files will be dropped after rotation. The files that will be around will still start harvesting if the output comes available again. So I think in your case this is a feasible solution.

(Ievgen Luppol) #5

I tried harvester_limit, but it didn't fix the problem. As I understood from filebeat manual, harvester_limit just sets the maximum number of harvesters, but even the only harvester keeps file open, so it cannot be rotated.
Also I noticed, that when filebeat is running and output is blocked, it locks only the last one file (log4cxx.log.10), so I cannot delete it by hand.
Is there any other way to close files when output is blocked? Or maybe some way to use other output (for example to file) when logstash output is blocked?

(ruflin) #6

The behaviour that you describe is what is expected with the harvester_limit. I'm not sure why you mention that the file cannot be rotated? It should be possible to rename / rotate file, only deletion is not happening. So what you normally end up with is that you have several "deleted but open" files with the same name. What are you using for log rotation?

(Ievgen Luppol) #7

I'm using log4cxx RollingFileAppender configured to rotate files every 1MB.
The problem is only with the last file, which cannot be deleted and as I understand it leads to situation when logs are accumulated in the original log file (log4cxx.log), so it becomes very large. When I stop filebeat, rotation process is resumed immediately, so log4cxx.log becomes log4cxx.log.1, log4cxx.log.1 becomes log4cxx.log.2 and so on... and log4cxx.log.10 is removed.

Log entries gets truncated on file rotation
(ruflin) #8

Seems to be the day of RollingFileAppender: Log entries gets truncated on file rotation Or is this other thread somehow related / same company?

The part I still didn't understand about RollingFileAppender is when the initial file gets truncated / removed?

(Ievgen Luppol) #9

Yeah, but I don't think this thread is somehow related :slight_smile:

We use RollingFileAppender with MaxBackupIndex set to 10, so it creates only 10 files during log rotation.

As I understand, RollingFileAppender just removes the last file, renames the initial file and all the subsequent files, and then new initial file is created.
As an example I tried to configure filebeat to read only from initial file. The rotation process stalled when initial file became the last one and I think RollingFileAppender couldn't remove it because it was opened by filebeat.

(ruflin) #10

Ok, that sounds like "normal" log rotation. What is your operating system / file system? I see some Windows path in your logs? This could be a Windows related issue :frowning:

(Ievgen Luppol) #11

We're using Windows Server 2008 R2 Enterprise and NTFS file system.

(ruflin) #12

Do you get any errors from log4j when it tries to rotate / remove the file? I currently assume on Windows deleted but still open files can't have the same name (possible on Linux). As the file is not deleted, log rotation is actually blocked. So instead of having open file handlers on deleted files like on windows, the initial file written to is constantly growing.

Here is a github issue where we are discussing about a config option like drop_events or similar which would solve this issue: But it would mean losing events.

(system) #13

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.