responses
<Input Result_Log>
Module im_file
File "C:\\xxx\\Result*.log"
SavePos TRUE
</Input>
above is my nxlog input config.
Result-3156.log is my log file name and 3156 is pid.
The log file will rotate when it reaches the max size and generate Result-3156.log.1 file.
I find some logs loss at the bottom of Result-123.log.1
And nxlog's log shows "2018-03-01 20:48:02 INFO inode changed for 'C:\xxx\Result-3156.log' (25746->25799): reopening possibly rotated file" at the same time point.
I suspect this is caused by the monitor interval 1 second.
Is it a bug ? or nxlog can not guarantee this scenario ? or something can do to avoid it ?
Comments (2)
The
im_file
module has been significantly enhanced in the NXLog EE beta that is scheduled for release this month. If you could test the trial and confirm whether the issue is still present that would help us and the CE could be also updated sooner.I tried NXLog EE beta. And problem still exists. I guess the scenario is like this, when log file rotate from file 'xxx.log' to 'xxx.log.1', because the file 'xxx.log.1' does not match im_file module file name pattern, the logs are lost during nxlog monitor interval 1 second. If you have specification about rotate file process, that will help me a lot.
By the way, when I install "nxlog-3.99.3332-x64_trial.msi" version, the default location is "C:\Program Files (x86)\nxlog\", not "C:\Program Files\nxlog\".