nxlog-processor does not terminate after reading logs?
Tags:
#1
andypprobert
I am experimenting running nxlog-processor against a configuration file which is working OK for foreground use, but it does not terminate after pickup, or if no new files are present.
I have configured it to monitor a folder in Windows with a wildcarded path \....\\*.JSON Also with multiline input.
Are there any limitations, special tips for single-run of nxlog-processor?
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Helvetica} p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 10.0px Helvetica}
#1
andypprobert
I am experimenting running nxlog-processor against a configuration file which is working OK for foreground use, but it does not terminate after pickup, or if no new files are present.
I have configured it to monitor a folder in Windows with a wildcarded path \....\\*.JSON Also with multiline input.
Are there any limitations, special tips for single-run of nxlog-processor?
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Helvetica}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 10.0px Helvetica}
The internal test harness uses nxlog-processor wherever possible to verify correctness and it exits properly for each test case. There is one similar bug report wrt nxlog-processor but it is related to the usage of network modules (om_tcp/im_tcp).
If you can post your config that would make things clearer.
